- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2023 07:13 AM
Your preference would be a default custom on-call schedule. We haven't found a way of doing this so need to setup each schedule individually. Once it's setup and working in Dev how do we move it to Test and then to Prod. I can't find the table where this is stored. Any recommendations?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 11:22 AM
I believe it's cmn_rota_escalation_set.list
I'm not positive because we are not using the escalations in the shifts/schedules; we are using SLAs to notify Team Leads/Managers if an alert isn't acknowledged. So - we haven't had to promote those to our test instance. I'll be interested to know if that does work for you because it's possible that we will move that direction or use the escalation in some form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2023 01:40 PM
Are you using a local update set to promote your build from dev to test to prod? If so - the only on-call piece that is automatically added to the current update set is the Trigger Rule. All the other pieces have to be added to the update set separately. You will need to go to the following application and 3 tables and add your build to your on-call update set:
1. All > System Scheduler > Schedules > Schedules: search for the group/schedule you just created and add all to the update set.
2. Type cmn_rota_member.list in the Filter Navigator and hit Enter to open the On-Call Member table - search for the rotation schedule you created and add all to the update set
3. Type cmn_rota_roster.list in the Filter Navigator and hit Enter to open the Roster table - search for the shift name you created and add all to the update set
4. Type cmn_rota.list in the Filter Navigator and hit Enter to open the Shift table - search for the group you created and add all to the update set.
Then complete your update set and pull from dev to test.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 11:01 AM
Hi Beth,
Thanks for the reply. Yes, we are using a local update set. We also export to XML. I'm looking for the table that contains the escalations so I export it. I'm fine with exporting the XML but haven't found the table(s) where it is stored.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 11:22 AM
I believe it's cmn_rota_escalation_set.list
I'm not positive because we are not using the escalations in the shifts/schedules; we are using SLAs to notify Team Leads/Managers if an alert isn't acknowledged. So - we haven't had to promote those to our test instance. I'll be interested to know if that does work for you because it's possible that we will move that direction or use the escalation in some form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2023 08:51 AM
Hi Beth,
I've been out of the office. I'm going to accept your solution, since it has been helpful. We haven't gotten granular enough yet to be 100%.