Planning an update of Next-Best-Action Designer
When preparing for an update, take into account the environments that you have in your pipeline. To avoid interrupting normal business operations with downtime for the update, the following update path is recommended:
- Run the pre-update check and resolve all of the identified errors.
- Update Next-Best-Action Designer in the Staging Clone environment.
- After the update is successful and tested, push the changes to the live Production system.
- Push the changes from Staging Clone to downstream instances such as BOE, Staging, Dev
or QA environments after Production is updated.
Note: Make sure to sync all Next-Best-Action Designer dependent Artifacts before migrating the Next-Best-Action Designer upgraded Artifacts for maintaining the same configuration in all instances. Avoiding this may cause problems with migrating Artifacts from Production to downstream instances.