Previous Topic: Notification without ACK Process ParametersNext Topic: Make an Event Inactive


Notification without Escalation Process Parameters

The process parameters that appear when you define an event depend on the workflow provider process type that you select. The Notification without Escalation process is an email notification process that is included with the product. This process sends an email notification to the specified recipient when an event occurs. If the recipient does not respond in the specified time period, the process does not escalate the notification. However, the process marks the associated event as failed. When you select this process as the workflow process for an event, a list of parameters appears.

Important! CA APM and CA Process Automation do not validate the information that you enter for the parameters. You must verify that your input is valid and that you entered the data in the correct format.

The following fields require explanation:

User IDs

CA Process Automation user ID (CA APM or non-CA APM user) for acknowledging the notification. You can specify more than one user ID, separated with colons. Do not enter spaces between entries.

Example: This example contains a user ID (John) that is a text entry value and the mapped field {legaldoc.owner.userid}. The two items are separated with a colon. The mapped field {legaldoc.owner.userid} represents the user ID of the user in the Owner field of the Legal Document. To obtain the mapped field {legaldoc.owner.userid}, click the Map Fields button, select the Owner link in the Add Fields dialog, and select User ID from the list of attributes.

John:{legaldoc.owner.userid}
Groups

CA Process Automation group name for acknowledging the notification. You can specify more than one group name, separated with colons. Do not enter spaces between entries.

Example: This example contains a CA Process Automation group name (ITAM) that is a text entry value.

ITAM
Email Addresses

Email address (or distribution list) of the recipient of the email. You can specify more than one address, separated with semicolons. You can enter spaces between entries.

Example: This example contains an email address (john.doe@company.com) that is a text entry value and the mapped field {legaldoc.owner.emailid}. The two items are separated with a semicolon. The mapped field {legaldoc.owner.emailid} represents the email address of the user in the Owner field of the Legal Document. To obtain the mapped field {legaldoc.owner.emailid}, click the Map Fields button, select the Owner link in the Add Fields dialog, and select Email Address from the list of attributes.

john.doe@company.com;{legaldoc.owner.emailid}
Email Copy Addresses

Email address (or distribution list) of the copy recipient of the email. You can specify more than one address, separated with semicolons. You can enter spaces between entries.

Example: This example contains an email address (jane.doe@company.com) that is a text entry value and the mapped field {legaldoc.requestor.emailid}. The two items are separated with a semicolon. The mapped field {legaldoc.requestor.emailid} represents the email address of the user in the Requestor field of the Legal Document. To obtain the mapped field {legaldoc.requestor.emailid}, click the Map Fields button, select the Requestor link in the Add Fields dialog, and select Email Address from the list of attributes.

jane.doe@company.com;{legaldoc.requestor.emailid}
Email Subject

Subject of the email message for the recipient. Enter text or combine text entry with mapped fields. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (Acknowledgment required for) and the mapped field {legaldoc.documentidentifier}.

Acknowledgment required for {legaldoc.documentidentifier}
Email Message

Message of the email for the recipient. Enter text or combine text entry with mapped fields. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (The Legal Document Document Identifier), the mapped field {legaldoc.documentidentifier}, and more text entry content.

The Legal Document Document Identifier {legaldoc.documentidentifier} requires your acknowledgment using the link in the Subject of this email.
Acknowledgment Title

Title that appears on the acknowledgment task that the user accesses in CA Process Automation to acknowledge receipt of the notification. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (The Legal Document Document Identifier) only.

The Legal Document Document Identifier
Acknowledgment Description

Description that appears on the acknowledgment task that the user accesses in CA Process Automation to acknowledge receipt of the notification. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (The Legal Document Document Identifier) and the mapped field {legaldoc.documentidentifier}.

The Legal Document Document Identifier {legaldoc.documentidentifier}
Acknowledgment Time-out (Days:Hours:Minutes)

The amount of time that is allowed for acknowledgment after the email notification is sent. Days, hours, and minutes can be any numeric value. The format must be days:hours:minutes (separated with colons).

Example: This example specifies a time-out period of exactly four days.

4:00:00
Reminder Email Subject

Subject of the reminder email message. The product sends a reminder when half of the Acknowledgment Time-out period has passed. Enter text or combine text entry with mapped fields. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (Reminder for), the mapped field {legaldoc.documentidentifier}, and additional text entry content.

Reminder for {legaldoc.documentidentifier}. Acknowledgment required.
Reminder Email Message

Message of the reminder email. The product sends a reminder when half of the Acknowledgment Time-out period has passed. Enter text or combine text entry with mapped fields. You do not need to enter colons or semicolons to separate entries.

Example: This example contains text entry content (Reminder: The Legal Document Document Identifier), the mapped field {legaldoc.documentidentifier}, and more text entry content.

Reminder: The Legal Document Document Identifier {legaldoc.documentidentifier} requires your acknowledgment using the link in the Subject of this email.