Info: This feature requires Assets Server 6.112 or higher.
When users work on assets, a history of specific actions is kept so that it can be determined which changes were made, when these were made, and who made them. These changes can be viewed in the History panel in Assets.
Over time, this can result in thousand of records for each file. This can negatively affect the loading time of the data in the History panel.
Another factor that could negatively affect the performance of the History panel is the amount of data that is stored in the changedMetadata field.
In addition, when an API call is made to retrieve the history data, it may not make sense to retrieve all records when many records exist.
The following options can therefore be configured in the cluster-config.properties.txt file to improve these scenarios:
| Option | Function |
|---|---|
| assetHistoryMaxRecordsClient |
For limiting the maximum number of records displayed in the History panel. Default value: 1000. |
| assetHistoryMaxRecordsAPI |
For limiting the maximum number of records returned by the Versioning and history REST API. Default value: unlimited. |
| metadataChangeHistoryFieldLength |
For reducing the amount of data stored in the changedMetadata field. Default value: unlimited. |
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.