When you need to change configuration files, you need to make the changes on the Test
environment, validate the changes, and then copy the changes to the Production environment.
CAUTION: Making untested changes directly in the Production environment
is not recommended since it may cause serious unwanted effects or render the
environment unusable.
-
If the change you are making is a workflow state change, move
all objects out of the status.
-
Make the change in the Test environment.
For example, change a topic template in the Test environment.
-
Verify the change in the Test environment as follows:
-
Connect to the Test environment.
-
Verify that the change works as expected and that no
regressions have occurred.
-
If any issues exist, iterate on the change.
Example tests include creating a new topic to test template changes,
moving objects between states to test workflow changes, or locking and releasing
objects to test DTD changes.
-
Duplicate the changes in the Production environment.
-
Test the change on Production environment in the same manner
that you did on the Test environment.