To manage a migrated request for change (RFC), search for the RFC by change ID by opening the RFC form and typing the full 15-character change ID. This will return any migrated tickets categorized as ZZ-Other. Update the RFC with the correct operational categorization and risk level by clicking the risk questionnaire button to avoid being marked as high risk. Click save to complete the changes to the migrated RFC.
To manage a migrated request for change (RFC), search for the RFC by change ID by opening the RFC form and typing the full 15-character change ID. This will return any migrated tickets categorized as ZZ-Other. Update the RFC with the correct operational categorization and risk level by clicking the risk questionnaire button to avoid being marked as high risk. Click save to complete the changes to the migrated RFC.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
To manage a migrated request for change (RFC), search for the RFC by change ID by opening the RFC form and typing the full 15-character change ID. This will return any migrated tickets categorized as ZZ-Other. Update the RFC with the correct operational categorization and risk level by clicking the risk questionnaire button to avoid being marked as high risk. Click save to complete the changes to the migrated RFC.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
1. Open the Request for Change form in search mode
by clicking on the Search Change option from the 4. All migrated tickets will be categorized as ZZ-Other, quick links on the left side of the Change Management Console ZZ-Other, ZZ-Other
2. Once the Change form opens, type the ENTIRE 15
characters of the CHG ticket number in the Change ID*+ field 5. Update the RFC with the correct Operational Categorization
3. Click Search at the bottom of the form
Required Step for all RFC’s that are in Draft, Planning
or Pending Approval Status
6. Click on the Risk questionnaire button to enter the
risk level of the change
Note: Failure to complete this step results in the RFC
to be marked as High Risk and will be included in the ECCB change review process (30-day lead time and review by Technology Leads).
7. Click Save to save this data change and continue
with the request
NOTE: You must choose “Search” in order to pull up a
migrated request. Clicking “Enter” on your keyboard will result in an error. 47565256.docx Page 1