Lab 5: Delete What You Won t Need from the Publish Process

(1)

Lab 5: Delete What Yo

Process

You have now created the groundwork that you need to build a process that will deal with remediation at source. In the following

completely from scratch. Instead you will adapt the process.

Open the Process, and Delete What you Don’t Need

1. If any other processes are already open on the them to avoid possible confusion.

2. In the Project Browser, on the left

2.Publish Alerts to Case Management

3. On the canvas, delete all of the processors

4. Delete the line connecting the Reader to the Advanced Match processor (but do not delete the processors themselves).

5. On the canvas, double-click the word

Records.

6. On the canvas, double-click the words

Publish to Case Management (Advanced Match)

7. Click to save the process.

Delete What You Won’t Need from the

You have now created the groundwork that you need to build a process that will deal with

the following labs, you will build that process. You will not work completely from scratch. Instead you will adapt the 2.Publish Alerts to Case Management

Open the Process, and Delete What you Don’t Need

If any other processes are already open on the canvas of the Director user interface, close em to avoid possible confusion.

In the Project Browser, on the left-side of the Director user interface, double

2.Publish Alerts to Case Management process to open it on the canvas

, delete all of the processors except for the Reader and Advanced Match. Delete the line connecting the Reader to the Advanced Match processor (but do not delete the processors themselves).

click the word Reader and rename the processor Read in Data k the words Advanced Match and rename the processor

Publish to Case Management (Advanced Match).

to save the process.

u Won’t Need from the ‘Publish’

You have now created the groundwork that you need to build a process that will deal with

will not work

2.Publish Alerts to Case Management

of the Director user interface, close side of the Director user interface, double-click the

canvas.

