Search Results wf_msg_attr

Overview

WF_NOTIFICATION is the core PL/SQL package of the Oracle Workflow Notification System in Oracle E-Business Suite, owned by APPS and classified under the OWF product. It exposes the public APIs through which applications create, query, update, and respond to workflow notifications — the messages that the Workflow engine delivers to users, roles, and external recipients through the Worklist and e-mail channels. In releases 12.1.1 and 12.2.2 the package remains an active, supported (compatibility "S") business entity. Its documented scope is to "provide APIs to access the Oracle Workflow Notification System and manage notifications," making it the programmatic foundation beneath the Worklist web pages, the Notification Mailer, and the numerous application modules that raise or route business events. The specification also declares supporting constants and state used across these APIs: document presentation tags (doc_text, doc_html), the framework region and mailer page identifiers, cached NLS language, territory, and charset values, and global context variables (user, recipient role, original recipient, from role, new role, more-information role, proxy, and user comment) introduced to carry post-notification context.

Key Procedures and Functions

The package documents 88 procedures and functions. The attribute accessors are central and are frequently reached for by name, including the search term wf_msg_attr:

• WF_MSG_ATTR — resolves and returns the value of a named message attribute for a given notification or message context, providing the general-purpose hook by which callers read attribute data without knowing its storage type in advance.
• ADDATTR and the setters SETATTRTEXT, SETATTRNUMBER, and SETATTRDATE — attach a message attribute to a notification and populate it as character, numeric, or date data respectively.
• GETATTRINFO and the getters GETATTRTEXT, GETATTRNUMBER, GETATTRDATE, and GETATTRDOC — retrieve metadata about an attribute and its value as text, number, date, or document (URL/content) form.
• GETTEXT, GETURLTEXT, GETSHORTTEXT, GETSUBJECT, GETBODY, and GETSHORTBODY — return the rendered subject and body content of a notification, in full or summarized form, including substitution of any embedded URL text.
• GETINFO — returns consolidated information describing a notification, such as its status, recipient, and attributes.
• RESPONDER — records a recipient's response to a notification and advances the associated workflow activity.
• NTF_TABLE and SETFRAMEWORKAGENT — generate Browser Look and Feel (BLAF) compliant HTML tables for notification display and set the framework agent context for notification processing.

Tables Accessed

The package reads and writes the notification data model through APPS synonyms. It operates on WF_NOTIFICATIONS and WF_NOTIFICATIONS_S for notification records and their status history; WF_MESSAGES, WF_MESSAGE_ATTRIBUTES, and WF_MESSAGE_ATTRIBUTES_TL for message definitions and their translatable attribute values; WF_COMMENTS for recipient comments; and WF_AGENT_T and WF_EVENT_T for agent and event information. Workflow context is resolved from WF_ITEMS, WF_ITEM_TYPES, WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ACTIVITY_STATUSES_H, and WF_ACTIVITIES. Recipients and roles are resolved through WF_LOCAL_ROLES, and FND_LOOKUP_VALUES supplies lookup translations used in rendering.

Usage Notes

WF_NOTIFICATION is invoked throughout the EBS stack: application forms and OA Framework pages raise notifications through it, the Worklist and Notification Mailer render content via its GET* and NTF_TABLE routines, RESPONDER drives activity completion, and the attribute APIs (including WF_MSG_ATTR) are the standard means of populating and reading notification payloads from custom PL/SQL. Because the package is referenced by 190 other packages and marked public and active, customizations should call these documented APIs rather than manipulating WF_NOTIFICATIONS directly, preserving compatibility with both 12.1.1 and 12.2.2.