Oracle Workflow Developer's Guide Release 2.6.3 Part Number B10284-02 |
![]() |
![]() |
![]() |
![]() |
![]() |
||
Previous | Next | Contents | Index | Glossary |
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.
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.
To View the Details of a Notification (for Oracle Applications), Oracle Workflow User's Guide
NtfSignRequirementsMet, Oracle Workflow API Reference
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.
#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.
To View the Details of a Notification (for Oracle Applications), Oracle Workflow User's Guide
Previous | Next | Contents | Index | Glossary |