home Workflow Notes Templates WF Scripts

Setup Workflow

1. Setup the Default Oracle Workflow user Preferences globally using the workflow configuration page. 
2. Change the Workflow administrator role from SYSADMIN to system administrator (or whatever user or role you'd like, 
    use * for all users) on the workflow configuration page
       FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD
3. Setup Directory Services

4. Set up background Workflow Engines to 

5. Setup the Business Event System - nothing to do here really


Optional Steps

1. Partition the  WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ACTIVITY_STATUSES_H, WF_ITEM_ATTRIBUTE_VALUES, and
WF_ITEMS tables for performance gain. 2. Set up the Workflow Mailer 3. Modify the email templates 4. Give users access to the advanced worklist and Personal Worklist 5. WF: Notification Reassign Mode profile option to control which
reassign modes are available to users from the Notification Details page 6. WF: Enable Bulk Notification Response profile option to specify
whether users can respond to a group of notifications collectively from the Worklist
and Notification Search pages
Important Note:
If the notification mailer cannot deliver an e-mail notification because the recipient's e-mail address is invalid, it performs the following actions:

• Sets the mail status of the notification to FAILED. This mail status indicates that an exception prevented this e-mail notification from being delivered but does not prevent the mailer from processing other notifications.

• Adds the e-mail address to its invalid e-mail address list. To avoid unnecessary processing, each notification mailer stores a list of e-mail addresses to which it could not deliver messages, and does not attempt to send any further messages to those addresses

• Instead, for any subsequent notifications to the listed addresses, the notification mailer simply sets the mail status directly to FAILED.

 

 
Workflow Sql 
--Set the Workflow System administrator preference to the internal name of the workflow role associated with that responsibility

select name, display_name
from wf_roles
where display_name like '%Admin%';
--To find which role currently has workflow adminstrator privileges without accessing the Workflow Configuration Page

select text 
from wf_resources
where name = 'WF_ADMIN_ROLE';

 

table    
WF_USERS

individual users

is based on WF_LOCAL_ROLES where the user flag is set to Y and on WF_LOCAL_ROLES_TL.
WF_ROLES Roles, which can have one or more members is based on WF_LOCAL_ROLES and on WF_LOCAL_ROLES_TL.
WF_USER_ROLES

Associations for users with roles of which they are members. A role cannot contain another role

is based on WF_LOCAL_USER_ROLES
WF_USER_ROLE_ASSIGNMENTS

Assignments of users to roles, both direct aand inherited through role hierarchy relationships

is based on WF_USER_ROLE_ASSIGNMENTS.
WF_LOCAL_ROLES The only roles in WF_LOCAL_ROLES that are marked as individual users with the user
flag set to Y are roles that represent Oracle Applications users, originating from the
FND_USER table, roles that represent Oracle Trading Community Architecture (TCA)
person parties, roles that represent TCA contacts (relationship parties), or roles that
represent ad hoc users

The WF_LOCAL_USER_ROLES table is used
to associate Oracle Applications users, TCA person parties, and TCA contacts with roles
defined by other applications.

An Oracle Applications user may be associated with an Oracle Human Resources person. In this case, some person information is combined into the user's record in WF_LOCAL_ROLES. In such a combined record, the originating system is changed from FND_USR to PER, and the display name is taken from Oracle Human Resources, while the internal name is the Oracle Applications user name from
FND_USER, and the user flag is still set to Y.

WF_LOCAL_USER_ROLES   WF_USER_ROLES is based on WF_LOCAL_USER_ROLES.

 

Oracle Applications Users and Oracle Human Resources People in WF_LOCAL_ROLES

Type Of Role Orig_System User_Flag
Oracle Applications user, not linked to an Oracle Human Resources person FND_USR
Y
Oracle Applications user linked to an Oracle Human Resources person PER
Y
Oracle Human Resources person PER_ROLE
N

Incremental Synchronization – Automatically synchronizes on an incremental basis
Bulk Synchronization – You can run if necessary =
Synchronize WF LOCAL Tables –
Orig System – All
Parallel Processes –
Loggin Mode – Determines wheather redo log data is generated by bulk sync. Default is logging, Optionally set to NOLOGGING
Temporary TAblespace –
Raise Errors – Select Yes or No – default is Yes

Validating Directory Service Information- Workflow Directory Services User/Role Validation
P_BatchSize
P_Check_Dangling – Yes to check that all users/roles referenced by user/role associations exist in the WF_LOCAL_ROLES table. If user/role are missing for any user/role association, the program removes that user/role association.

You should run the script wfdirchk.sql to validate your directory service data
model. This script is located in the $FND_TOP/sql directory. See: Wfdirchk.sql,
page 9-10.

 

Background Engine Queues

Queue Table

Queue Name

Payload Type

Retention Time

Description

WF_DEFERRED_QUEUE_M WF_DEFERRED_QUEUE_M SYSTEM.WF_PAYLOAD_T 0 days  Standard background deferred queue
WF_OUTBOUND_QUEUE WF_OUTBOUND_QUEUE SYSTEM.WF_PAYLOAD_T 0 days  Standard background outbound queue
WF_INBOUND_QUEUE WF_INBOUND_QUEUE SYSTEM.WF_PAYLOAD_T 0 days  Standard background inbound queue

