Skip Headers
Oracle Workflow Developer's Guide
Release 2.6.3.5
Part Number B12161-02
|
|
|
|
|
|
|
|
|
Previous |
Next |
|
Contents |
Index |
Glossary |
Action History
A notification can include an action history table that shows what actions users have performed on the notification to date. The action history table contains a row for each previous execution of the same notification activity node in a process, as well as a row for the initial submission of the process. For example, for a requisition approval notification activity that sends a certain notification to several approvers in turn, the action history table would contain a row for each approver to whom the notification was sent, as well as a row for the process owner. Additionally, if a notification is reassigned to another user in either delegate or transfer mode, or if one user requests more information about the notification and another user answers that request, the action history contains rows for those actions also.
- If the notification requires a response, then Oracle Workflow automatically includes the action history table in the notification.
- If the notification does not require a response, then Oracle Workflow only includes the action history table automatically if the notification has been reassigned at least once or if at least one recipient has requested more information about the notification. However, you can manually include the action history table by calling the special message function WF_NOTIFICATION(HISTORY) in the message body.
The formatting of the action history table depends on whether the notification contains an embedded Oracle Applications Framework region.
- If the notification contains an Oracle Applications Framework region, or if it contains only plain text and calls to the special WF_NOTIFICATION() message function, the table is formatted as an Oracle Applications Framework region.
- If the notification does not contain any Oracle Applications Framework regions, but does contain references to other types of message attributes, then the table is formatted in a standard Oracle Workflow format. This category includes all notifications in standalone Oracle Workflow as well as any Oracle Applications notifications that reference values other than Oracle Applications Framework regions.
The standard action history table provided by Oracle Workflow includes the following columns:
- Num - A sequence number indicating the order in which the actions on this notification took place, beginning at one (1) for the initial submission of the process by the process owner.
- Action Date - The date that a user acted on the notification.
- Action - The action performed on the notification.
- From - The user who performed the action.
- To - The next user who must act on the notification as a result of this action. For example, the next approver, the user to whom the notification was reassigned, or the user from whom more information was requested.
- Details - An additional note from the user who performed the action. To allow a recipient to add a note for the action history table while responding, you must create a special 'Respond' message attribute with the internal name WF_NOTE.
Define the message attribute with the following properties:
When the WF_NOTE attribute is defined with a source of 'Respond', it appears as part of the notification response section, and the recipient can enter a note there when responding to the notification. Oracle Workflow retrieves the note text stored in the WF_NOTE attribute and displays it in the action history table.
If the responder did not enter a note, or if the WF_NOTE message attribute was not defined for the notification, then the Note column in the action history table is left blank.
Oracle Workflow also lets users enter notes while reassigning a notification, requesting more information, or answering a request for more information. These notes are likewise displayed in the action history table.
To allow the process owner to add a note for the action of submitting the process and sending the initial notification, you must define a special message attribute named #SUBMIT_COMMENTS. See: #SUBMIT_COMMENTS Attribute.
You can optionally create a custom action history table to replace the standard action history table, using the special message attribute named #HISTORY. Your custom action history table must be formatted as an Oracle Applications Framework region, PL/SQL document, or PL/SQL CLOB document. You can also define the #HISTORY attribute with a null value to manually suppress the action history table for a notification. See: #HISTORY Attribute.
See Also
Embedding Oracle Applications Framework Regions in Messages
WF_NOTIFICATION() Message Function
To Create a Message
To Define a Message Attribute
Copyright © 2003, 2004, Oracle. All rights reserved.