Oracle Workflow Developer's Guide Release 2.6.3 Part Number B10284-02 |
![]() |
![]() |
![]() |
![]() |
![]() |
||
Previous | Next | Contents | Index | Glossary |
Note: WF_NOTIFICATION() is not a PL/SQL function, but rather a special message function that can only be called within an Oracle Workflow message body.
Message Attribute Table To include a table of message attributes in a message body, call WF_NOTIFICATION() with the ATTRS option followed by the internal names of the message attributes, separated by commas. Use the following format:
WF_NOTIFICATION(ATTRS,<attribute1>,<attribute2>,<attribute3>,...)
Note: You must not include any spaces or carriage returns in the call to WF_NOTIFICATION(). You only need to use a comma to delimit the parameters in the list.
The message attribute table contains a row for each message attribute listed in the WF_NOTIFICATION() call, showing the display name and the value for each attribute.
Notification History Table To include a notification history table in a message body, call WF_NOTIFICATION() with the HISTORY option in the following format:
WF_NOTIFICATION(HISTORY)
The notification history table contains a row for each previous execution of the same notification activity in the process, as well as a row for the initial submission of the process. Notification history is specific to a particular notification activity node and is most useful when a process loops back to the same node more than once. For example, for a requisition approval notification activity that sends a certain notification to several approvers in turn, the notification history table would contain a row for each approver to whom the notification was sent, as well as a row for the process owner.
The notification history table includes the following columns:
Note: The process owner cannot add a note for the notification history table when submitting the process. Only a notification recipient can add a note when responding to the notification.
Previous | Next | Contents | Index | Glossary |