The e-mail notifications are based on message templates defined in Oracle Workflow
Builder. Oracle Workflow provides a set of standard templates in the System:Mailer item type, which are used by default.

It is not recommended to modify the standard templates. However, you can customize the message templates used to send your e-mail notifications by creating your own custom message templates in a custom item type using the Workflow Builder.

Then assign these templates to a particular notification in a workflow process by defining special message attributes. In this case the templates assigned to the notification override any other templates.

See: Modifying Your Message Templates, page 2-86 and Notification Mailer Message Template 1Attributes, Oracle Workflow Developer's Guide.

You can also create your own custom message templates in the System: Mailer item
type using the Workflow Builder, and assign these templates to a particular notification
mailer service component in the mailer configuration parameters. The templates
assigned to a mailer override the default System: Mailer templates. However, if any
notifications have templates specifically assigned to them through message attributes,
the notification-level templates still override the templates assigned to the mailer. See:
Modifying Your Message Templates, page 2-86.

If the notification mailer cannot deliver an e-mail notification because the recipient's
e-mail address is invalid, it performs the following actions:

• Sets the mail status of the notification to FAILED. This mail status indicates that an exception prevented this e-mail notification from being delivered but does not prevent the mailer from processing other notifications.
• Adds the e-mail address to its invalid e-mail address list. To avoid unnecessary processing, each notification mailer stores a list of e-mail addresses to which it could not deliver messages, and does not attempt to send any further messages to
those addresses.

• Instead, for any subsequent notifications to the listed addresses, the notification mailer simply sets the mail status directly to FAILED.

Note: Each notification mailer can store up to 100 e-mail addresses in its invalid e-mail address list. If the notification mailer encounters additional invalid addresses when the list is already full, the notification mailer removes the oldest addresses from the list and adds the new addresses in their place.

Also, the notification mailer clears the list by removing all addresses whenever you stop and restart the mailer.• Sends a notification to the SYSADMIN user with the information that an e-mail notification could not be sent to one or more recipients, that the notification preference for those recipients has been set to DISABLED, and that those recipients' original notification preferences, which are listed, should be reset after the issues that caused the failures are corrected. See: User Notification Preference Update Report Message, page 2-138.
After correcting invalid e-mail addresses and resetting DISABLED notification preferences, you can run the Resend Failed/Error Workflow Notifications concurrent
program to retry open notification

 

It is not recommended to modify the standard templates. However, you can optionally
customize the message templates used to send your e-mail notifications by either using
the alternative templates provided in the System: Mailer item type by Oracle Workflow,
or creating your own custom message templates in the System: Mailer item type using
the Workflow Builder. You can implement alternative standard or custom templates in
the following ways:

These message templates are defined in the System: Mailer item type.

The value for a message template attribute must be specified in the following format:
<item_type_internal_name>:<message_internal_name>
For example, to specify the Workflow Open Mail (Templated) message within the
System: Mailer item type, you would enter the following value:
WFMAIL:OPEN_MAIL
You can either specify a constant value for a message template attribute, or specify an

You can define the following attributes to specify templates to be used for a notification
message at various stages in e-mail notification processing.
• #WFM_OPEN_MAIL - Specify the template to use for e-mail notifications that require
a response, if you are using the templated response method

 


• Assign the templates you want to a particular notification mailer service component
in the mailer configuration parameters. The templates assigned to a mailer override
the default System: Mailer templates. See: Notification Mailer Configuration
Wizard, page 7-31.
• Assign the templates you want to a particular notification in a workflow process by
defining special message attributes. In this case the templates assigned to the
notification override both the templates assigned to a mailer and the default
System: Mailer templates. See: Notification Mailer Message Template Attributes,
Oracle Workflow Developer's Guide.

You can customize the boilerplate text that appears in the body of the Workflow Open
Mail (Templated) message, where attributes preceded by an ampersand (&) are token
substituted with runtime values when the notification is sent.
The boilerplate text for a plain text message body is as follows:
Oracle Workflow Notification
&TIMEZONE
______________________Start of Response Template______________________
Response Template for &NOTIFICATION
To submit your response, reply to this message, including this response
template with your reply. Copy and paste from this message if
necessary to obtain an editable copy of the template. Insert your
response value between the quotes following each response prompt.
&RESPONSE
______________________End of Response Template_______________________
Notification Details:
&HEADER
&BODY
Due Date: &DUE_DATE
&HISTORY
The boilerplate text for an HTML-formatted message body is as follows:
<HTML> <HEAD> <TITLE> Oracle Workflow Notification </TITLE>
<STYLE>
<! -
&TEMPLATE_STYLE
- >
</STYLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" >
<P><SPAN class="OraTipLabel">&TIMEZONE</SPAN>
<P>&HEADER
<P>&BODY
<P>Please click on one of the following choices to automatically
generate an E-mail response. Before sending the E-mail response to
close this notification, ensure all response prompts include a
desired response value within quotes.
<P>&MAILTO
<P>&HISTORY
</BODY>
</HTML>