Configuration Item tab in Digital Product Release
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
What should we look for in the Configuration Items tab of a Release in Digital Product Release, so as not to assume its functionality? We
just updated to 2.4.1 and we don't know what to expect from that tab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hi @joseaarias
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hi @joseaarias
1) "Select the Configuration items section to review and manage the configuration items in the release.
- You can add more configuration items or remove the existing ones as needed. "
Refer: Servicenow Documentation - Work on a timeline-oriented release for a single product or service
2)Also As per the community post :How to Configuration DPR (digital product release)
"Please refer to the Adoption Playbook for a quick start and to review the prerequisites before setting up the DPR. The following post includes an attached PDF—go through it for detailed guidance and official resources:
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
You can associate any Configuration Item from the CMDB to each phase of a release. When a change is raised and related to the same phase, we include an action to associate the CIs from the release phase into the Affected CIs tab of the Change to help streamline the process of having CIs connected to Change Requests. We have future plans to make it easier to select which CIs can be associated to the Release.
One of the reasons for this feature was for customers that want to create Policies that check for successful Change Requests for CIs in the QE/UAT environments before allowing deployment to Production environments.
Thanks,
Colin