Full History for Publishes and CSV Merge
The document history tracks changes that are made in the Axcelerate 5 front end. It does not track values that come in with a publish. Also, it does only track very generic information on fields that are changed using CSV Merge.
You can configure the system to show the full history for specific fields, that is, the exact values inserted by a publish or CSV Merge, and, of course any other changes in the Axcelerate 5 front end.
Full history is useful
- for metadata fields that are filled during data load and that will possibly be modified through tagging in the Axcelerate 5 front end.
- for field values that will be modified using CSV merge.
Example: Custodian field
A use case for this may be the Custodian field. It may happen that this field is wrongly filled during data load.
If documents have not been published yet, you can configure the Custodian field to be tracked for Document History. After the publish, the Custodian field values are then shown in the Document History.
If you then correct the custodian, using CSV Merge, the Document History will display this correction with the changed value too. Case Managers will be able to check the values in the user interface.
Document History for CSV merge and publish