r and Advanced Match. Delete the line connecting the Reader to the Advanced Match processor (but do not delete

Read in Data

(2)

Case Management: Dealing With Remediation at Source

Lab 6: Read in and Prepare the List of Old Errors

In this lab you will read in the list of old

lab, and then prepare the old errors to be used in the remainder of your publish process. The preparation will take the form of two steps:

1. Filter out the cases.

The cases table consists of both alerts (which are known as issues)

ultimate objective is to feed data into a workflow that will change the state of alerts when they have been remediated. In

remediated. So your process should filter out all rows relating to

to assess the value in the caseType cases.

2. Extract the UNIQUEID and Error Message into separate attributes

The cases table includes both the UNIQUEID (the primary key of the data records) and the Error Message. But unfortunately both are stored in the same attribute

(which is effectively alerts’ p

UNIQUEID and Error Message to be in separate attributes, so

You will do the extraction by using a Parse processor. Parsing is a sophisticated process, and since this course does not focus on parsing, you will import a pre

parse processor to save time

about parsing, you are encouraged to complete the Introduction to Parsing self

course, or to attend Oracle University’s Oracle Enterprise Data Quality: Match and Parse course.

Read in the List of Old Errors

1. In the Tool Palette, on the right family of processors, and then drag the reader that is already there 2. Double-click the new Reader

3. Leave the Type set to Staged data 4. In the Source dropdown, select

all of its attributes as inputs for the process.

Case Management: Dealing With Remediation at Source, Release 12.2.1

Page

Read in and Prepare the List of Old Errors

old errors from the cases table that you staged in a previous to be used in the remainder of your publish process. The preparation will take the form of two steps:

The cases table consists of both alerts (which are known as issues) and cases.

ultimate objective is to feed data into a workflow that will change the state of alerts when they have been remediated. In your architecture, cases themselves will not

your process should only be interested in the alerts. You will therefore filter out all rows relating to cases. You can do this by configuring a Value Check processor

caseType field, which will be either issue for alerts or QUEID and Error Message into separate attributes

both the UNIQUEID (the primary key of the data records) and the Error Message. But unfortunately both are stored in the same attribute: the

primary key). Later steps in your process will require the UNIQUEID and Error Message to be in separate attributes, so you will extract them now.

will do the extraction by using a Parse processor. Parsing is a sophisticated process, urse does not focus on parsing, you will import a pre-configured published to save time. Please note, however, that if you would like to find out more about parsing, you are encouraged to complete the Introduction to Parsing self

rse, or to attend Oracle University’s Oracle Enterprise Data Quality: Match and Parse

Read in the List of Old Errors

In the Tool Palette, on the right-side of the screen, click to select the Read and Write

family of processors, and then drag a Reader onto the Canvas, dropping it directly below the reader that is already there.

Reader. The Reader Configuration window will open. Staged data.

dropdown, select Case Management Tables.cases and click all of its attributes as inputs for the process.

Release 12.2.1

Page 32 of 96

Read in and Prepare the List of Old Errors

you staged in a previous to be used in the remainder of your publish process. The

and cases. Your ultimate objective is to feed data into a workflow that will change the state of alerts when

will not directly be will therefore a Value Check processor

for alerts or case for

QUEID and Error Message into separate attributes.

both the UNIQUEID (the primary key of the data records) and the : the keyLabel our process will require the

will extract them now. will do the extraction by using a Parse processor. Parsing is a sophisticated process,

configured published . Please note, however, that if you would like to find out more about parsing, you are encouraged to complete the Introduction to Parsing self-paced

rse, or to attend Oracle University’s Oracle Enterprise Data Quality: Match and Parse

Read and Write , dropping it directly below . The Reader Configuration window will open.

(3)

5. Click OK to close the Reader Configuration window. 6. On the canvas, double-click the word

Errors from Case Management Tables

Filter Cases Out From the List of Old Errors

1. In the Tool Palette, on the right processors, and then drag a 2. Wire up the output port from the

Case Management Tables

window will open.

to close the Reader Configuration window.

click the word Reader and rename the processor Read in Old

Errors from Case Management Tables.

es Out From the List of Old Errors

In the Tool Palette, on the right-side of the screen, click to select the Audit family of

processors, and then drag a Value Check processor onto the Canvas.

port from the new reader that you renamed Read in Old Errors from

Case Management Tables to the Value Check processor’s input port.

Read in Old

to select the Audit family of

Read in Old Errors from

(4)

3. In the Value Check window, select

4. Navigate to the Options tab, and enter a

5. Click OK to close the Value Check window. 6. On the canvas, double-click the words

process alerts; filter out cases (Value Check)

Page

In the Value Check window, select caseType as the Field for validation

Navigate to the Options tab, and enter a Value to compare records against

to close the Value Check window.

click the words Value Check and rename the processor

process alerts; filter out cases (Value Check).

Release 12.2.1

Page 34 of 96

Field for validation.

compare records against of issue.

(5)

7. Click to run your process.

8. Once your process has finished running, single

Management Tables processor on the

On the right-side of the Results Browser, you should see that 240 records were read into the process.

9. Single-click the Only process alerts; fi canvas.

to run your process.

has finished running, single-click the Read in Old Errors from Case processor on the canvas.

side of the Results Browser, you should see that 240 records were read into the process.

Only process alerts; filter out cases (Value Check) processor on the Read in Old Errors from Case

(6)

On the left-side of the Results Browser, you should see that 122 records passed the comparison. This means that 122 of the 240 records that were read into the process were alerts (this was denoted b

caseType field). The remainder of the records discard from the process.

Import a Published Parse Processor

1. Right-click at the bottom of the Project Browser and select alternatively follow the menu path

2. Navigate to the file ParseKeyLabel.dxi

~edq_training_assets_12.2.1

click Open. A folder named Project Browser.

3. Expand the ParseKeyLabel.dxi node, and then expand the processor called Parse Out

4. Drag the Parse Out UNIQUEID and Error Message from keyLabel processor from beneath the

Page side of the Results Browser, you should see that 122 records passed the comparison. This means that 122 of the 240 records that were read into the process were alerts (this was denoted by the word issue in the

field). The remainder of the records are cases, which we will discard from the process.

Import a Published Parse Processor

click at the bottom of the Project Browser and select Open Package File… alternatively follow the menu path File >> Open Package File…

ParseKeyLabel.dxi which you will find in

12.2.1\Data Files\Case Management. Select the file and

. A folder named ParseKeyLabel.dxi should appear at the bottom of the

ParseKeyLabel.dxi folder, and then, within that folder, expand the

node, and then expand the Published Processors node. You should see a published

Parse Out UNIQUEID and Error Message from keyLabel Parse Out UNIQUEID and Error Message from keyLabel published

from beneath the ParseKeyLabel.dxi folder and drop it on top of the

Release 12.2.1

Page 36 of 96 in the

Open Package File… or

. Select the file and d appear at the bottom of the , and then, within that folder, expand the Projects

node. You should see a published

UNIQUEID and Error Message from keyLabel.

published and drop it on top of the

(7)

Published Processors node

Extract the UNIQUEID and Error Message and Put Them in Separate

Attributes

1. In the Tool Palette, on the right

Processors family of processors, and then drag the

Message from keyLabel

node within your Case Management Training pr

Extract the UNIQUEID and Error Message and Put Them in Separate

In the Tool Palette, on the right-side of the screen, click to select the Published

Processors family of processors, and then drag the Parse out UNIQUEID and Error processor onto the canvas.

Case Management Training project.

Extract the UNIQUEID and Error Message and Put Them in Separate

to select the Published

(8)

2. Wire up the Pass port from the

alerts; filter out cases (Value Check) Message from keyLabel

Message from keyLabel

3. In the list of Available Attributes select Selected Attributes.

4. Click OK to close the window.

5. Double-click the Map sub 6. In the Inputs dropdown select

need do nothing).

Page

port from the Value Check processor that you renamed Only process

alerts; filter out cases (Value Check) to the Parse out UNIQUEID and Error processor’s input port. The Parse out UNIQUEID and Error [Parse] window will open.

In the list of Available Attributes select keyLabel and click to add it to the list of

to close the window.

sub-processor to open the Map window.

dropdown select keyLabel (it may already be selected, in which case you

Release 12.2.1

Page 38 of 96

Only process Parse out UNIQUEID and Error

Parse out UNIQUEID and Error

to add it to the list of

(9)

7. Click OK to close the window. 8. On the canvas, navigate to the

9. Click to run your process.

10. Once your process has finished running, single

Error Message from keyLabel

to close the window.

avigate to the Process tab.

to run your process.

Once your process has finished running, single-click the Parse out UNIQUEID and

Error Message from keyLabel processor on the canvas.

(10)

11. In the Results Browser, navigate to the

12. Drill-down on the 122 Unknown records.

13. Note that the UNIQUEID and Error Message have been extracted from the keyLabel and put into separate attributes. These attributes are called

ErrorMessage.Parse respectively.

Page

In the Results Browser, navigate to the Results tab.

Unknown records.

e that the UNIQUEID and Error Message have been extracted from the keyLabel and put into separate attributes. These attributes are called UINIQUEID.Parse

respectively.

Release 12.2.1

Page 40 of 96

e that the UNIQUEID and Error Message have been extracted from the keyLabel and