Defining Message
This page can be used to create a new message or edit existing message for the selected task. Tell me more.
Select the “Define Message” link at the bottom of the “Define Message – Choose Message” page.
The “Define Message” page appears.
The system displays the following fields:
Component Name |
The name of the component for which the message needs to be defined. |
Activity Name |
The name of the activity for which the message needs to be defined. |
Task Name |
The name of the task for which the message needs to be defined. |
Enter the following field:
Message ID |
The ID of the message (Alphanumeric, 5). Click on the lens icon near the ‘Message Id’ to launch the ‘Help on message’ page. The message id can be selected from this page. |
Click the "Get" pushbutton to retrieve the message details.
Modify the details in the following fields, if required:
Message Description |
A description of the message (Alphanumeric, 40). |
Notification Type |
Use the drop-down list box to select the type of the notification. Refer to the topic “Classifying Messages” for details on predefined notification types. |
Click the "Get Default Message" pushbutton to retrieve the default message details.
Enter the following fields:
Subject |
The purpose of the message (Alphanumeric, 1000). |
Message |
The body of the message (Alphanumeric, 2000). |
The system displays the following fields in the "Available Place Holders" multiline:
Place Holder |
A space to carry the dynamic value of any workflow parameter defined for an area. It can be used in subject or in message body. |
Description |
The description of the parameter, which is being used by a placeholder. |
Note: If no message is attached to the task, choose “Notification Type” in the drop-down list box and click the “Get Default Message” pushbutton. The system would display the default values of “Message”, “Message Description”, “Subject” etc. which can be changed and saved. Also, a “New Message ID” will be generated if no Message ID is specified.
Click the "Save" pushbutton to save the message details.
Click the "Delete" pushbutton to delete the message details.
Defining Message – An overview
This page can be used to create a new message or edit existing message for the selected task. There are sixteen types of notifications as classified below.
Messages can be classified into one of the predefined notification types, as listed in the following table:
Notification Type |
Objective |
Advanced Notification |
Select “Advanced Notification” if the message is to be sent to the ‘Authorizer’ while creating the document. For example, when an employee file is created, advanced notification can be sent to the user who has to authorize the employee file. |
Amendment Message |
Select “Amendment Message” if the message is to be sent to the ‘Authorizer‘ on amendment. |
Acceptance Notification to All |
Select “Acceptance Notification to All” if the message is to be sent to all the users (from the creator, through the intermediate authorizers, till the final authorizer) after the document is authorized. |
Acceptance Notification to Applicant |
Select “Acceptance Notification to Applicant” if the message is to be sent to the creator/initiator/applicant only, after the document is authorized. |
Cancel Message |
Select “Cancel Message” if the message is to be sent to the “Authorizer’, informing the cancellation of a document. Generally, on creation of the document, the authorizer is informed about the pending authorization. But, before the authorization, the user might cancel the document/request. In such a case, the authorizer has to be informed about the cancellation. |
Escalation |
Select “Escalation” if the escalation message is to be sent to a superior. For example, if an authorizer has not authorized a document and it is pending for a long time, “Workflow” business component has the capability of sending escalation messages to the superior. For example, if the leave application of an employee is pending with his/her supervisor, then an escalation message can be sent, to the next level supervisor to inform about the pending action. |
Forward Notification for Next Document |
Select “Forward Notification for Next Document“ if the message is to be sent to an authorizer, in an area other than the workflow area, in which the initiation of the document/request happened. When a document/request has to be authorized within the same area, then “Advanced Notification” is sent to the authorizer. |
Hold Message |
Select “Hold Message” if the message is to be sent to all the users by the authorizer, while putting a document on hold for some time. |
Message |
Select “Message” if a message has to be sent to some users. To broadcast a message, set the "Notification only Required" option. |
Reminder |
Select “Reminder” if the message is to be sent as a reminder about the pending action. |
Rejection Notification to All |
Select “Reject Notification to All” if the message is to be sent to all the users in the authorization process when the document gets rejected. Messages will be sent to all the users who worked on that document (from the creator to the authorizer). |
Rejection Notification to Applicant |
Select “Reject Notification to Applicant” if the message is to be sent to the creator / initiator when the documents gets rejected. |
Short Close |
Select “Short Close” if the message is to be sent to all the users while canceling an authorized document. The difference between “Cancel Message” and “Short Close”: The cancel message will be sent only to the authorizer when the creator cancels the document/request, but short close message will be sent to all the users when an authorizer cancels the authorized document. |
Skip |
Select “Skip” if the message is to be sent to the user who will get skipped during a task. Workflow intermediate step in authorize task, can be skipped. For example, if a request is pending with a user for more than ten days, then that level of authorization would be skipped and the document would proceed to the user for the next step defined in Workflow. This option provides the facility of waiting period for authorization. |
Superuser |
Select “Superuser” if the message is to be sent to all the users about the action of a superuser. If a superuser performs an action on the document, the document will reach the final state immediately and all the intermediate states will be bypassed. The message will be sent to all the users defined for the document. |
Information Exchange |
Select “Information Exchange” if the message is to be sent through the “Post Message” option. |
You can attach a new message to the selected task or edit an already attached message.