Search Results wf_standard




Overview
Explore in AI Chat

Overview

The APPS.WF_STANDARD package is the engine-level PL/SQL package that implements the core runtime primitives of the Oracle Workflow engine. It is the physical realization layer for the standard activity functions that the Workflow Builder exposes to designers as standard function activities — the join, branch, comparison, notification, wait, and process-launch operations that make up the majority of any workflow process definition. When a workflow process is executed, whether from a business event subscription, an HR approval transaction, or a concurrent program launch, the Workflow Engine resolves each activity node to its function and, for standard activities, executes the corresponding routine inside WF_STANDARD.

The package holds a VALID status in the APPS schema on both release 12.1.1 and 12.2.2, and is classified as an "OTHER" API in ETRM, meaning it is supported as an engine component rather than as a developer-facing business API. It depends directly on the SYS.STANDARD package and is referenced across a broad set of EBS application modules.

Key Procedures and Functions

The package documents 36 procedures and functions. Core engine control primitives include ABORTPROCESS, which terminates an active process instance, and LAUNCHPROCESS, which starts a child process from within a running activity. Branching and convergence are handled by ORJOIN and ANDJOIN, with FORKITEM spawning parallel branches and NOOP providing the pass-through activity used as a placeholder node.

Data manipulation activities include ASSIGN, which sets a workflow item attribute, and COMPARE, which evaluates a relational condition between item attributes. COMPAREEXECUTIONTIME performs temporal comparisons for time-based routing decisions.

Event integration is served by SETEVENTPROPERTY, GETEVENTPROPERTY, and COMPAREEVENTPROPERTY, which read and write attributes on the workflow event raised by the Business Event System.

Notification and human interaction are handled by NOTIFY, which generates a workflow notification to a role or user, and ROLERESOLUTION, which resolves role references to concrete performers. Timing and blocking activities are implemented by WAIT, BLOCK, and DEFER.

Error handling is provided by INITIALIZEERRORS, RESETERROR and CHECKERRORACTIVE, which collectively manage the error state recorded against an activity instance so that a failed node can be retried or repaired through the Workflow Monitor.

Tables Accessed

WF_STANDARD operates against the Workflow definition and runtime tables through APPS synonyms. It reads process structure from WF_PROCESS_ACTIVITIES, WF_ACTIVITIES, WF_ACTIVITY_TRANSITIONS, and WF_ACTIVITY_ATTR_VALUES to determine what to execute next. Runtime state is maintained in WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_PARAMETER_LIST_T.

Role and directory resolution uses WF_LOCAL_ROLES, WF_AGENTS, and WF_AGENT_T. Event-driven activities consult WF_EVENT_SUBSCRIPTIONS and WF_EVENT_T. Notifications are written to WF_NOTIFICATIONS, and configuration values are read from WF_RESOURCES and WF_SYSTEMS.

Usage Notes

WF_STANDARD is invoked by the Workflow Engine at runtime rather than called directly by end users. Custom workflow developers do not normally call its procedures; instead they select the corresponding standard function activity in Workflow Builder, and the engine dispatches to this package. It is also reached indirectly through the Workflow Function activity plumbing, evidenced by WF_FUNCTION_CALL referencing it.

Because ten documented packages depend on it — including ASO_APR_WF_PVT, HR_APPRAISAL_WORKFLOW_SS, HR_APPROVAL_SS, HR_DOR_REVIEW_SS, PAY_US_WORKFLOW_API_PKG, PAY_KR_WF_SUBMIT_PROGRAM_PKG, PER_RESPOWNER_UTIL_SS, and PV_WORKFLOW_PUB — customizations should avoid altering its specification. Any customization that requires behavior beyond the delivered primitives should be implemented as a separate PL/SQL package registered as a custom workflow function, leaving WF_STANDARD intact to preserve engine integrity across 12.1.1 and 12.2.2.