On this page, we will provide a description of the approval process for break clearing. This can start as soon as another user has started submitting proposed resolutions, after analysing identified breaks in a market data data cleansing (or exception management) workflow (MD XM).
On this page, we will provide:
- an overview of the approval process for market data break clearing
- a description of the approval actions and corresponding permissible values, which apply to all break resolutions
Once breaks are resolved and approved, you can view and export the results of the data cleansing process, including raw, preliminary cleansed and overlay cleansed data (as described below), with the triggered breaks and corresponding resolution applied where applicable.
Overview
Once proposed resolutions have started being submitted in respect of identified market data breaks, you will need to:
- check out the relevant approval task
- at the task level, apply a (collective) approval action on selected MDKs with a break (as described below)
In case of rejection, the resolution process will need to be repeated. Given the nature of the two-stage MD XM workflow, you will not be able to approve your own proposed resolutions.
At the task level, the approval process will be as follows (similar to the resolution process):
- for each MDK with breaks, you can
Apply your validation or rejection of the proposed resolution either collectively (on all or on a sub-selection of filtered or explicitly selected items) or individually.(1) - applied approval actions for selected items can be undone by clicking on
Reset - you can submit applied approval actions “as-you-go” by clicking on
Submit or CTRL+ENTER / CMD+ENTER on your keyboard (2) - an approval task can be cancelled as a whole at any point by clicking on
Cancel (3)
Approval Task for Market Data Breaks
In this section, we will illustrate with a worked example how to approve market data preliminary break resolutions. The same process will apply to overlay break resolutions.
In our example, we had a preliminary market data break (Quantum test) that was resolved with the individual ‘Manual’ override action.
Under
Once proposed proposed resolutions have been submitted for approval, a different user to the resolver can check out a task by double-clicking on the line item or selecting a series of tasks and clicking on
The status of the selected clearing task(s) will go from ‘PENDING_APPROVAL’ to ‘IN_APPROVAL’ until completed, when it (they) will disappear from the live task list.
In addition to setting your preferred display configuration, you can:
- view all or only MDKs with breaks (by clicking on either ‘All’ or ‘Breaks Only’ in the data table)
- filter and sort by Data Provider, Asset Class, Instrument Type, etc.
Supporting evidence can be uploaded prior to submission by clicking on
A description of the approval scope and status and corresponding permissible values are set out in the table below.
| Field Name | Description | Permissible Values |
|---|---|---|
| Approval Scope | The scope of the approval | OVERALL | INDIVIDUAL |
| Approval Status | The approval status to be applied to the filtered/selected items | VERIFIED | REJECTED |
| Comment | Rational for approval | Free text |
After applying and submitting ‘VERIFIED’ as your approval action, the MD XM workflow should look like this:
If a resolution is rejected however, the task(s) will go back to (or be re-created with) the status of ‘NOT_STARTED’ in the resolver’s live task list panel.
