Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
After adding a new environment to the migration path and clicked on the 'Add new env. to CSR' button as documented in the manual, nothing happens. According to the instructions, this should open a list of CSRs that the user wants to add the new instances to.
원인
Misinterpretation of the documentation.
해결 방안
You can add environments to existing migration paths that are already associated with CSRs. You then have the option of updating the migration path on selected CSRs to include the new environments.
NOTE: Environments can be removed from the migration path maintenance table. However, removing an environment from a migration path will only be reflected on newly created CSRs. The environment will not be removed from existing or closed CSRs.
Below are examples of when user would have the ability to add env to CSR. Current migration path: PROD – DEV - TEST
Now TEST is removed and added SYSTEM TEST and the migration path now look like this: PROD - DEV - SYSTEM TEST
Stat will not list the CSR to be added to the migration path. The only way user will see the pop-up is if the migration path looks like this: PROD - DEV - TEST - SYSTEM TEST
In other word, the add env to CSR would only be available if the user added additional DB, but not if DB gets removed or changes the order of the DBs around.
