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

Transcription

1 Lab 5: Delete What You Won t Need from the Publish Process You have now created the groundwork that you need to build a process that will deal with remediation at source. In 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 process. Open the Process, and Delete What you Don t Need 1. If any other processes are already open on the canvas of the Director user interface, close them to avoid possible confusion. 1. In the Project Browser, on the left-side of the Director user interface, double-click the 2.Publish Alerts to Case Management process to open it on the canvas. 2. On the canvas, delete all of the processors except for the Reader and Advanced Match. 3. Delete the line connecting the Reader to the Advanced Match processor (but do not delete the processors themselves). 4. On the canvas, double-click the word Reader and rename the processor Read in Data Records. 5. On the canvas, double-click the words Advanced Match and rename the processor Publish to Case Management (Advanced Match). 6. Click to save the process. Page 1 of 10

2 Lab 6: Read in and Prepare the List of Old Errors In this lab you will read in the list of old errors from the cases table that you staged in a previous 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) and cases. Your 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 directly be remediated. So 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 to assess the value in the casetype field, which will be either issue for alerts or case for 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: the keylabel (which is effectively alerts 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. 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-configured published parse processor 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-paced 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-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. 2. Double-click the new Reader. The Reader Configuration window will open. 3. Leave the Type set to Staged data. 4. In the Source dropdown, select Case Management Tables.cases and click to select all of its attributes as inputs for the process. Page 2 of 10

3 5. Click OK to close the Reader Configuration window. 6. On the canvas, double-click the word Reader and rename the processor Read in Old Errors from Case Management Tables. Filter Cases Out From the List of Old Errors 1. 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. 2. Wire up the output port from the new reader that you renamed Read in Old Errors from Case Management Tables to the Value Check processor s input port. The Value Check window will open. Page 3 of 10

4 3. In the Value Check window, select casetype as the Field for validation. 4. Navigate to the Options tab, and enter a Value to compare records against of issue. 5. Click OK to close the Value Check window. 6. On the canvas, double-click the words Value Check and rename the processor Only process alerts; filter out cases (Value Check). Page 4 of 10

5 7. Click to run your process. 8. Once your process has finished running, single-click the Read in Old Errors from Case Management Tables processor on the canvas. 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; filter out cases (Value Check) processor on the canvas. Page 5 of 10

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 by the word issue in the casetype field). The remainder of the records are cases, which we will discard from the process. Import a Published Parse Processor 1. Right-click at the bottom of the Project Browser and select Open Package File or alternatively follow the menu path File >> Open Package File 2. Navigate to the file ParseKeyLabel.dxi which you will find in ~edq_training_assets_12.1.3\data Files\Case Management. Select the file and click Open. A folder named ParseKeyLabel.dxi should appear at the bottom of the Project Browser. 3. Expand the ParseKeyLabel.dxi folder, and then, within that folder, expand the Projects node, and then expand the Published Processors node. You should see a published processor called Parse Out UNIQUEID and Error Message from keylabel. 4. Drag the Parse Out UNIQUEID and Error Message from keylabel published processor from beneath the ParseKeyLabel.dxi folder and drop it on top of the Page 6 of 10

7 Published Processors node within your Case Management Training project. Extract the UNIQUEID and Error Message and Put Them in Separate Attributes 1. 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 Message from keylabel processor onto the canvas. Page 7 of 10

8 2. Wire up the Pass port from the Value Check processor that you renamed Only process alerts; filter out cases (Value Check) to the Parse out UNIQUEID and Error Message from keylabel processor s input port. The Parse out UNIQUEID and Error Message from keylabel [Parse] window will open. 3. In the list of Available Attributes select keylabel and click to add it to the list of Selected Attributes. 4. Click OK to close the window. 5. Double-click the Map sub-processor to open the Map window. 6. In the Inputs dropdown select keylabel (it may already be selected, in which case you need do nothing). Page 8 of 10

9 7. Click OK to close the window. 8. On the canvas, navigate to the Process tab. 9. Click to run your process. 10. Once your process has finished running, single-click the Parse out UNIQUEID and Error Message from keylabel processor on the canvas. Page 9 of 10

10 11. In the Results Browser, navigate to the Results tab. 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 UINIQUEID.Parse and ErrorMessage.Parse respectively. Page 10 of 10