Search Results wf_notifications_s

Overview

The APPS.WF_NOTIFICATION package body is the core PL/SQL implementation of Oracle Workflow notification processing in Oracle E-Business Suite 12.1.1 and 12.2.2. Its business function is to create, compose, render, and manage the notification messages that Oracle Workflow routes to human performers—approvers, requesters, and other participants—during the execution of a workflow process. This includes building notification content from message definitions and message attributes, resolving recipient roles through the directory services, controlling the notification framework (e-mail, Web-based, or other delivery agents), and capturing user responses that drive the workflow forward.

The package operates within the Workflow Notification System, which generates the items visible in the Worklist, the Notifications Summary, and the e-mail notifications sent through the workflow mailer. Because it is a package body with a companion specification, all external callers interact with it through WF_NOTIFICATION; the routines documented here are the internal implementations of that public API.

Key Procedures and Functions

ETRM documents 88 procedures and functions in this package body. The principal groups are described below by purpose; parameter lists are intentionally not reproduced here.

• Attribute management: ADDATTR, SETATTRTEXT, SETATTRNUMBER, SETATTRDATE, GETATTRINFO, GETATTRTEXT, GETATTRNUMBER, GETATTRDATE, and GETATTRDOC read and write the message attribute values associated with a notification, including text, numeric, date, and document attributes.
• Message and framework access: NTF_TABLE and WF_MSG_ATTR support access to the notification table and message attribute definitions, while SETFRAMEWORKAGENT designates the delivery framework agent for the notification.
• Content generation: GETTEXT, GETURLTEXT, GETSHORTTEXT, GETSUBJECT, GETBODY, and GETSHORTBODY produce the rendered subject and body text used for e-mail and Web notification display, including URL-bearing content.
• Notification lifecycle: GETINFO retrieves notification metadata, and RESPONDER records the recipient's response (for example, Approve or Reject), updating the notification status so the workflow engine can continue.

Tables Accessed

The package body reads and writes the central Workflow notification tables and their supporting definitions. WF_NOTIFICATIONS and its sequence-backed table WF_NOTIFICATIONS_S hold notification records, WF_NOTIFICATION_ATTRIBUTES stores attribute values, and WF_MESSAGES, WF_MESSAGE_ATTRIBUTES, WF_MESSAGE_ATTRIBUTES_TL, and WF_MESSAGE_ATTRIBUTES_VL provide message definitions and their translated attribute metadata. Recipient resolution uses WF_ROLES, WF_USER_ROLES, WF_LOCAL_ROLES, and WF_DIRECTORY. Workflow context is drawn from WF_ITEMS, WF_ITEM_TYPES, WF_ITEM_ACTIVITY_STATUSES, and its history table WF_ITEM_ACTIVITY_STATUSES_H. Routing and rules are supplied by WF_ROUTING_RULES, WF_NTF_RULES, WF_NTF_RULE_CRITERIA, and WF_NTF_RULE_MAPS. Supporting data includes WF_COMMENTS, WF_LOOKUPS, WF_ACTIVITIES, and WF_EVENT_T.

Usage Notes

WF_NOTIFICATION is invoked indirectly through the Workflow Engine whenever a Notification activity executes, and directly by the Workflow Notification System pages, the Worklist and Notifications Summary forms (OAF and Web), and the workflow mailer. Custom workflow developers typically call the companion package WF_NOTIFICATION from WF_NOTIFICATION-based activity functions or via WF_ENGINE APIs rather than invoking these internals directly. Because the object depends on 190 external references and is referenced by 190 other packages, modifications are high risk; functional changes should be implemented through the documented public routines and Oracle-supported APIs only.