Oracle Workflow Guide Release 2.6.2 Part Number A95265-03 |
Contents | Index | Glossary | Master Index | Feedback |
Attention: To update the internal name for a message attribute once it is defined, you must use a special SQL script called wfchmsga.sql. You should only use this script to correct errors in a message attribute's internal name during design time. Do not use this script to rename message attributes that are involved in running instances of processes. See: Wfchmsga.sql.
Caution: Do not include colons ":" or leading/trailing spaces in your internal name.
Attention: For 'Send' message attributes, the Display Name of the attribute appears in plain text e-mail notifications only if the attribute is of type URL to describe what the URL drills down to.
Attention: 'Respond' message attributes of type URL do not appear properly when you view the notification from a plain text e-mail reader. You should advise your workflow users to view their notifications from the Notification Details web page if you plan to create messages with 'Respond' message attributes of type URL.
Attention: A single 'Respond' message attribute of type URL replaces the Notification Details web page response frame and takes the notification recipient to a custom HTML page to complete the notification response. Your custom HTML response document must include references to all your 'Respond' message attributes, including the special RESULT attribute, if one is defined, and must also include a call to the Workflow Engine CompleteActivity( ) API to inform the Workflow Engine when the notification response is complete.
Attention: 'Send' and 'Respond' message attributes of type Form appear only when your Notifications web pages are launched from Oracle Applications. The attached form icon is enabled if a notification message includes a 'Send' message attribute of type Form. The notification recipient can click on the attached form icon to drill down to the form function defined by the message attribute.
Attention: If a message includes a 'Respond' message attribute of type Form, the attached form icon that appears in the notification's Response section simply drills down directly to the designated form function. This form function must be coded with a call to the Workflow Engine CompleteActivity( ) API to inform the Workflow Engine that the notification response is complete. See: Workflow Engine APIs.
Attention: Do not specify a message attribute's data type as Attribute, as it serves no purpose in a notification message and is also not supported by the Workflow Notification System.
Attention: 'Respond' message attributes of type Date, Number, Text, Document or Role prompt the notification recipient to respond with a date, number, text value, document, role (internal or display name), respectively.
'Respond' message attributes of type Lookup prompt the notification recipient to select a response from a list of values.
Note: You can attach, as well as embed (by token substitution) Document attributes in the notification message and are not limited to one or the other.
Note: You can attach, as well as embed (by token substitution) URL attributes in the notification message and are not limited to one or the other.
Note: A message attribute type of 'Text' is compatible with any item attribute type, but all other message attribute types must match the item attribute type exactly.
Note: Message attributes assume the access/protection level of their parent message.
Attention: The order that you list 'Respond' message attributes in the navigator tree correlate to the order in which they appear in the response section of the notification message. You can use the drag and drop feature of the navigator tree to reorder a set of attributes, or select an attribute and choose Move Attribute Up or Move Attribute Down from the Edit menu.
Using the Edit Button in a Property Page
Reviewing Notifications via Electronic Mail
Previous | Next | Contents | Index | Glossary |