Using Setup Data Manager

Use Setup Data Manager to save the time of manually re-entering setup data in multiple environments, eliminate the potential for a user to make a mistake when re-entering setup data, and allow you to update a number of setup data policies all at once.

Setup Data Manager (SDM) lets you publish configuration (setup) data from one tenant to another tenant. Setup data is data that you enter as part of the configuration of the suite. For example, setup data includes pay rules, labor levels, and manager summaries. You can copy all setup data or select specific setup data.

SDM adds or updates setup data items based on the name of the item:

• If the item name already exists on the target database, then the item is updated.
• If the item name does not exist on the target database, then the item is added.
• An item is never deleted from the target database, regardless of whether it exists or has been deleted from the source database.

The only exceptions to the items above are for Business Structure elements, Business Processes, Process Models, Attestation Workflows, and Attestation Models, which are added or updated based on an internal ID. This allows you to change the name of an item but keep its place in the business structure. This means that a business structure node that was created on one tenant, always has a different ID than any node on another tenant, and is considered a unique setup item. For nodes on different tenants to be considered the same they must have originated on the same tenant.

The changes made to setup data on the target server during the data transfer are written to the server’s audit trail, just as if they were entered manually on the target system. This means that a business structure node that was created on one tenant, always has a different ID than any node on another tenant, and is considered a unique setup item. For nodes on different tenants to be considered the same they must have originated on the same tenant.