BehnSusan ABCsOfWorkflowSetup PDF
BehnSusan ABCsOfWorkflowSetup PDF
BehnSusan ABCsOfWorkflowSetup PDF
Susan Behn
April, 2006
Table of Contents
Table of Contents......................................................................................................ii
Objectives ................................................................................................................1
Assumptions and Environment ...................................................................................1
Workflow Builder (Client)...........................................................................................2
Finding the most recent Workflow Builder Client ......................................................2
Installing the Workflow Builder Client ......................................................................3
Oracle Workflow (Server) ..........................................................................................7
Finding the most recent Workflow Server Patch .......................................................8
Finding Latest Workflow Information on MetaLink ....................................................9
Major Workflow Changes starting with OWF.G .........................................................9
Important Workflow MetaLink Notes........................................................................9
Oracle Workflow (Server) Setup...............................................................................10
Prerequisites ........................................................................................................10
Required Steps.....................................................................................................10
Workflow Configuration............................................................................................... 10
Profile Options ........................................................................................................... 15
Directory Services....................................................................................................... 17
Background Engines ................................................................................................... 24
Start Listeners............................................................................................................ 29
Business Event System ............................................................................................... 30
Optional Steps .....................................................................................................32
Partition Tables .......................................................................................................... 32
Additional Languages.................................................................................................. 34
Setup Notification Mailer ............................................................................................. 34
Setting an Override Notification Mailer Address ............................................................. 46
Responsibility Functions and Request Groups................................................................ 47
Vacation Rules ........................................................................................................... 48
Customize Logo.......................................................................................................... 49
Custom Icons............................................................................................................. 49
Verification Scripts................................................................................................49
Wfver.sql ................................................................................................................... 49
More Workflow Sessions and Training….................................................................59
Objectives
Workflow setup training will cover the following topics:
• Understand workflow components
• Understand steps to set up workflow environment using Oracle Applications Manager
• Understand scripts and steps required to verify workflow environment is configured
correctly
• Understand steps to set up workflow notification mailer
• Gain familiarity with optional setup steps
The training session will focus on setup steps required to run workflow in the Oracle
Applications Environment. Additional steps required to run workflow as a standalone application
will not be covered.
To find the most recent workflow client patches for releases prior to 10g, use the Advanced
Search on the Patches Tab on MetaLink. Choose product family “Workflow Client (wf)”, release
“Applications 11i” and patch type “Any”. Click the “Go” button.
As of April 3, 2006, the most recent patches for workflow are shown below. Although there is a
different patch listed for release 11.5.10, we have not observed any problem with using patch
4066964 for releases 11.5.9 or 11.5.10, so we recommend choosing the most recent patch.
If you expect to upgrade to 10g in the near term, consider installing the workflow client for 10g.
It will also work with other 11i releases on the Oracle9i database. The only disadvantage of
loading this version is it will install a 10g home on the client. If you have no other need for a
10g Oracle_Home, I would advise against using the additional space on your client and having
another Oracle_Home to manage.
The 10g version is not available on MetaLink. You must download this release from the OTN
website at the following link.
http://www.oracle.com/technology/software/products/workflow/index.html
Choose the Oracle Workflow Client Release 2.6.3.5 for Microsoft Windows.
Prior to installing Workflow Builder Client, it might be necessary to disable firewall products
such as Norton or McAfee. Some client product installations, particularly those installing an 8i
home, will actually require you to de-install McAfee, however, we have not yet observed this
problem with the Workflow Builder Client. If you have problems connecting to the database
after you have completed the installation process, you should look at potential conflicts with
your firewall software.
After your download is complete and you have extracted the files, go to Disk1 à Install à
win32 à setup.exe. This will start the Oracle Installer as shown below.
Click “Next”.
Do not install Workflow Builder in an existing $Oracle_Home used for other client products.
Workflow is very selfish. It wants its own $Home. Accept the defaults or change as desired,
then click “Next”.
Click “Next”. The summary page details what will be installed. You do not need to install the
Oracle XML Gateway Message Designer.
If this is the first time you have installed Oracle Workflow Builder, the Configuration Tools
window will appear after the installation of Workflow Builder is complete. This will help you
install the net services needed to access the Oracle database and will help you set up your
tnsnames file. If you have other Oracle client products, you can skip this step and copy the
tnsnames file from another home to the new Workflow Builder home.
To find the latest Oracle Workflow (OWF) patch, use the Advanced Search on the Patches Tab
on MetaLink. Choose product family “Workflow (owf)”, release “Applications 11i” and patch type
“Patch Set/Minipack”. Also choose your server platform where you have installed Oracle
Applications. Click the “Go” button.
To find the latest updates regarding workflow builder or workflow on the server, go to the
knowledge browser on MetaLink, choose “Workflow” in the alphabetical list of categories, and
click the “Go” button.
Release 11.5.9 was a transitional release for workflow. OWF.G was introduced in 11.5.9 which
included major changes to workflow. Some of the most significant changes are as follows:
• The java mailer is introduced replacing the c based mailer in earlier releases.
• The inbound mailer must be IMAP4 compliant.
• Oracle Applications Manager (OAM) is now used for setup and administration of
workflow including the workflow mailer.
• OWF.G with patch 3409889 introduces the SMTP outbound mailer in the database.
Setup of client software for outbound mail is no longer required.
• Workflow forms are now in the OA Framework (java) format. The old grey forms are
gone.
• Multi-org may be required depending on installed products. See MetaLink note 272292.1
• Generic Services Manager (GSM) must be running
• Web browser must support JavaScript and Frames
Required Steps
Workflow Configuration
The Global Preferences page shown below has been changed to Workflow Configuration and is
accessed via Workflow à Administer Workflowà Administration. This page is available on
multiple responsibilities such as Workflow Administrator Web Applications, Workflow
Administrator Web (New) and System Administrator, however, only users with workflow
administrator privileges can make changes to this page. The following sections describe how to
set the values on this page.
In 11.5.9 the default for the workflow administrator is * which gives everyone access to the
global preferences for workflow. It is very important to update this field on this release.
On releases prior to OWF.G, the Global Preferences page does not identify the workflow
administrator. To get this information use the following SQL statement:
TEXT
---------------
SYSADMIN
TEXT
---------------
FND_RESP|FND|FNDWF_ADMIN_WEB|STANDARD
Security groups are now part of the wf_admin_role. Therefore, in these releases, make sure the
correct value (one that includes the security group) is selected when updating the workflow
administrator.
Prior to 11i.ATG_PF.H Rollup Patch 3, there was a bug on the Workflow Configuration page
preventing updates to the workflow administrator from the workflow configuration form.
Additionally, the default value is set to an invalid value. Therefore, prior to applying this patch,
a SQL update is required to update the workflow administrator. This SQL statement and
additional details are provided in MetaLink note 308160.1. The SQL statements are also
included here for your reference.
To set the Workflow Administrator Web (New) responsibility to be the workflow system
administrator responsibility, execute the following SQL statement:
update wf_resources
set text = 'FND_RESP|FND|FNDWF_ADMIN_WEB_NEW|STANDARD'
where name = 'WF_ADMIN_ROLE';
OR
update wf_resources
set text = 'FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD'
where name = 'WF_ADMIN_ROLE';
If you have applied the RUP3 patch, click the flashlight next to the workflow administrator field.
Enter your search criteria and click the go button. Then choose a responsibility that includes the
security group.
Pick me!
LDAP
LDAP settings are for systems using single sign on. This allows the directories used by single
sign on to sync with directory services. Enter the following information for LDAP:
The system name is the name of the database where workflow server is installed. After
completing business event system setups, the status must be “Enabled” until the business event
system setups are complete. After completion, come back to this page and change this status if
necessary.
Global Preferences
Notification Style
The notification style specifies how workflow notifications should be sent. The user can override
these defaults in their individual preferences. For this reason, the workflow administrator should
periodically check user records for valid preferences. For example, if you have chosen not to
email the notifications, users should not change their notification preference to one of the email
options. This will cause workflow notification errors.
Additionally, if you choose one of the email options, users must have a valid email address and
the notification mailer must be set up. Setup of the notification mailer is covered later.
• HTML mail with attachments – notifications are in HTML format and include an attached
link to the Notification Details page. Users must read their email using an HTML email
client. Users can click buttons in the email to provide responses.
• Plain text mail with HTML attachments – notifications are in plain text format and
include an attached link to the Notification Details page and an attachment with the
HTML-formatted version of the notification. Users must type the exact text to respond.
Comments > 1 line must be enclosed in double quotes. Text of original email must be
excluded from the response. Details of notifications written using OA Framework are not
visible.
• Plain text mail – notifications are in plain text format. Users must type the exact text to
respond. Comments > 1 line must be enclosed in double quotes. Text of original email
must be excluded from response. Details of notifications written using OA Framework
are not visible.
• Plain text summary mail – Send a summary of all notifications as plain text email. Users
must use the Worklist pages to view and respond to notifications.
• Do not send me mail – Do not send the notifications as email. Users must use the
Worklist pages to view and respond to notifications. Use this setting until the workflow
notification mailer is set up.
• HTML mail – notifications are in HTML format but do not include the attached link to the
Notification Details page. Users must read their email using an HTML email client. Users
can click buttons in the email to provide responses.
• HTML summary mail – Send a summary of all notifications in HTML format with a link to
the Worklist page and links to each notification in the Notification Details page. Users
must use the Worklist pages to view respond to notifications.
• Disabled – Do not use this value for global preferences. Individual user preferences will
be set to “Disabled” when workflow tries to send a notification but does not find an
email address.
Note: Starting with RUP3, workflow will now put the notification in your worklist if there is no
email address without recording an error. Previously, a notification would be sent to sysadmin
stating the event failed and error records would exist even if the notification was acted upon
properly via the worklist.
The browser signing DLL location is the location of the Capicom.dll file that is used for Web
page operations with encryption in the Microsoft Internet Explorer browser. This preference is
required when using electronic signatures for notifications and using Internet Explorer to access
the applications. Update this value if Microsoft changes this location or if you choose to point to
a local copy of this file.
Profile Options
This profile option should be set to Y at the site level for workflow to perform efficiently. The
Generic Services Manager (GSM) automates the management of java processes. It will
automatically start and stop various services.
Server Timezone
Set the server timezone at the site level. Failure to set this profile option will prevent the
workflow monitor from opening.
This profile option specifies how you will allow recipients of notifications to pass responsibility
for that notification to other users. Valid values for WF: Notification Reassign Mode are
delegate, transfer or reassign.
Delegate: You can delegate notifications to other users, but you cannot reassign notifications.
Delegate allows another user to respond to a notification, but the original user will retain
ownership. Use this option to delegate authority while you are away from your job.
Transfer: You can transfer workflow notifications, which will sometimes also change the
hierarchy, but you cannot delegate. This options transfers ownership of the notification. Use
this option when you have received a notification for an action that falls outside your area of
responsibility.
Note: Prior to 11.5.10, this profile option is FND: Notification Reassign Mode.
Valid values are enabled or disabled. If enabled, this profile option allows the user to specify
“All” for vacation rules. If you are using Human Resources fully installed, it is not recommended
that you enable this feature. You should force the user to specify delegation or transfer of HR
notifications separately for privacy reasons.
Note: Prior to 11.5.10, this profile option is WF: Routing Rules – Allow All
Set this profile option to yes to allow electronic signing to occur only on plain text notifications.
Set the WF: GUEST Access to Notification profile option to Enabled at the site level to allow
users to access the worklist from the email notification without logging in to Oracle Applications.
This feature is not recommended due to security considerations.
This profile option must be set to a specific physical server address if the Application Framework
Agent profile option is set to a virtual or load balancing server.
This profile option specifies the mode to use when accessing a notification that was sent
without the access key. Valid values are Personal Home Page (PHP) or Portal.
Set the Socket Listener Port to a different value for each database to allow a user to open
multiple Forms sessions where each session is connected to different a database. This is no
longer required in 11.5.10. MetaLink note 272585.1 provides additional information about this
functionality.
Directory Services
This process synchronizes data from specific applications such as Human Resources with the
WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES tables. Run the Synchronize WF Local Tables
concurrent program daily for sources of data that are not automatically synchronized. Automatic
synchronization was introduced in 11.5.9 and completed in 11.5.10.
Prior to upgrading to 11.5.10, you should run this concurrent program and resolve all
synchronization errors. This process will not run in 11.5.10 for systems that are synchronized. If
you do not run this process prior to upgrade, errors must be manually resolved by updating
something in the source record.
MetaLink note 171703.1 provides the latest patches and additional information on directory
service synchronization.
Choose the original system data to be synchronized or “ALL.” If you are unsure which systems
must be synchronized, choose “ALL.” The process will only synchronize systems that are not
automatically synchronized.
If you have sufficient hardware resources, the number of parallel processes can be increased.
Otherwise, set this value to 1.
Set the logging mode to nologging to increase performance, but if the process fails, you will
need to rerun it.
In OWF.G, the option was added to choose a temporary tablespace. If this process fails with
ORA 1652 "unable to extend temp segment by %s in tablespace %s", choose a larger
temporary tablespace.
The wfdirchk.sql script, located in $FND_TOP/sql, will provide information associated with
directory services. Run this script as the apps user and resolve errors prior to upgrades and
prior to opening service requests if possible.
A partial sample output file is shown here. This script will typically return hundreds of pages
depending on your number of roles.
.
Orig System : FND_USR
------------------------------------------
Partition id : 1
Role view : NOBS
Migration of user/role data successful
User/Role view : NOBS
ERROR : Seeded view NOBS does not exist
Migration of user-role data successful
Bogus error
Role TL view NOBS
.
.
Orig System : PER_ROLE
------------------------------------------
Partition id : 3
Role view : PER_ROLE_ROLES_V
ERROR : Migration of user/role data unsuccessful : Please rerun Bulk
Synchronization for this Orig System and reverify
No User_Role view is defined for Orig System PER_ROLE Migration error – rerun
Orig System not MLS Enabled bulk sync
.
.
Orig System : POS
------------------------------------------
Partition id : 4
Role view : PQH_POS_ROLES
Migration of user/role data successful
User/Role view : PQH_POS_UR
Migration of user-role data successful
Orig System not MLS Enabled
.
.
Orig System : AMV_CHN
------------------------------------------
Partition id : 6
Role view : WF_AMV_CHN_ROLES
Migration of user/role data successful
User/Role view : WF_AMV_CHN_UR
Migration of user-role data successful
Orig System not MLS Enabled
.
.
.
Tables and indexes
Partitioned : YES
Table Space : APPS_TS_TX_DATA
Index Info
-----------
Index name : WF_LOCAL_ROLES_N2
Partitioned : YES
Table Space : APPS_TS_TX_IDX
Uniqueness : NONUNIQUE
.
.
…lots of additional pages
. Invalid names
(#,/,length > 30)
------------------------- Roles (Includes users) ------------------------
prompt
-- WF_ROLES: Invalid names
ERROR
1 row selected.
3 rows selected.
ffff
Invalid compound names
-- WF_ROLES: Invalid compound names
-- NAME <> <orig_system>:<orig_system_id>
ERROR :
1 row selected.
1 row selected.
Duplicate roles
no rows selected
Roles linked to the same original id
User Name User Sys U.System ID Role Name Role Sys R.System ID PARTITION_ID
------------- ---------- ------------ ------------- ---------- ------------ ------------
COMMS_ISTORE PER 5131 ~WF_ADHOC-460 WF_LOCAL_ROLES 0 0
NAME
------------------------------
ECX_SA
1 row selected.
Duplicate Roles
--Number of roles that qualify for purging (Make sure you run purge
--regularly!
COUNT(*)
----------
1385
1 row selected.
--Number of userroles that qualify for purging (Make sure you run purge
--regularly!
COUNT(*)
----------
2425
1 row selected.
Background Engines
The Workflow Background Engine is the background engine that runs workflow processes. At
least one background engine must be started to run workflow processes in the applications.
However, workflow will run more efficiently with additional background engines.
Background engines can be started through the concurrent manager or through OAM.
Minimum and Maximum Threshold: If you have workflows that are long running, the threshold
can be set to a high number in the workflow builder. You can run a separate background
engine during slower processing times for those workflows with a higher threshold.
Stuck workflows occur due to data errors or other conditions. Another reason a workflow will
become stuck is when an end node is not marked as an end node. When errors are resolved,
the workflow should be restarted so that it can move to the next step. It is not recommended
that this value be set to “Yes” for the background engine you have set to run every 5-20
minutes because there are often many “Stuck” workflows. A separate background engine
should be set up to run less frequently (once or twice per day) for stuck processes. This
background engine will attempt to restart all of these processes when the Process Stuck
parameter is set to “Yes” so this could cause a performance problem.
In summary, at a minimum start two background processes. One should run every 5-20
minutes with the parameters, null, null, null, yes, no, no. The second engine should run daily
with the parameters null, null, null, no, yes, yes. Add other background engines to manage
throughput as necessary depending on your installed products.
To start a background engine in the concurrent manager, submit a request for the Workflow
Background Process concurrent program and enter parameters as identified in the previous
section.
To start a background engine in OAM, click on the “Go” button next to Submit Request for
Background Engine.
Start Listeners
Start the Workflow Agent Listener Service container the first time you use workflow. Listeners
start workflow events and send notifications. The Workflow Agent Lister Services is the
container for several other listeners. These other listeners listed below will start automatically
when you start the Workflow Agent Listener Service container. The listeners shown below with
a status of “Running” are the listeners automatically started by the Workflow Agent Listener
Service container. The startup mode for the running listeners will be set to “Automatic.” Do not
change this setting.
To start the Workflow Agent Listener Service container, go to OAM à Workflow. Click on the
icon next to Agent Listeners or Service Components.
Select the Workflow Agent Listener Service, choose “Start” from the drop down list and click
“Go.”
If you plan to use the Workflow Notification Mailer to email notifications, return to this page and
start the Workflow Mailer Services after configuration of the Workflow Notification Mailer is
complete.
A queue is like a mailbox. The queue holds events or notifications. If it is an event, the
subscription will process the event. If it is a notification, the notification mailer will process the
notification. A queue is assigned to each agent listener. Oracle now sets up these queues
automatically. You should verify that the required queues are active in OAM. To check the
queue assigned to an agent listener, go to OAM and click on the icon next to Agent Listeners.
Choose and agent and click the “Edit” button.
Job_queue_processes handles propagation of the business event system event messages. The
default value is 2, however the recommended value is 10.
Run the concurrent program “Synchronize Product License and Workflow BES License” to
disable any business events for products not licensed at your site. If you are using the System
Administrator Responsibility as the Workflow Administrator, add this concurrent program to the
System Administrator request group.
If Control Queue Cleanup is scheduled, this icon next to Control Queue Cleanup in OAM will be
green. If not, schedule this concurrent program to run every 12 hours. Control Queue Cleanup
removes subscribers from the WF_CONTROL queue for processes that are not active. Processes
become inactive when a middle tier process dies. This will make the business event system run
more efficiently.
For additional details about the business event system, attend Karen Brownfield’s ABCs of
Workflow – Business Events Essentials on Thursday at 8:30am.
Optional Steps
Partition Tables
1. Run the Purge Obsolete Workflow Runtime Data concurrent request to purge the
maximum amount data possible in the workflow tables prior to partitioning. This will
speed up the partitioning process.
o WF_ITEMS
3. Verify that the free space in the tablespace that contains these workflow tables is
slightly more that what is currently in use including indices. The main reason the
partitioning process fails is due to lack of space.
4. Run the following script located in @$FND_TOP/admin/sql:
o sqlplus <apps user>/<apps pw> @wfupartb.sql <fnd_user> <fndusr pw>
<apps user> <apps pw>
o Example: sqlplus apps/appspw @wfupartb.sql applsys applsyspw apps appspw
Additional Languages
If additional languages are installed on the server, individual users can set their preferred
language from their workflow home page. They must also set the NLS_LANG environment
variable on their desktop. Changing this preference only translates the prompts.
Prerequisites
Create an email account for the mailer. It is strongly recommended that you do not use a user’s
email. It is an option, but additional setup is required. (See help in OAM for additional details.)
Create three folders for this email account named INBOX, PROCESSED and DISCARD. These
folders must be in uppercase. It is preferred that you treat this email account as if you have an
employee named WF mail. Make sure you can send email to and from this account and email is
not redirected. Ping the email server from the Oracle server to confirm communication is
working.
Step 1. Make sure the Startup Mode is “Automatic.” Accept the other default values on this
page and click “Next.”
Step 2.
Set the max error count to 100 as recommended in MetaLink note 300141.1.
The inbound and outbound thread counts default to 1 to allow both inbound and outbound
processing. If you choose to block responses to this email account, set the inbound thread
count to 0.
Until the notification mailer is tested and working properly, set the log level to “statement.”
This will provide detail information in the log. After the notification has been setup and verified,
change the log level to “error” to reduce space required by the logs. Accept the default values
for the remaining parameters and click “Next.”
Step 3.
Enter the mailer node name. This name must be in uppercase, contain no special character and
be 8 characters or less. This is the name of this notification mailer. It is included in outbound
notifications and is used in inbound notifications to determine which mailer should process the
message.
The email parser is the java class used to parse an incoming notification response. The default
email parser is oracle.apps.fnd.wf.mailer.TemplatedEmailParser. Do not change this value.
The alternate email parser is used if you set the DIRECT_RESPONSE parameter to Y. The
default value is oracle.apps.fnd.wf.mailer.DirectEmailParser. Do not change this value.
Check the Expunge Inbox on Close check box if you want processed or discarded messages to
be deleted when the email for the mailer is closed.
If responses will be allowed for this notification, enter the Inbound Email Account parameters.
The inbound server name is the host name for the server. You may optionally include the port
number using the format <server_name>:<port_number>. Otherwise, the mailer uses port
143. Do not specify the value “localhost.”
Enter the username and password of the mail account that was set up specifically for the
workflow mailer.
Accept the default values for the remaining parameters in the Inbound Email Account section.
The outbound server name is the host name for the server. You may optionally include the port
number using the format <server_name>:<port_number>. Otherwise, the mailer uses port
143. Do not specify the value “localhost.”
The test address, if assigned, is displayed here. In earlier versions, this is where you would
assign a test address for redirection of all outbound notification emails. New features and setup
for assigning a test address will be covered later.
Accept the default values for the remaining parameters in the Outbound Email Account section.
Accept the default values for the processed and discard folders. (You should have already
created these folders in your email account.)
Uncheck the Allow Forwarded Response check box if you prefer to force the responder to be
the recipient of the notification.
Click “Next.”
Note: If your parameters are valid, you can proceed to step 4. Otherwise, you will not be able
to proceed.
Step 4.
From is the value that appears in the “From” field of a message header.
Specify a full email address as the Reply-to Address. In RUP3, this address is validated for the
@ sign even if you are not allowing replies. If you are not allowing replies, enter
noreply@noreply.com.
The HTML Agent is the value of the “Applications Web Agent” profile option. This is the HTML
agent that handles notification responses.
Check the Autoclose FYI check box to automatically remove FYI notifications from the worklist.
Check the Reset NLS check box to allow the users to convert the NLS code set based on the
user’s preferences.
Check the Inline Attachments check box to display attachments in the body of the email.
Click “Next.”
Step 5.
If anyone is using one of the ‘Summary’ email notification preferences, schedule the time and
day to start sending summary emails and set the interval in minutes before restarting. 1440
minutes is 24 hours.
Optionally you can schedule start, refresh, suspend, resume or stop events for service
components. Typically this would only be required for custom service components.
Click “Next.”
Step 6.
This step is a replacement for the wfmail.tag file required by the c based mailer. Tags allow the
mailer to identify specific strings of text and respond appropriately. Consider adding a tag for
out of office emails with an action of “Ignore.”
Click “Next.”
Click the flashlight to select a role with an email address to test the mailer.
Verify the email was received and you can respond to the email. Then click “Next” to review the
summary page. If the settings are correct, click “Finish.”
For non-production instances, you should set an override mailer address to allow for testing of
notifications without sending notifications to users who may confuse them with production
notifications.
Note: This functionality has moved in RUP3 and now requires verification.
From the OAM Notification Mailer page, click the “View Details” button.
The mailer details page will appear. Click the “Set Override Address” button.
Enter the email address where you want to direct ALL notifications and click “Submit.”
New RUP3 functionality: You must wait until the email arrives for the override address. This
email will include a verification code which must be entered here. This prevents you from
setting an override email address to an invalid or incorrect address which could result in
sending an email with private information to an unintended recipient.
To clear the override address, go back to this page and click the “Clear Override Address”
button.
Add Worklist functions to other menus in System Administration à Application à Menu. The
function name is “Advanced Workflow Worklist.” The sub-menu is “Workflow User (New).”
Vacation Rules
The default list of item types a user can select when creating vacation rules displays those item
types for which the user has previously received at least one notification. To allow users to
create vacation rules for other item types, add the item type to the lookup code for the lookup
type "WF: Vacation Rule Item Types". In earlier releases, this lookup type was "WF: Notification
Rule Item Types.”
Note: Terminology has changed. Notification rules became routing rules, and is now vacation
rules.
Add items to the lookup code in the Application Developer Responsibility à Application à
Lookups à Application Object Library
Query for meaning “WF: Vacation Rule Item Types.” Add the item type and meaning for
workflows you would like to include in the list of values for vacation rules.
From the home page, the user can now set up vacation rules as shown below for the item type
you have defined.
Customize Logo
You can use your own logo that will appear on the workflow pages. Create a logo file named
FNDLOGOS.gif and store this file on the server in the virtual directory for OA_MEDIA.
Custom Icons
You can create custom icons to use in workflow builder that will subsequently appear in the
workflow monitor. Store the .ico files on the desktop for workflow builder in <oracle
home>/wf/icon. Convert the .ico files to .gif files and store on the server in the virtual directory
for OA_MEDIA.
Verification Scripts
Wfver.sql
This script will provide details critical to determining whether or not the workflow environment
in configured correctly. If you open a service request on MetaLink regarding any issue with
workflow, Oracle Support will ask you to run this script and send the results. Therefore, prior to
opening a service request, you should run this script and resolve any obvious problems first. For
example, at a minimum, check the following items:
A partial sample output file is shown here. This script will typically return over 25 pages.
SQL> @wfver.sql
Server Version (last official install)
Version
------------------------------
Workflow version
2.6.0
Status
----------
ENABLED
Local System Status
Name Value
------------------------------ -----------------------------------
aq_tm_processes 1
job_queue_processes 10
nls_language american
nls_territory america
XML Parser
XML Parser version (1) Version
(2) Status
Version
---------------------------------------------------
Oracle XML Parser 2.0.2.9.0 Production
Status Details
----------------------------------------------------------------------
INSTALLED and VALID in SYS Schema
INSTALLED and VALID in APPS Schema
Status Details
----------------------------------------------------------------------
/379229ed_javaxxmlparsersDocum INSTALLED and VALID in SYS Schema
/bc3b995a_javaxxmlparsersSAXPa INSTALLED and VALID in SYS Schema
README_xmlparser.txt INSTALLED and VALID in APPS Schema
xmlparser_2.0.2.1_production INSTALLED and VALID in APPS Schema
xmlparser_2.0.2.6_production INSTALLED and VALID in APPS Schema
xmlparser_2.0.2.7_production INSTALLED and VALID in APPS Schema
xmlparser_2.0.2.8_production INSTALLED and VALID in APPS Schema
xmlparser_2.0.2.9_production INSTALLED and VALID in APPS Schema
Queue Information
AQ$WF_CONTROL_R Rules:
----------------------------------
(none)
.
AQ$WF_DEFERRED_R Rules:
----------------------------------
Name: WF_DEFERRED, Rule: 1=1
.
.
.
no rows selected
PL/SQL Object
PL/SQL Version Information versions
WF Engine Status
OAUG Collaborate 06 Copyright 2006 Solution Beacon, LLC 54
Workflow Setup
Training
OAUG COLLABORATE 06 April 2006 Real Solutions for the Real World.
oracle.apps.wf.notification.send.group
Not Defined WF_NOTIFICATION_OUT@A510VIS1.S ENABLED
OLUTIONBEACON.NET
oracle.apps.wf.notification.send.group
wf_xml.SendNotification@A510VI Not Defined DISABLED
S1.SOLUTIONBEACON.NET
Type Class
-------------------- ----------------------------------------
BASE oracle.apps.fnd.cp.gsc.SvcComponent
WF_AGENT_LISTENER oracle.apps.fnd.wf.bes.AgentListener
WF_DOCUMENT_WEB_SERVICES oracle.apps.fnd.wf.ws.client.SOAPOutboun
dComponent
WF_JAVA_AGENT_LISTENER oracle.apps.fnd.wf.bes.AgentListenerNew
WF_MAILER oracle.apps.fnd.wf.mailer.Mailer
Service Components
no rows selected
--------------------------------------------------
Enabled
ICM Status
____________________________________________________________________________
ICM is running
Environment Variables
Concurrent-tier Environment
----------------------------------------------------------------------------
AFJVAPRG –
/oraappl/sb/a510vis1/a510vis1comn/util/java/1.4/j2sdk1.4.2_04/bin/java
AF_CLASSPATH –
/oraappl/sb/a510vis1/a510vis1comn/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/
oraappl/sb/a510vis1/a510vis1comn/util/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/oraa
ppl/sb/a510vis1/a510vis1comn/util/java/1.4/j2sdk1.4.2_04/jre/lib/charsets.jar
:/oraappl/sb/a510vis1/a510vis1comn/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.
.
.
.
11 rows selected.
End of wfver.sql