CDT configuration groups and driver entities

The entire set of the Sterling Order Management System Software configuration data is broken down into logical subsets called "configuration groups" and "driver entities". Configuration groups and driver entities are predefined and cannot be changed.

During the deployment process, if you need to perform more granular inserts, updates, and deletes so that your target database matches your source, you choose these configuration groups or driver entities.

Driver entities

Most of the Sterling Order Management System Software configuration data can be deployed starting with a logical entity, for example, an organization or a pipeline. These logical entities are called "driver entities". Driver entities represent the most granular level of information that can be deployed from the source to the target without loss of data integrity.

Only driver entities allow deployment at a record level. For other tables either of the following conditions apply:

The table is completely deployed if it is not dependent on any driver entity.
Only records corresponding to the driver entity are deployed.

Information about driver entities can be stored in multiple tables and when deploying an entity, data in all related tables is deployed together in one transaction boundary to preserve data consistency.

Configuration groups

Logically related tables or driver entities are also grouped together into "configuration groups" that typically represent larger, significant logical data models within Sterling Order Management System Software. Examples include the Business Process Model or the Participant Model. These groups are provided for convenience and for ease of navigation on the user interface.