Overriding Values
Data quality isn't always perfect.
There are times - particularly when you're working with processes that involve one or more human steps - that data has bad timing or is simply incorrect due to factors you can't compensate for.
When this happens, the Capture system allows administrative users to override values in a capture.
Performing an Override
To override a value, sign into ARDI as an administrative user and open the Capture you want to change.
Press the Override button at the bottom of the page.
Choose the property you want to edit, and the new value you'd like it to have, then press the '+' button.
Once you've added all of the changes you'd like to make you'll also optionally be able to write a small explanation. This will let later users understand why your overrides were needed.
Hit Apply to record the new values.
Displaying Overridden Values
Any overridden properties are marked in red on the page and are explained in detail at the bottom of the capture page.
Deleting Overrides
When you remove an override from the list (by clicking the 'trash' icon next to it), the original value will be restored.
You will not have to remember or write down the original values in the case of mistakes.
Overrides and Regeneration
Overrides are designed to persist through updates.
For example, if the following sequence of events happens…
1) You change a value from 0 to 10 for batch 225.
2) You change your Capture logic
2) You regenerate the capture for batch 225.
Even though you've regenerated your batch data and the value has been calculated to be '0' again, it will show as 10 because the system has remembered the override.
This prevents you losing valuable manually-entered data when you need to rebuild parts of your captured information.
Complex Example
When regenerating a capture that has one or more overrides, the original value recorded by the system - the value that will be restored if you remove the override - will be updated with the results of any new Captures or back-generations you perform..
So the following sequence might happen…
Displayed Value: 0
1) You override a value from 0 to 10 for batch 225.
Displayed Value: 10, Original Value: 0
2) You change your Capture logic
3) You regenerate the capture for batch 225.
Your new logic does a better job and calculates the value to be '9.5'. But the override remains in place, so the displayed value is still 10.
Displayed Value: 10, Original Value: 9.5
4) You then remove the override.
Displayed Value: 9.5