Database Purging or Cleanup Guidelines

Order Management System

Order Management System is provided with a purge script that can be used to clean up data about orders that are in a certain state, in a given date range. This can be used to purge order data at regular intervals and can also be run while the system is processing new orders, thus avoiding the need for an outage.

However, purging completely deletes the data about orders and associated objects such as plans, plan items and User Defined Fields. If any of this information needs to be kept, then consider implementing an archiving strategy, where data is not purged, but copied to an archive. This requires some custom development.

Ensure that the business requirements around logging and archiving are properly captured and analyzed.

Transient Data Store and Orchestrator

Both these components can be configured to self-clean when an order reaches an end-state. Use these features to avoid having to clean up the Transient Data Store and Orchestrator. Order Management System might be seen as the database of record for orders and plans, and the backing stores for Orchestrator and Transient Data Store might just be for dealing with data about orders that are in-flight.