Previous	Next		Contents	Index	Glossary

If you are using the Oracle Applications Framework-based version of the Worklist pages available with Oracle Workflow embedded in Oracle Applications, you can use a special message attribute with the internal name #WF_SIG_POLICY to require that a user's response to a notification be authenticated by an electronic signature. This electronic signature is analogous to a written signature. If you define a notification to require a password-based signature, users must respond to the notification from the Notification Details web page and must confirm their response by entering their Oracle Applications user name and password. Otherwise, the response will not be considered valid.

The #WF_SIG_POLICY attribute must be either of type text or lookup. To require a password-based signature, set the value of the #WF_SIG_POLICY attribute to PSIG_ONLY. If you set the value to DEFAULT, leave the value blank, or if you do not define a #WF_SIG_POLICY attribute for the message, Oracle Workflow performs the default response processing that does not require a signature.

You can either specify PSIG_ONLY as a constant value for the #WF_SIG_POLICY attribute, or specify an item type attribute as the value and include logic in your workflow process that dynamically determines at runtime whether a password should be required or not and sets that item type attribute to either PSIG_ONLY or DEFAULT, respectively.

Note: The Oracle Workflow web pages are being converted to the Oracle Applications Framework user interface format. Depending on your version of Oracle Workflow and which patches you have applied, you may see Oracle Workflow web pages in the new format or in the previous format. The new Worklist pages that support password-based electronic signatures are currently available for the version of Oracle Workflow embedded in Oracle Applications.

However, Oracle Workflow supports password-based electronic signatures only if you are maintaining your Workflow directory service based on Oracle Application Object Library users and passwords. This option is not currently supported if you are integrating with Oracle Internet Directory (OID) to maintain your directory service.

In future releases, Oracle Workflow will support other types of electronic signatures, using the #WF_SIG_POLICY attribute with other values.

See Also

To View the Details of a Notification (for Oracle Applications), Oracle Workflow User's Guide

NtfSignRequirementsMet, Oracle Workflow API Reference

#WF_SIG_ID Attribute

If you are using the Oracle Applications Framework-based version of the Worklist pages available with Oracle Workflow embedded in Oracle Applications, you can specify an electronic signature policy for notifications by defining the #WF_SIG_POLICY message attribute. If you specify a signature policy that requires an electronic signature to validate a user's response to a notification, Oracle Workflow creates another message attribute named #WF_SIG_ID after the notification is signed. The #WF_SIG_ID attribute stores the identifier for the signature, which you can use to reference information about the signature later if necessary. This attribute is of type text and has a source of 'Respond'.

Note: Oracle Workflow automatically creates and sets the value of the #WF_SIG_ID attribute when a user submits a response to a notification with an electronic signature. You do not need to manually create or set this attribute.

Header Attributes

If you are using the Oracle Applications Framework-based version of the Worklist pages available with Oracle Workflow embedded in Oracle Applications, you can use special header message attributes to display key information in the notification header region of the Notification Details page. Header attributes are also displayed at the beginning of e-mail notifications. To identify a message attribute as a header attribute, you must define an internal name for it that begins with #HDR_

using the following format:

#HDR_<name>

The display order of any header attributes in the Notification Details page or the e-mail notification is determined by the sequence of those attributes within the navigation tree in the Workflow Builder. The display name of each header attribute will appear as a label before the attribute value in the notification header region. You can either specify a constant value for each attribute, or specify an item type attribute as the value and include logic in your workflow process that dynamically sets the item type attribute value at runtime.

Note: The Oracle Workflow web pages are being converted to the Oracle Applications Framework user interface format. Depending on your version of Oracle Workflow and which patches you have applied, you may see Oracle Workflow web pages in the new format or in the previous format. The new Worklist pages that support header attributes are currently available for the version of Oracle Workflow embedded in Oracle Applications.

See Also

To View the Details of a Notification (for Oracle Applications), Oracle Workflow User's Guide

Copyright © 2003 Oracle Corporation.
All rights reserved.