Data Clean-Up
OMD tasks are usually uploaded by an external system. For example, production data may be received from an ERP such as SAP, Oracle or MS Dynamics. Relevant data produced during the planning and optimization process or during Field Service is usually propagated back into the ERP system.
To avoid historical data to be stored eternally in OMD, the following preferences can be used to determine the time frame during which production data remains available in OMD. During implementation, these preferences must be set according to the contract requirements.
Historical GPS data can be purged after a certain period of time. By default, tracking data is deleted after 10 days. If set to 0, track information is never purged.
| purgeTracks | ||
|---|---|---|
| Type | Default Value | Example |
| Days | 10 | 3 |
Most data on OMD is related to tasks. The amount of task data can increase significantly over time, depending on the amount of resources and their average amount of tasks.
Once a task is planned, it will be purged after purgeTasks days when having been closed or cancelled in the meantime or after having been planned purgeTasks days ago without having been closed, cancelled or moved.
Unplanned tasks are never purged, unless the task hasn't been touched since purgeTasks days and the status is a remove status or the latest attribute has passed purgeTasks days. If purgeTasks is set to 0, task information is never purged.
| purgeTasks | ||
|---|---|---|
| Type | Default Value | Example |
| Days | 0 | 10 |
Since tasks usually have attachments, these entries should also be deleted after a certain amount of days. Note that the purgeAttachments preference should always be smaller or equal to the purgeTasks preference.
| purgeAttachments | ||
|---|---|---|
| Type | Default Value | Example |
| Days | 0 | 10 |
To clean up stored posted documents, use the preference purgePostedDocuments preference.
| purgePostedDocuments | ||
|---|---|---|
| Type | Default Value | Example |
| Days | 2 | 1 |