lab 1: amend your workflow › webfolder › technetwork › ... · lab 1: amend your workflow in...

of 12 Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Lab 1: Amend Your Workflow In this lab you will add two new states to the Alert Workflow that you created in the Publishing to Case Management training module. These new states will be called Remediated and Reopened respectively. You will also add a new parameter called ErrorStatus to your workflow, and new reception rules to transition to each of the new states depending on the value in the ErrorStatus parameter. Note that at this stage in proceedings the ErrorStatus parameter will have no value. The reception rules will not work until it is populated, which we will do in later labs.

Before You Start The labs in this module will only work if you have already completed the labs in the Publishing to Case Management module. If you have successfully completed the labs in the Publishing to Case Management module, and the configuration is still in your EDQ training environment, you can ignore the rest of this section, and move straight to the Navigate to the Launchpad section of this lab. If you completed the Publishing to Case Management module some time ago, and the configuration is no longer in your EDQ training environment, then complete this section before continuing to the Navigate to the Launchpad section of this lab.

Note that you are strongly advised not to attempt these labs unless you have already completed the Publishing to Case Management training labs.

1. If you haven’t already done so:

a) Set up an EDQ 12.1.3 training environment. Instructions for how to do this are online at http://tinyurl.com/edq-training-env.

b) If you are using the pre-built virtual machine as your training environment, follow the instructions in section 1.8 of the Virtual Machine Installation Guide to set up a shared folder (the Virtual Machine Installation Guide is available online at http://www.oracle.com/technetwork/middleware/oedq/edq-vm-install-guide-2424081.pdf).

c) Download the EDQ training data from http://www.oracle.com/webfolder/technetwork/tutorials/tutorial/edq/spt/universal-assets/edq_training_assets_12.1.3.zip.

d) Unzip the edq_training_assets zip file. If you are using the pre-built virtual machine, unzip this to the C:\share folder on your host machine.

2. If you are using the pre-built virtual machine as your training environment, copy the parts.csv file from the ~edq_training_assets_12.1.3\Data Files\Case Management to the following folder on the virtual machine: /apps/oracle/fmw/user_projects/domains/edq_domain/edq/oedq.local.home/landingarea

To do this, move to the desktop of the virtual machine, and double click the shortcut to EDQ landingarea folder. The shortcut to EDQ landingarea window will be displayed. Next, double click the share folder. Within the share folder, double click the edq_training_assets_12.1.3 folder, then, within that folder, double click the Data Files folder and then double click the Case Management folder. Drag the parts.csv file from

http://tinyurl.com/edq-training-env

http://www.oracle.com/technetwork/middleware/oedq/edq-vm-install-guide-2424081.pdf

http://www.oracle.com/technetwork/middleware/oedq/edq-vm-install-guide-2424081.pdf

http://www.oracle.com/webfolder/technetwork/tutorials/tutorial/edq/spt/universal-assets/edq_training_assets_12.1.3.zip

http://www.oracle.com/webfolder/technetwork/tutorials/tutorial/edq/spt/universal-assets/edq_training_assets_12.1.3.zip

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

of 12

the Case Management folder to the shortcut to EDQ landingarea folder.

3. If you are not using the EDQ-12.1.3-Trn2 virtual machine, copy the parts.csv file from the ~edq_training_assets_12.1.3\Data Files\Case Management to your EDQ instance’s landingarea.

Note that the landingarea is a sub-directory of the oedq_local_home

directory. The location of oedq_local_home can vary, depending on your machine’s operating system and the type of installation you have carried out.

On a Windows 7 machine, the default location of oedq_local_home is: C:\ProgramData\Oracle\Enterprise Data Quality\oedq_local_home.

4. Unzip the Model Solution - Publishing to Case Management.zip file that you will find in edq_training_assets_12.1.3\Model Solutions 12.1.3. This will create a folder called Model Solution - Publishing to Case Management.

5. Copy the flags.xml file from the Model Solution - Publishing to Case Management folder to your EDQ server’s oedq.local.home/casemanagement folder.

On the EDQ-12.1.3-Trn2 virtual machine this folder is located at

/apps/oracle/fmw/user_projects/domains/edq_domain/edq/oedq.local.home/casemanagement.

6. Restart the EDQ application server. To do this on the EDQ-12.1.3-Trn2 virtual machine, navigate to the virtual machine’s desktop, double click the Terminal icon to open a terminal window, type restart-edq-app-server and hit the Enter key on your keyboard. The EDQ application server may take several minutes to restart.


7. Import the Model Solution - Publishing to Case Management.dxi into EDQ using the Director UI. You will find the Model Solution - Publishing to Case Management.dxi file in the the Model Solution - Publishing to Case Management folder.

8. Import the following workflows, which you will find in the Model Solution - Publishing to Case Management folder, into EDQ using the Case Management Administration UI’s Workflow Administration:

a) Model Solution - Cases Workflow.dxic

b) Model Solution - Alerts Workflow.dxic

9. Import the Model Solution - Errors.dxic Case Source into EDQ using the Case Management Administration UI’s Case Source Administration. You will find Model Solution - Errors.dxic in the Model Solution - Publishing to Case Management folder.

