Handle Messages
Overview
This activity enables you to specify the error message details for a selected component. For the selected language you can search for existing list of message codes, define new message codes and message description. You can also map the message codes to methods and map placeholders to messages.
Click the checkbox next to a component and click the “Specify Errors” link if you want to specify the error message details for the selected component.
The “Handle Messages” page appears.
The following details are displayed in the header:
Business Process |
The description of the business process. |
Component |
The description of the selected component. |
Select the following field:
Language |
Use the drop-down list box to select the language for which you want to specify the message details. The list of available languages is displayed as options. Mandatory |
There are three tabs displayed viz. Message Definition, Message Mapping and Message Placeholder Mapping.
Click the “Message Definition” tab to define the message details.
This tab is displayed by default on launch of the page.
To view existing message details
Enter the following search criteria fields:
Message |
The description of the message whose details you want to retrieve. You can specify the message fully or partially using the “*” as wildcard character. All the messages similar to the value entered are retrieved and displayed. |
Message Code From |
The starting code from which you want to retrieve the list of message codes. |
Message Code To |
The ending code up to which you want to retrieve the list of message codes. |
Severity |
Use the drop-down list box to select the severity by which you want to retrieve the list of message codes. The options listed are “Continue” and “Critical”. |
Click “Search”.
The system retrieves and displays the list of message codes in the multiline based on the specified search and filter criteria.
Note: The search results are displayed based on the language selected in the drop-down list box in the header.
To define new message details
Enter the following field in the header:
Message Code |
A unique code that identifies the message. |
Message in English |
The message description is displayed in English when you click “Message Definition Save”. |
Message Description |
The description of the message that should be displayed to the user in the specified language. |
Severity |
Use the drop-down list box to select the severity for the message code. The options listed are “Continue” and “Critical”. Continue – Displays a message and continues with the process. Critical – Stops all action processes. |
Default Corrective Action |
The corrective action for the message code. |
Click “Message Definition Save”.
The message details that have defined for the specified component in the selected languages are saved.
Note:
· Message in English will be available only when the message details for the language English already exists for the given Message Code.
· Message placeholders can be used in the message description.
· Placeholders can be incorporated in the message as follows “Employee “{employeecode}” already exists!” Here the placeholder name is employeecode which is identified between the {} characters. The length of a placeholder name can be up to 30 characters long.
· Place holder name accepts characters ‘a to z’, ‘A to Z’, ‘0 to 9’, ‘_’ (underscore). The first letter of the name should be an alphabet.
· At run time placeholder value will holds the actual value like “Employee “John” already exists!”
· In a message there can be more than one place holder.
· When the message is updated for different languages the placeholders used in other languages should be same.
Click the “Message Mapping” tab to map the message codes to a selected method.
The “Message Mapping” tab is displayed.
Select the following fields:
Service |
Use the drop-down list box to select the service to which you want to map the message codes. The list of services that have generated for the component is displayed as options. |
Process Section |
The list of process sections for the selected service is displayed as options. |
Method |
Use the drop-down list box to select the method to which you want to map the message codes. The list of methods for the selected process section is displayed as options. |
Enter the following fields in the multiline
Message Code |
The code that identifies the message that you want to map to the selected method. Click |
Message Description |
The description of the message is displayed for the specified message code in the selected language. |
Click “Message Mapping Save”.
The message mapping details for the specified component are saved.
Click the “Message Placeholder Mapping” tab to map the message place holders to a selected message.
The “Message Placeholder Mapping” tab is displayed.
Select the following fields:
Service |
Use the drop-down list box to select the service to which you want to map the message placeholders. The list of services for which placeholders are available will be displayed as options. |
Process Section |
The list of process sections for the selected service is displayed as options. |
Method |
Use the drop-down list box to select the method to which you want to map the message placeholders. The list of methods for the selected process section is displayed as options. |
Message |
Use the drop-down list box to select the message to which you want to map the message placeholders. The list of messages map to the selected method is displayed as options. |
Enter the following fields in the multiline
Place Holder Name |
The name of the place holder for the selected message. |
Method Parameter Name |
Use the drop-down list box to select the name of the method parameter that you want to associate with the place holder for the message. |
Click “Place Holder Save”.
The message placeholder mapping details for the specified component are saved.
4 Business processes, components, activities and user interfaces should have been defined.
4 In the Specify User Interface Layout user interface control specifications and generate service should have been completed for the component