Before You Begin
Purpose
This tutorial demonstrates how to create and configure a workflow model with conditional stages in Oracle Data Relationship Governance.
Time to Complete
Approximately 30 min.
Background
Workflow models control the user tasks, stages of workflow, and types of data involved to govern a particular set of changes to data in Oracle Data Relationship Management. Each workflow model consists of multiple workflow stages that define approvals and enrichment steps required before the changes can be committed to a version. When a stage is assigned to a workflow model, the stage type attribute defines the type of participation for users in that stage of the workflow.
Stages can have conditions that allow altering the workflow path of a particular request based on specified criteria evaluated for the request items. Stages with conditions define what action should be taken if the condition is met, for example whether a request can enter the stage or if some of the request items are split off into a separate request.
Scenario
In this tutorial, you create workflow tasks and a workflow model with conditional stages for a change request process to add a financial account. The workflow model consists of five stages:
- The Submit stage that defines the initial request items to be included in a request.
- An Enrich stage that enables the user to set values for the request item properties, Allow Posting and Allow Budgeting, that control which workflow stages the request must go through in order to be commited to the version.
- Two conditional Enrich stages that are included in the workflow path of the request based on values set for the Allow Posting and Allow Budgeting properties in the first Enrich stage.
- The Commit stage that is used for final approval and commitment of all performed workflow tasks.
Context
After building the workflow model by completing this tutorial, you create a multi-item change request. You load the request items from a source file and submit the request for enrichment and approval by other users by following steps outlined in the Loading Request Items tutorial.
What Do You Need?
Before starting this tutorial, you should:
- Have access to or have installed Oracle Data Relationship Management 11.1.2.4.311.
- Have access to or have installed the COAMGT Data Relationship Management application. You can download the application here and use these instructions to install and configure the application.
Logging On to Data Relationship Management
-
Launch Data Relationship Management Web Client.
The logon page for Oracle Data Relationship Management is displayed.
-
Log on to the COAMGMT application as user admin with a password of Welcome!.
The Browse page is displayed on the Home tab.
Creating Workflow Tasks
Workflow tasks are building blocks of workflow models. Each workflow task defines a single set of changes performed for a local node; it consists of an action type, properties to be viewed or edited, and validations. In this section, you create three workflow tasks that will be used to define the Enrich stages in the workflow model later in this tutorial.
Creating the General Ledger Account Setup Task
In this section, you create a workflow task to set up a financial account in the General Ledger.
-
On the Home tab, select the Administer task group.
-
In the New drop-down list, select Workflow Task.
The New Workflow Task tab is displayed.
-
Enter the following values for the new workflow task:
- Name:
GL Account Setup
- Label:
GL Account Setup
(this is the default value) - Instructions:
Set up a financial account in the General Ledger.
- Action Type:
Update
Note that there are no default properties selected for the Update action type.
- Name:
On the Properties tab, verify that System is selected in the Property Category drop-down list, select the Description, Name, and Parent Node properties, and then click the Select button ( ) to select the properties.
On the Properties tab, from the Property Category drop-down list select Oracle General Ledger.
-
In the Available list, select the Account Type, Allow Posting, Allow Budgeting, Enabled, End Date, Start Date, and Financial Category properties. Click the Select button ().
-
In the Action column for the Description property, click the Edit button ().
-
Select the Required option. Notice that the Editable option is selected automatically.
Click the Update button ().
-
Repeat steps 7 through 9 to configure the Editable option and the Required option for the remaining properties as specified in the following table:
Label Editable Required Name True True Parent Node False False Account Type True True Allow Posting True True Allow Budgeting True True Enabled True True End Date True False Start Date True False FInancial Category True False -
Reorder the selected properties list:
Select the Name property and click the Move Up button () to place it to the top of the list.
Select the Start Date property and click the Move Up button () to place it before the End Date property in the list.
Click the Save button ().
The workflow task is saved and the tab is renamed to GL Account Setup.
-
Close the GL Account Setup tab. You are navigated back to the Home tab displaying the Administer task group.
Creating the Insert Financial Account Task
In this section, you create a workflow task to insert a financial account into the All Accounts hierarchy.
-
On the Home page for the Administer task group, select Workflow Task from the New drop-down list.
The New Workflow Task tab is displayed.
-
Enter the following values for the new workflow task:
- Name:
Insert Financial Account
- Label:
Insert Financial Account
(this is the default value) - Instructions:
Insert a financial account into the All Accounts hierarchy.
- Action Type:
Insert
- Name:
-
On the Properties tab, verify that the Parent Node property is selected.
-
On the Properties tab, from the Property Category drop-down list select Financial Management.
-
In the Available list, select the Account Type, Alias, Custom 1 Top Member, Enable Custom 1 Aggregation, Security Class, and Uses Line Items properties. Click the Select button ().
-
Configure the Editable option and the Required option for the selected properties as specified in the following table:
Label Editable Required Parent Node True True Account Type True False Alias False False Custom 1 Top Member True False Enable Custom 1 Aggregation True False Security Class True False Uses Line Items True False Click the Save button ().
The workflow task is saved and the tab is renamed to Insert Financial Account.
-
Close the Insert Financial Account tab. You are navigated back to the Home tab displaying the Administer task group.
Creating the Update Planning Task
In this section, you create a workflow task to update property values for Planning and Budgeting.
-
On the Home page for the Administer task group, select Workflow Task from the New drop-down list.
The New Workflow Task tab is displayed.
-
Enter the following values for the new workflow task:
- Name:
Update Planning
- Label:
Update Planning
(this is the default value) - Instructions:
Update property values for Planning and Budgeting.
- Action Type:
Update
Note that there are no default properties selected for the Update action type.
- Name:
-
On the Properties tab, from the Property Category drop-down list select Planning.
-
In the Available list, select the Account Type, Aggregation (Plan 1), Alias, Data Storage, Data Type, Exchange Rate Type, Formula, Skip Value, Smart List, Source Plan Type, Time Balance, Two Pass Calculation, User Defined Attribute, Valid for Plan (Plan 1), and Variance Reporting properties. Click the Select button ().
-
Configure the Editable option and the Required option for the selected properties as specified in the following table:
Label Editable Required Account Type True True Aggregation (Plan 1) True False Alias False False Data Storage True False Data Type True False Exchange Rate Type True False Formula True False Skip Value True False Smart List True False Source Plan Type True False Time Balance True False Two Pass Calculation True False Use Defined Attribute True False Valid for Plan (Plan 1) True False Variance Reporting True False Click the Save button ().
The workflow task is saved and the tab is renamed to Insert Update Planning.
-
Close the Update Planning tab. You are navigated back to the Home tab displaying the Administer task group.
Building a Workflow Model
Creating a Workflow Model
-
On the Home page for the Administer task group, select Workflow Model from the New drop-down list.
The New Workflow Model tab is displayed. On the Workflow Stages tab, note that there are two default stages (Submit and Commit) that are required in every workflow model.
-
Enter the following values for the new workflow task:
- Name:
New Financial Account - Conditional
- Label:
New Financial Account - Conditional
(this is the default value) - Description:
Define a new financial account for general ledger accounting purposes.
- Request Duration:
5
- Claim Duration:
1
- Hidden: unchecked
- Name:
Defining the Submit Stage
The Submit stage is always the first stage of a workflow model; it defines the initial request items to be included in a request.
-
For the Submit stage in the Action column, click the Edit button ().
The Submit stage row is enabled for editing.
-
On the Stage tab, configure the Submit stage using the following values:
- Label:
Define Financial Account
- Task:
Add Financial Account
- Re-Approval:
All
(a pushed back request must be approved by all stages after it) - Notify:
Assignees
(users assigned to the stage are notified of activity in that stage) - Separation of Duties:
unchecked
- Label:
On the Node Access Groups tab, select Vision Workflow.
-
Click the Update button () to save the changes.
Defining the First Enrich Stage
The first Enrich stage enables the user to set values for request item properties, Allow Posting and Allow Budgeting, that control which workflow stages the request must go through in order to be commited to the version.
-
Click Add Stage.
-
On the Stage tab, configure the new stage using the following values:
- Label:
General Ledger Setup
- Workflow Method:
Any Group
(any group assigned can approve, only one approval required) - Type:
Enrich
(users can approve or reject the request as well as edit it) - Task:
GL Account Setup
- Re-Approval:
All
(a pushed back request must be approved by all stages after it) - Notify:
None
- Separation of Duties:
unchecked
- Label:
-
On the Node Access Groups tab, select W_ApproveAccount.
-
Click the Update button () to save the changes.
Defining Conditional Enrich Stages
Two conditional Enrich stages, Insert into Consolidations and Update Planning Application, define the workflow path of the request based on values set for the Allow Posting and Allow Budgeting properties in the first Enrich stage.
-
Click Add Stage. On the Stage tab, configure the new stage using the following values:
- Label:
Insert into Consolidations
- Workflow Method:
Any Group
- Type:
Enrich
- Re-Approval:
All
- Task:
Insert Financial Account
- Notify:
None
- Separation of Duties:
unchecked
- Label:
-
On the Node Access Groups tab, select Consolidation Workflow.
-
On the Condition tab, configure the stage condition that evaluates the Allow Posting property value that is managed by the Enrish user in the General Ledger Setup stage. From the Type drop-down list, select Property Criteria to and click Add. Select Allow Posting from the Property list, Equal from the Operator list, type True in the Value field, and click the Update button ().
-
The stage is also configured with the Enter Stage conditional action. If request items in a request meet the condition, the request will enter the stage and the Insert Financial Account task is performed. Otherwise, the request will skip the stage and proceed to the next stage in the workflow.
-
Click the Save button ().
-
Click Add Stage. On the Stage tab, configure the new stage using the following values:
- Label:
Update Planning Application
- Workflow Method:
Any Group
- Type:
Enrich
- Re-Approval:
All
- Task:
Update Planning
- Notify:
None
- Separation of Duties:
unchecked
On the Node Access Groups tab, select Planning Workflow.
On the Condition tab, configure the stage condition that evaluates the Allow Budgeting property value that is managed by the Enrish user in the General Ledger Setup stage. From the Type drop-down list, select Property Criteria to and click Add. Select Allow Budgeting from the Property list, Equal from the Operator list, type True in the Value field, and click the Update button ().
- Label:
-
From the Action drop-sown list, select Split Request Items to configure the stage so that request items in a request that meet the condition will be split into a separate request which will enter the stage. Any request items that so not meet the stage condition will stay in the original request and the request will skip the stage and immediately proceed to the next stage.
-
Click the Save button ().
Defining the Commit Stage
The Commit stage is always the last stage of the workflow model; it is used for final approval and commitment of all performed workflow tasks.
-
For the Commit stage in the Action column, click the Edit button (). On the Stage tab, configure the Submit stage using the following values:
- Label:
Commit Financial Account
- Workflow Method:
Any Group
- Notify:
Participants
(previous participants of the request are notified) - Separation of Duties:
selected
(prevents any participating user in a previous stage from claming the request and requires a separate user in the stage to approve the request)
- Label:
-
On the Node Access Groups tab, select COA Manager Workflow and click the Update button () to save the changes.
Click the Save button ().
The workflow model is saved and the tab is renamed to New Financial Account - Conditional.