Configuration Management - managing test and production data

During an implementation project, keeping environments synchronized is a consistent challenge. A configuration change tested and approved in the test environment must move to production cleanly and completely. The move must also not overwrite data that should not change.

When a bug occurs in production that you cannot reproduce in the testing environment, the fastest fix is to refresh the test environment with a copy of live data. Without tools to support these tasks, teams perform both tasks manually, and the process is inconsistent.

After the implementation is live, the same challenge continues. Each new season requires new configuration. This configuration can include updated business rules, new views, and revised lookup tables. This configuration must also move from the test to the production environment in a controlled way. Additionally, this process must not depend on manual steps that a person must remember and document.

In Infor PLM for Fashion, Infor configuration management supports this process. You can package, tag, and transfer configurations between environments in a structured way. This process gives your team a repeatable, auditable method and reduces dependence on individuals.

The result is lower risk when you move changes to production. The process also reduces the time to refresh a test environment and simplifies the transition when the implementation team transfers responsibility to the business.

In Self Service Portal, you can transfer PLM for Fashion configurations between tenants in a controlled manner. You can use features or tagging in PLM for Fashion.

Currently, these features are supported for Local Packages:

• Business rules
• Generic look up for items that are part of the business rules
• Admin > views for views that are unique to the customer
• Roles - Permissions
• FQV queries
• Item types
• Exchange rates