Change Control

Team to email to move tickets: Epic Data Courier Movers – Orders/Bugsy

Allowed to move/Need CC List

Email List for move to prod: Epic Data Courier Movers – Orders/Bugsy

EAP Change Control:

  1. When creating a new EAP, modifying an existing EAP, or inactivating/soft deleting an EAP, identify the appropriate OneNote form(s) that applies to the EAP change(s) you are making
  1. a.EAP Change Control – New EAP/EDP
  2. EAP Change Control – Inactivate/Soft Delete EAP/EDP
  3. EAP Change Control – Modify Existing EAP/EDP
  4. EAP Change Control – Modify Department/Location Restrictions EAP
  5. Do not modify the OneNote directly. Click the “Email Page” button on the Ribbon to email the form to the affected applications. Populate the relevant fields with the appropriate information prior to emailing the form.
  2. Add this in the Subject line of the email: <App team> EAP Change Control – <Description of the EAP change>
  3. List of Application DLs for reference
  1. You must get approval from all affected applications via the EAP Change Control Process before migrating the changes to TST.
  2. Add the following statement in the Change Details section of your CM ticket: <Date> – Received approval via EAP Change Control process from <affected applications>.
  3. Once you have migrated the changes to TST, check the UH Allowed to Move list to see if the change needs to go to Change Control (CAB) before migration to PRD.

Archived Change Mgmt Tickets

Following up on a topic I brought up on this morning’s call. In an attempt to help improve filters and searches in Content Management I configured Data Courier settings yesterday to archive tickets that were more than 2 years old (based on migration or edited date) and data courier packages that were more than a year old. Unfortunately, as I discovered on the call, some teams are regularly searching all tickets, even back to implementation days to understand earlier decisions.  

Archived tickets and packages can still be searched; however, it’s done via Text and not Hyperspace. Seeing as many teams search those older tickets and the search in Text isn’t nearly as user friendly as it is in Hyperspace, I am following up on what options, if any, there are to get some of that information back in Hyperspace. I’ve also removed the settings to prevent further archiving until we can develop a better plan for how to improve filtering without sacrificing ease of searching old tickets. In the meantime, if you are running a search for a ticket or a package and not finding something you expect to see, it may be an older ticket or package that is now archived and you should follow the instructions in these galaxy articles. Please note the search tool looks at both archived and non-archived tickets so if you want to look through all tickets and not just recent ones, you may want to start your search in Text instead of Hyperspace.

I covered the updates during yesterday’s change control call and wanted to share with the rest of the group. First a reminder that I only archived POC and TST so you can still search all tickets in PRD hyperspace as long as they made it that far in their migration journey. If they didn’t make it to PRD then yes, you’ll need to use Text to search POC/TST for older tickets.

  • Tickets cannot be easily restored from the archive file and options for possibly bringing the information back into POC or TST are complicated and not recommended unless necessary.
  • Searching archived tickets from Hyperspace instead of Text is not on the roadmap but is an open enhancement request.
  • Exporting the report from Text is the only way to see the full text of Change Details.

Environments

To move to PLY, move TST-> MST. PLY is a copy of MST.

Change Control