Migrate to legacy change risk assessments
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- Change Management
Users can migrate legacy change risk assessments to versions compatible with the new Change Risk Assessment table schema and logic.
Before you begin
Few points to remember:
- Customers with Change Management - Risk Assessment [Legacy] (com.snc.change.risk_assessment) plugin already installed on their instances should only follow this task.
- The Change Management - Risk Assessment [Legacy] (com.snc.change.risk_assessment) plugin cannot be installed for customers who are on Kingston and later releases.
- Migration guidance and best practice suggests that the migration should be performed on a development instance and not on a production instance.
- The development instance must have the new Change Management - Risk Assessment [com.snc.change_management.risk_assessment] plugin installed.
- All migration work must be captured in an update set, moved to a test instance, and then tested before moving them to a production instance.
Role required: itil_admin
About this task
- Risk assessment definition, questions, and question choices.
- For multiple assessment conditions, the migration might result in the following one or more than one risk assessment records:
- If all the multiple assessment conditions are on the same table, then the migration results in only one risk assessment.
- If the multiple assessment conditions are on different tables, then the migration creates as many risk assessments as they pertain to different tables.
Procedure
What to do next
disable_legacy_change_risk_assessment.js Capture
the results in the update set created and later mark the update set as closed complete. For more information, see Mark an update set complete.Note: The given procedure is a suggested practice. Alternatively, you can capture each migrated Change Risk Assessment in their own update set. You
can also capture the results of disabling of the Change Management - Risk Assessment [Legacy] using
disable_legacy_change_risk_assessment.js in a separate update set.