Search Results set_notif_message

Overview

JTF_TASK_WF_UTIL is a utility package in the Oracle E-Business Suite Task Management module (part of the CRM/TeleSales family, JTF schema) that integrates Oracle Tasks with the Oracle Workflow notification engine. Its central purpose is to build and dispatch Workflow notifications when a task is created, reassigned, or otherwise modified during its lifecycle. The package declares itself with AUTHID CURRENT_USER and carries a header revision stamp of 120.1.12000000.2 (2007), reflecting its long-standing role in the 11i through 12.2 code line. Constants such as jtf_task_wf_item_type ('JTFTASK') and jtf_task_main_process ('TASK_WORKFLOW') identify the Workflow item type and top-level process the package feeds. Rather than exposing business logic to end users, the package acts as the plumbing between task transaction APIs and the Workflow runtime, translating task state changes into notification messages addressed to the appropriate resources.

Key Procedures and Functions

The package documents five callable units, all oriented around notification preparation and delivery:

• DO_NOTIFICATION — A function that determines whether a notification should be raised for a given task. It returns a Boolean and is typically used as a gate so that notifications are only generated when task data satisfies the relevant conditions.
• CREATE_NOTIFICATION — The principal procedure that assembles and initiates a Workflow notification. Its signature accepts the triggering event, the task identifier, and a set of optional old/new owner and assignee values (resource id and type code pairs), plus old type, priority, and status values. These parameters allow the notification to describe what changed on the task so the message body and routing reflect the true nature of the event.
• SET_NOTIF_MESSAGE — Populates the notification message text (subject and body content) that will be delivered to the recipient. This is the procedure most commonly targeted by developers searching for set_notif_message, since it is the point at which the human-readable notification content is assembled.
• SET_NOTIF_PERFORMER — Establishes the performer, i.e., the Workflow role or user to whom the notification is addressed, drawing on assignment and resource data.
• SET_NOTIF_LIST — Assembles the notification recipient list, using the package's internal nlist_tbl_type collection of name, display name, and email address records to accumulate the addresses that will receive the message.

Tables Accessed

The package reads and writes a broad set of Task and Workflow tables through APPS synonyms. Core task data comes from JTF_TASKS_B (task base record), JTF_TASKS_TL (translated task text), and JTF_TASK_ALL_ASSIGNMENTS (owner and assignee assignments). Reference and descriptive values are resolved from JTF_TASK_PRIORITIES_TL, JTF_TASK_STATUSES_TL, and JTF_TASK_TYPES_B/TL, while JTF_TASK_WORKFLOW_PROCESS_S maps tasks to their workflow processes. Recipient identity and routing information is derived from JTF_RS_RESOURCE_EXTNS, JTF_RS_GROUP_MEMBERS, JTF_RS_TEAM_MEMBERS, and JTF_OBJECTS_B. Finally, the package interacts with the Workflow runtime tables WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_LOCAL_ROLES to create items, track activity status, and resolve role-based recipients.

Usage Notes

JTF_TASK_WF_UTIL is invoked indirectly rather than from standard concurrent programs or self-service forms. It is called by the Task Management APIs and by two other packages that reference it, whenever a task event warrants a workflow notification. Customizations and extensions that need to emit task notifications should call CREATE_NOTIFICATION (with DO_NOTIFICATION as an eligibility check) rather than manipulating Workflow tables directly. Developers overriding notification content or routing should target SET_NOTIF_MESSAGE, SET_NOTIF_PERFORMER, and SET_NOTIF_LIST. Because the package relies on current schema privileges and standardized Workflow item types, it should be exercised within the Task Workflow process context, and any modification should respect the JTFTASK item type and TASK_WORKFLOW process definitions to avoid breaking notification delivery in 12.1.1 and 12.2.2 environments.