Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

User Exit Messages

User Exit Messages

User exits can return a message (as an error, warning or confirmation) to be displayed to the user.
These messages are handled by IDD in the same way that it handles its own messages. Each message has a code that is a key to the resource bundle ErrorCodeBundle.properties. IDD finds the error level (error, warning or confirmation) and the text of the message in this resource bundle.
Be sure to use unique codes for any custom messages.
These message strings can be localized just as other strings can be localized.
Messages can have parameters that are replaced with data specified in the user exit. These parameters are handled using the Java MessageFormat class.
The format for the messages in ErrorCodeBundle.properties is:
error code=error level|title|main message[|secondary message]
where
Item
Description
Error code
Unique key for the message.
Error level
One of the following values: ERROR, WARNING, or CONFIRMATION.
Title
Title for the dialog box. The title should describe the location and context in which the problem occurred. If not specified, the title will be 'Informatica Data Director'.
main message
Main error message. This text should describe the problem from the IDD application user's point of view - not an internal technical point of view. For example, something like
"Problem saving xxx", not "Put error"
.
Secondary message
Secondary part of the message telling the IDD application user what to do about the problem. In the dialog box, this part will be separated from the main message by at least one blank line. This message should not be too long.

0 COMMENTS

We’d like to hear from you!