The Process Overview screen shows information about a specific process and its runs.
Run result summary
For each run of a process, the screen shows a colour-coded results bar that gives a quick summary of the match results.
If you hold your mouse pointer over a results bar, a results summary for that particular run will pop up.
The pop up shows the number of items that are...
- Partially matched
- Excluded: Items that have been excluded from the process through filtering rules. (The page Filter rules provides more information about filter rules)
The match evolution box shows a graph of how the percentages of matches, partial matches, etc. change between runs. When a process is being set up, this box typically shows that the number of partial matches rapidly reduces run after run as the process is configured, rules added, etc. Once a process is set up and runs at regular interval, the percentages should stay fairly steady. A big sudden change in the number of partial matches might indicate the that something has happened and requires further investigation. A sudden change in the match evolution graph happens for various reasons, for example:
- The data has changed. This can be normal or it might mean that the new data sets contain new types of items. You might need to revise the filtering rules or the matching rules.
- The process settings have changed. Another user with sufficient permissions may have changed the process settings.
To access the match evolution box, select the History menu and then choose All runs from the drop-down.
The Run times box indicates the run times for each run of the process.
If tracking is enabled, the Process overview screen will show also an Ageing box, which the page Record tracking and ageing describes in detail.
Mark a run as failed
A file with bad data may be submitted by mistake or unintentionally (e.g. through automatic submission) and still trigger a run in Duco. This could result in many incorrect matches and/or new unwanted exceptions that may be mixed up with legitimate exceptions carried-over from previous run.
In such scenarios it is possible to mark a run as failed. Duco will then close all the new exceptions created, re-open exceptions from previous successful run, and restore their workflow statuses.
To mark a run as failed simply select the Mark as failed button next to the applicable run. Note that this will only be selectable for the most recent valid run.
The Breaking fields box shows how many results items break for each field.
In the example above 7 results items have a break on the Trade Date field, 2 on the Price field, 2 on the Symbol field, and 1 on the Company field.
After clicking on "7 breaks", Duco shows the six results that contain a break on the field "Trade Date".
You can get to the same results also using filters. As the following image shows.
The Data submission information box shows the exact count of records submitted.
Inspecting match results
To view the match results in more detail, click on one of the items in the navigation bar on the left of the screen.
For example, the partial matches might look as follows:
To view a particular match result, click on the match result ID.
This screen shows all the field values for a match result. If there are any breaks, these are highlighted in red. From this screen you can also write a comment or create a case relating to this match result.
In this particular example, we can see that this is a partial match because the "Company" field contains the value "Biomet," (notice the comma) in one data set, and "Biomet" in the other data set. You can introduce a "strip character" rule to solve this problem. The pages A quick start guide to Duco and Rules & Rule sets describe how to do this.
If you click on Filtered, Duplicates, and Errors from the navigation bar then you'll see a screen like the following.
And if you click on a result ID, you'll see something like the following.
In this case, Duco cannot match items from the two data sets. The result items for each data set are therefore listed separately and clicking on a result item ID shows only the details for one data set.
If record tracking is enabled, a match result page will contain also a History box. The page Record tracking and ageing describes this in detail.