Note that the project, workflows and case source will have different names to

those created in the Publishing to Case Management labs. This is deliberate:

it enables anybody experiencing difficulties with the Publishing to Case Management labs to import the model solution and compare it to their

configuration. These differences are set out below:

Project Name Cases Workflows Name

Alerts Workflow Name

Case Source Name

Publishing to Case Management Labs

Case Management Training

Cases Workflow Alerts Workflow Errors

Model Solution Model Solution – Publishing to Case Management

Model Solution – Cases Workflow

Model Solution – Alerts Workflow

Model Solution - Errors

If you have imported the model solution, please take these differences into

account as you complete the labs in this module.

10. In the Director user interface, expand the Model Solution - Publishing to Case Management project, and run both the PARTS Table snapshot and the Audit and Publish Errors to Case Management process.

Navigate to the Launchpad 1. If you are using the pre-built virtual machine as your training environment, open a web

browser on your host machine and navigate to the Launchpad at the following URL: http://localhost:8011/edq.

2. If you are not using the EDQ-12.1.3-Trn2 virtual machine, open a web browser and navigate to the EDQ launchpad. If you have installed EDQ locally on a Windows machine using the Quick Start installer, the URL is likely to be http://localhost:9002/edq.

http://localhost:8011/edq

http://localhost:9002/edq


of 12

Note that the Launchpad may take some time to display when you have just started the virtual machine (this is because the EDQ server is starting). Be

patient, and it should appear.

3. In your web browser, make the Launchpad web page a favorite or bookmark it so you can easily return to it in future.

Launch Case Management Administration Note that to launch the Case Management Administration user interface, you will need an up to date Java Runtime Environment (JRE) installed on your

host computer. You can download a Java Runtime Environment from http://www.java.com.

1. On the Launchpad, click the Case Management Administration link to launch the application. Allow any Java webstart confirmation boxes that may appear so that the client software can be downloaded. If you are asked whether you want to run the application, click Run. If a dialog box warns you that the Windows Firewall has blocked some aspects of the program, click Unblock.

2. The Login to localhost dialog will open. Login with the following credentials:

a. Username: dnadmin

b. Password: dnadmin

http://www.java.com/


dnadmin is a superuser. It has all the security privileges available in EDQ.

In a live environment, in which many users may interface with the same EDQ server, most users will have a more restricted set of privileges. However, in

the training environment, which is figuratively a sandpit, it will be useful for

you to enjoy unrestricted access to all EDQ functionality.

3. The Case Management user interface will open.

Add Two New States to Your Alerts Workflow: Remediated and Reopened

1. Double-click Workflow Administration. The Workflow Administration window will open.


of 12

2. Double-click your Alerts Workflow to open it in the Workflow Editor.

3. Click Add… The State window will open.

4. Enter a Name of Remediated.

5. Click OK to close the State window.

6. Click Add… The State window will open.


7. Enter a Name of Reopened.

8. Click OK to close the State window.

9. Click to save the Alerts Workflow.

Add the ErrorStatus Parameter to Your Alerts Workflow 1. Navigate to the Parameters tab, which is near the bottom of the Workflow Editor.

2. Click . The Parameter window will open.

3. Enter a Name of ErrorStatus


of 12

4. Ensure that the Enabled? checkbox is selected and click OK.

5. Click to save your workflow.

Add a Reception Rule to Transition to the Remediated State 1. Navigate to the Reception tab, which is near the bottom of the Workflow Editor.

2. Under the Transitions box, on the right-side of the screen, click Add… The Transition window opens.

Note that the transitions you add here are solely for use with reception rules.

3. Enter a Name of Error was found to be Fixed.

4. In the To State dropdown, select Remediated.


5. Click OK to close the Transition window. You are returned to the Workflow Editor.

6. Under the Actions box, on the left-side of the screen, click Add… The Action window opens.

7. Enter a Name of Set State to Remediated.

8. Enter a Condition of ErrorStatus == "Remediated".

9. In the Transition dropdown, select Error was found to be Fixed [Remediated].


of 12

10. Click OK to close the Action window. You are returned to the Workflow Editor.

Add a Reception Rule to Transition to the Reopened State 1. Under the Transitions box, on the right-side of the screen, click Add… The Transition

window opens.

Note that the transitions you add here are solely for use with reception rules.

2. Enter a Name of Error has Recurred.

3. In the To State dropdown, select Reopened.


4. Click OK to close the Transition window. You are returned to the Workflow Editor.

5. Under the Actions box, on the left-side of the screen, click Add… The Action window opens.

6. Enter a Name of Set State to Reopened.

7. Enter a Condition of ErrorStatus == "Recurred".

8. In the Transition dropdown, select Error has Recurred [Reopened].


of 12

9. Click OK to close the Action window. You are returned to the Workflow Editor.

10. Click to save your Alerts Workflow.

11. Close the Workflow Editor.

lab 1: amend your workflow › webfolder › technetwork › ... · lab 1: amend your workflow in...

Documents