Search Results home_float




Overview

WFA_HTML is the server-side PL/SQL package within the Oracle E-Business Suite Workflow (Workflow Agent, or WFA) architecture that renders the HTML pages comprising the Workflow web interface. It acts as the presentation layer for Workflow notification functions, generating the markup returned to a user's browser when they open the Worklist, read a notification detail, forward a notification, or respond to a notification. The package is declared with AUTHID CURRENT_USER and was last shipped under the version header wfhtms.pls 120.2.12010000.1 (2008/07/25), which corresponds to the 12.1.1 and 12.2.2 code lines.

WFA_HTML does not implement the business rules of Workflow itself; those reside in packages such as WF_NOTIFICATION and WF_CORE. Instead, WFA_HTML builds the user interface by emitting HTML through the Oracle Web Toolkit primitives (HTP and HTF) and by streaming document content through WPG_DOCLOAD. It maintains a small set of package-level constants, including image_loc defaulted to '/OA_MEDIA/', and two associative array types—name_array and value_array—used to hold complex name#type identifiers and their corresponding values read back from submitted web pages.

Key Procedures and Functions

ETRM 12.2.2 documents 33 procedures and functions in WFA_HTML. The principal presentation procedures include:

  • HOMEMENU — generates the menu shown on the Workflow home page, providing links to all other Workflow web interfaces. It accepts an optional message and an origin indicator.
  • HOME_FLOAT — the object referenced by the user's search term; it supports the floating home-page element/utility used alongside the Workflow home interface.
  • HOME — generates the Workflow home page itself, with an optional message argument.
  • LOGOUT — renders the logout page that terminates the user's Workflow web session.
  • HEADER — emits the standard Workflow page header, including styling and navigation context.
  • LOGIN — generates the login page. This page is only used to enable access when no external security is installed; normally users are authenticated by the chosen security system (Internet Computing, web server native, or similar) and access the notification pages directly. An i_direct argument was added per bug 1838410.
  • VIEWER — validates the user supplied on the login page and then displays the worklist.

The remaining documented procedures support the notification reading and response workflow: FIND, WORKLIST, DETAILFRAME, RESPONSEFRAME, FORWARDFRAME, ATTRIBUTEINFO, DETAIL, DETAIL2, DETAILLINK, SUBMITFORWARD, SUBMITRESPONSE, SUBMITSELECTEDRESPONSE, and FORWARDNIDS. Collectively they render the frames, detail views, attribute information, and submission targets that let a user act on one or many notifications.

Tables Accessed

WFA_HTML references its data through APPS synonyms. The Workflow tables it touches are WF_NOTIFICATIONS (the notification records being displayed or acted upon), WF_MESSAGE_ATTRIBUTES (message attribute metadata), and WF_NOTIFICATION_ATTRIBUTES (attribute values specific to a notification). It also uses the Oracle-supplied components DBMS_LOB and DBMS_SESSION, the DUAL table for singleton queries, HTF, HTP, and OWA_UTIL for HTML generation and CGI handling, PLITBLM for image storage, and WPG_DOCLOAD for streaming document content to the browser.

Usage Notes

WFA_HTML is not normally called directly by end users or by custom concurrent programs. It is invoked by the Workflow web pages and by the Workflow Agent (WF_WEB_AGENT) URL infrastructure, which resolves the base URL through wf_core.translate('WF_WEB_AGENT'). Because the procedures emit HTML directly to the HTTP response, they are typically reached through the Oracle Web Toolkit PL/SQL gateway. ETRM records that WFA_HTML is referenced by 36 other packages, indicating it is a widely depended-upon presentation utility. Customizations should avoid modifying the package in place; instead, the supported approach is to override page templates or use the Workflow customization framework, since changes here affect every Workflow web interface in the environment.