good morning good afternoon good evening everybody wherever you are thanks for joining uh this webinar on digital product release um we're specifically targeting some of our customers who use release management V2 just to share more about our new release management product which is digal product released uh and we're going to talk about some of the uh tools we have to help you migrate from release management B2 to DPR uh but also give you an overview of what DPR is uh what it can do and give you a pretty uh handy demo to to watch before we jump into the agenda uh always need to start with this Safe Harbor notice this presentation might have some forward looking statements um that's based on what we currently believe with the information we have available but please don't take anything we say is set in stone uh things that are forward looking could change uh and may for today's agenda I'm going to start with brief introductions uh of your speakers uh then we're going to jump into some overview about the evolution of release governance uh in the Enterprise then look at DPR specifically and give you an overview of what DPR is how it works and then from there jump into a demo uh we have time for Q&A at the very end but please don't hesitate to ask questions throughout you can either raise your hand or use the Q&A uh in the zoom chat uh we we have a few folks on the call who can help answer those Q&A questions and we'll also flag some to to answer live if we think it's broadly applicable all right so let's start with intros uh my name is my name is kayin Casto I am an outbound product manager uh focusing specifically on our modern governance products within icsm of which digital product release is one I've been with service now for about two years now um yeah and Colin over to you yeah certainly so hello everybody uh and for whatever reason Zoom has decided I cannot turn my uh camera on so you'll have that that nice picture of me and the introductions uh but my name is Colin O'Brien I am a part of the inbound product management team service now going on 10 years um and focused currently on our digital product release um application uh and then also uh although not on the slide you may either see question responses from uh Joe or bology they're both also part of our product management team uh and we be helping out in the the Q&A in the chat Perfect all right while we I pull up this poll I see Sam already has a question so Sam way to let you off mute Sam go ahead and ask your question uh yeah just uh we've got a user that's unable to get in uh says their registration is pending approval okay I will look into that thank you Joo okay all right uh while I look into that I'm going to launch this poll question all right so uh for those on the call just wanted to gauge your familiarity with DPR ahead of this session um maybe it's your first time hearing about it maybe you've heard about it in previous webinars maybe you've already installed it and started playing around with it maybe you're planning to install it uh or implement it rather would love to to learn more this up this about five more seconds okay I disapproved jao so hopefully he'll be able to join now all right uh looks like the vast majority of folks on the call are unfamiliar with DPR so that's great to hear hopefully you get a lot of value out of this session learning more about what it is how it works and and how it can help you and few others who have some familiarity with it so hopefully this is still helpful for you am I still unmuted uh you are okay so just as a point of reference to you um this came off of we have some heavy users in release management and got the email that release management wasn't going to be supported anymore so a lot of people are just kind of seeing okay what's this about what is it and you know we're not looking to move anytime soon but it's kind of a FYI to to the Future yeah yeah totally fair yeah and so uh as I I'm going to take over uh sharing so let me um for those that are are learning about the uh shift to the new product from release management V2 uh keep in mind that through your your current contract uh release management V2 will be supported and even after that um that period is ended we actually get very few support cases for release management V2 primarily because you know out of the box it's mostly a collection of tables uh so for those and this is going to be one of the poll questions because I am interested in how much customization you all have done to release me to um by and large most customers have uh have you know enhanced it to the point where it's like your own product so I think over the past year we've gotten a total of six cases uh and so even once your support contract is over we're not uninstalling release V2 but going forward uh and I mean there haven't been any updates to release V2 I think since either New York uh so several years ago um it will continue to be in your instance so the move to uh digital product release which is the next evolution in our support for release management um it can be made Side by by side uh it does not have to be made immediately and we are working on we actually have some utilities to help with the migration and a part of one of the last poll questions is to get feedback on are there other areas that we could help through that transition um so it's just for everyone to to to keep in mind it's not going to be uninstalled and there's a good chance that you haven't even open a support case in years uh for for release V2 so you'd be able to continue to use it uh as you're doing today although you know as as uh I I hope that many of you on the call will do is uh is start the transition uh because I have been a part of like my name has been attached to release management V2 uh as the owner of it for some time uh I want to say six or seven years but that St been my primary product uh somebody needed to be able to talk to customers or triage in that were coming in that we might need to make updates to but during that time as I've talked with customers we have seen a shift the reason why release V2 was um was really positioned more as a framework was because there wasn't a lot of consensus as to what release management should be back when it came out which predates me so again I've been at service now for about 10 years um it the the previous owner for it who's also still with service now um she and I talk pretty regularly uh she had it before then and it predates her and she's been here 12 years so back going you know 10 15 years ago the release space was not well defined fast forward to today and we've seen a shift in the market uh especially on release being about how we deliver products uh applications software um you the the term there's lots for them but we've seen a shift to where teams are more involved in their release process they're trying to release applications um they're trying to release uh I use the term products um and so we're helping with this transition uh where I have several customers that are using DPR today that are more project oriented but even those projects are enhancing products which is what actually gets released and once we get into the seem Tob side you know application services are what are being updated and so DPR has taken an approach where we're helping customers manage the release process for software-based uh uh applications at least for now we have road map items for more types of releases but that's where we started because I think greater than 90% of our customers were really using it for software oriented um releases but we can help through that transition because one other thing that um that we saw a lot of the challenges again I've been talking with customers about this for quite some time is you know as products are getting more complex as the release process is getting more complex it's taking a lot of time to validate things um as teams are becoming more uh involved they don't necessarily know what the criteria is from an organization's perspective on releasing they just you know their code compiles it it you know deploys with their pipelines um and there may be other governance requirements that are necessary uh but also as we decentralize into teams there's less visibility by the central governance Side by Central um change teams uh Central governance teams to know what's going on and also we I've been hearing that we've overloaded the change management process with release Concepts so it's made change a much bigger process than it needs to it makes it more cumbersome changes also when you're trying to do a one siiz fits-all for all of your release process and your change process it can become difficult to maintain over time so we are working to help by bringing in automation uh as kind of a native concept within DPR we are trying to make it so teams are aware of how we know that we're done while not losing visibility for the central teams to understand what's coming down the pipe and being able to validate that the teams have completed everything uh as well as a more explicit interaction between change and release uh so instead of changes being Loosely coupled with release the way it is in release V2 uh by default we have a a stronger more dedicated connection between um change and release for uh for DPR so these are just some of the challenges that we've been hearing and why we decided to go back and build DPR digital product release uh from the ground up based on the feedback and best practices that we've been hearing from customers over the past uh several years so uh we've got a second poll question uh to learn some feedback um because we would like to understand how you're using release management today uh whether it's validating that something is ready for deployment or if it's for managing maybe complex uh deployments like multiple change requests uh we'd also like to understand um the uh the different things that you uh use for release or what things you plan to use for uh DPR so whether it's managing the entire life cycle um if are you using it for Hardware or software or patches how are you using it is it just software or is it other things that you are managing so we'll give about 60 seconds for this poll and then oh uh there's actually a scroll keep in mind um so if you did select other we'd like to hear more and then the last question is how much have you customize release management V2 um just to what extent because I've seen lots of customizations I've seen customers try and use it straight out of box so curious uh the level of customizations across all the people on the call today so real quick uh while you're answering um I'm gonna there's one question that's com in that I'll show a little bit more later on you know collisions with change and the cmdb um right now the uh we are uh leveraging the cmdb much closer with digital product release uh but change is still used for Collision detection um so change conflicts are primary we also do have some some items because of official calendar support um but more kind of collision detection type of items are on our road map um for uh for next year so if there's more and you want to put it in in the chat for us to capture what types of kind of collision ofo voidance type scenarios you have I'd love to learn more um on that one okay um Kay do you want to end the poll yep right so good number using uh using release for both validation and deployment um so that's uh a lot of the customers when I was or talking we're on the validation side but it looks like release fe2 customers are using it for both um and then what kind uh across the board um one so um probably should have had another question just on uh on maybe percentage wise but lots of software but also some Hardware use cases as well so right now digital product release just from its name is focused more on the software side but supporting other types like hard or uh service oriented ones are one of our road map items uh for next year that we're we're planning to work on um and then for customizations um I'll be honest I'm surprised that a third of people are using it out of the box so customizations for tracking approvals that's a very common one uh same thing with Integrations um I guess uh while I've definitely talked with customers that have done a total overhaul uh no one on this call has uh done it to that level um but we're definitely going to go into what DPR now has out of box so thank you for those uh those poll uh submissions okay so what is digital product relas trying to be we're really focused on I'll call a process orchestrator there are tools in the market now that are focused on actually doing deployment so cicd tools like Jenkins uh or harness or Azure devops they have pipelines that are really geared toward deploying software um we are focused on making sure that all of the things that need to happen are done before you do that deployment so if you need to validate that stories are accepted or you need to validate the tests are completed or you need to validate through an approval that um your maybe a central governance team needs to review it or you have marketing that has to review it or legal or anything like that any requirements that we have and we need to validate how do we validate those activities have occurred that's what we are really focused on so we're not trying to replace a cicd pipeline we're not trying to replace um a code repository we are taking information from those s sources in order to help automate the process or to automate the validation of your uh release and we do this through our Integrations um could have had another uh poll question just to see if people are familiar with devops change velocity but we leverage the same Integrations that devops change came with in order to pull data in from a variety of sources or leveraging just service now's inherent ability to integrate with systems to pull in information we pull that in so that we can automate answering the questions or automating the requirements that are used as Gates throughout the process so if as a part of kind of planning and scoping your release you might have some tasks that need to occur some approvals that need to occur but if there's data that we can use we have the notion of policies that look at data Within service now to determine whether or not we are compliant or non-compliant with that um with that policy so if we need to ensure that all the stories are in a ready State we can do that or as we get into user acceptance testing if we need to validate that uh all of our unit tests are passing or all of our um functional tests are passing or that security scans have occurred we'll take in that data and validate that as well so leveraging out of box Integrations or if there are custom tools that you leverage leveraging those in order to pull information in that's how we connect uh all of this together and you'll be seeing that in the demonstration in just a uh in just a little bit now while we have support out of box for all these Concepts like connecting to cicd pipelines or connecting to planning tools or connecting to your source code repos or uh artifact repositories all those different Integrations you don't have to be doing those on day one to get started with DPR um most customers that have started have really started with we're going to get into visibility and tracking where we can Define what our process looks like it's still going to be more manual where we have people approving things um and we'll we'll just get started with it and then we start integrating with tools uh most of the time customers plan to or or are uh and integrating with planning tools first because they want to understand the scope of their release so they'll connect a planning tool later they'll start connecting their cicd Pipeline and testing tools so that we can get data from those and ultimately like our ultimate goal is by leveraging both digital product release and the abilities within devops change that we can help streamline the entire process so even the change request itself can just get created we can look at the releas lease for validation we can have change policies to authorize the change and the change is also a completely automated process to help streamline and kind of modernize um uh governance which is why we're part of the modern governance uh uh Team uh here within itsm so again you you can get started we're going to start today with more of the I'm just creating a release and I have manual things uh and then we'll talk through some of the more advanced uh options as well so for the demo um I'm going to go through some of the differences between release V2 and how we do it in DPR um because some of the concepts are pretty closely aligned others there's a bit of a difference so we'll focus on how we can Define release and track a release looking at both RMV 2 out of box um and then how that really Maps into DPR and then we'll go into some DPR specific things so how do we integrate with planning tools or other tools on the software development side um just how would I get started what does it look like to get started and then also we're going to go over a bit of migration utilities to help customers move from release V2 into DPR because again they can live side by side okay so I don't see any in the Q&A at the moment so that um that's good for me to switch over okay so I am in um one of my instances and I just have kind of a Bare Bones installation of release management V2 so not all customers were using this but Within release you could just create a release or they could be tied to products so I have a product defined here this is just like my sap uh I'm going to be doing an update to it um and so I can create you know a new release and creating a new release out of the box is just saying I want to make a new release I'll give it a name um I'm really good at naming things uh so we've got a new one and then if I want to build it out again out of the box uh I would have to go in and manually create phases so I can specify what my phases are I can create new a whole lot so I'd have maybe my planning phase and I'd give it some time which I'm GNA skip for today um if I have some tasks within it I have to drill in and do those tasks now this is an area where I have seen customers put some sort of Automation in place place where the phases and tasks get created for them because nobody wants to click the new button every single time and also make sure that everything is done properly uh I'm going to go to a a preset up um release for talking to the rest of it uh we also can connect other things to the release so if I have some epics or some stories I can connect those as well um this was I believe the last enhancement we made to release V2 where you can attach additional tasks but you have to know what you're looking for so when I click the attach button um I need to know what the Epic number is and I can then attach things that I need to validate uh or watch as a part of the um as part of the scope of this release so you know out of box that's how things work but now I'm going to switch over into digital product release and go through some of these same Concepts um but show how things are are done from dpr's perspective so first of all DPR is a dedicated experience so under workspaces you would find digital product release workspace um and I'm logged in as someone who can do pretty much everything I might change roles through the process but I'm gonna be logged in as Joe um and Joe has some active releases you can see we have a dashboard out of the box we do have a process to help you get started uh digital product release can be implemented as more of a turnkey solution so some of our customers have uh leveraged a partner to implement DPR other customers have just turned it on and followed this process and got it gotten going themselves usually the big difference between a partner involvement or doing it themselves is how much of their change process they will also be modifying in in order to account for DPR because again a lot of customers have put change related Concepts into um uh into change management so if you're going to unwind those more likely a partner is needed but to get started you do not need um you know partner implementation you also don't need a system administrator with the exception of turning on the application for the first time um but we do have products as our Central kind of concept so if I go into the the products um section and good it didn't log me out during the uh during the list I have a list of all of my products now releas V2 had a products tab but it was a standalone products table uh it wasn't connected to anything else within the cmdb while I use the term products and digital products there the table where this is actually residing is a part of the cmdb uh this is based on the common Services data models best practices so I am helping to put things in the right place uh and in fact this probably already has data in it especially if you're using business applications or if you're using like Agile development 2.0 these will get pre-populated from that Source but if you do need to create a new one uh you can create one however it's requesting it because again this is now part of the cmdb it's more closely aligned with uh service now best practices and so you may need an approval process in order to create these records instead of just being able to create them um so we we did put that in place and then I have you know my products I'm going to go into smart Shopper uh to talk about the products for a little bit before I navigate into one of the releases so for smart Shopper I have you know an overview of the product itself and along the top I have a couple other Concepts oh and by the way for uh kayn biology if there is a Q&A that I should answer immediately just uh let me know and and interrupt me and it'll it'll be fine with me um so for here I'm I'm in the overview of a product and one of the first things you see is we have the notion of features so this is what are the things the product's supposed to do when you're looking at the scope of planning what's in a release these are optional but they allow you to start seeing what is it that this release is supposed to deliver and then we have versions so a release is making sure that a version is ready and version is also a cmdb item uh this will you'll see traceability that you start to get from leveraging these Concepts now that we are uh closely aligned with the cmdb and the common Services data model um and we can also Define a hierarchy so in this case my smart Shopper I've broken out into components those can be broken out into even more uh components where I want to define the hierarchy in a bit more uh in a bit more detail so included products optional if you don't break things down more and more detailed you don't have to do that product features are also optional but the versions are needed and again we'll get into the benefits um of saying that I have my August release my May release maybe use a numbering system service now as you all know we use um a naming Convention of countries or cities and um we're going to then be able to do release planning now release planning is allowing you to take the features and move them into the versions that you want to deliver them again this is optional if you're getting started and you don't track the scope of what's in the release then you don't need to use this at all all you would really do is say that I want to uh create a release either from this screen or from the next screen so I think I have releases no uh so this one I could create a release so I have this option to create a release which allows me to give the release a name uh Define which product it's a part of the version that it is and then we have two more Concepts that were missing from release management V2 one of these is having a template so when a release is created you could have a variety of different processes that you follow in order to validate the release so these are templates each template defines its own set of phases its own set of tasks its own set of approvals its own set of policies that this particular release will follow and we also have two different types of release um release phases we have ones where the timeline of the release matters so service now follows this kind of timeline type of approach um we have well xanadoo is well GA in a couple of weeks but it's already in Early Access um and then we have uh um you know more releases coming in the future we have them every six months and then for the store releases we have them every three months so for those releases we follow a calendar-based approach because we have very specific times that we have to be ready with our products before they become available to customers but not all customers care about the timeline of their release some just need their phases to track activities but as soon as the team is done they can move from one phase to the next without any notion of time being involved we support both Concepts um so but the templates allow you to Define what your process looks like instead of having a one- siiz fits-all or having to manually create all the steps each time the other uh item that's missen and this goes into the calendar is when do you plan on being ready for this release so I have a bunch of release Readiness dates um like I could say this needs to be ready on the 15th of September uh or this needs to be ready um you know on January the 5th these are allow these are aligning a little bit more to service now's uh release calendar so if you are trying to to Target a specific date from that point the release and all of the you know dates aligned with it will be pivoting around whatever date you have chosen that your release needs to be ready by now I'm not going to create the release for today because I have a whole bunch of releases already created but once you create it you will be able to start track in your release this might be a good time for for I think a good question in the chat so Vanessa is asking um particularly around with DPR when you're requesting a product I think really her question is what's the relationship between digital products and business application she's asking do you need to request products rather than creating a new uh business application or application service yeah so that's a good question um the actual table that this is all in is the application product model uh table which is related to a business application so starting in Vancouver there is a job that the cmdb team released put in place that will generate a application product model for every business application you have because the recommendation is every business application should have an application product model um so if you're creating them there then there's nothing additional for you to do however and this gets into how you want to track things some products that you might need to go through a release are not business applications and I believe we have a webinar coming up in October that's going to go into uh some of these Concepts in uh in more depth on the cmdb but I'll give an example of a customiz working with they were they're a bank they have a a banking platform that has microservices within them those microservices are not business applications but they do go through a um a release process so all while all of your business applications will show up here there might be smaller things that you need to go through a release process that don't rise to the level of being a business application so some of this is a it depends on your specific scenario uh but generally speaking if it's going to go through a release process it should be listed here you should have a a product entry uh for it and in my example a smart Shopper I have these kind of smaller pieces as examples to show that we can model the hierarchy but if the smaller pieces never go through a release process then you you really don't need to Define them you can just uh uh keep it at whatever level you do a release for all right um any other good ones uh that I should answer now kayin I think let's keep keep moving forward and then we'll we'll save these for later okay um so next I'm just going to go into a release so I think I chose one that's technically old so it's going to have a lot of red uh on its dashboard um but releases themselves you know tracking to release in RMV 2 was the same real experience from tracking the release or creating the release it's just a form and it would have you know the the various uh dates and it would have the phases and you could look inside of them to see any tasks that were there but for digital product release we have still this dedicated experience where we have things broken out into the dashboard so again right now um we were supposed to be done back in uh in June so our risk score is very high um there's a description you know tasks are overdue and we're we're past how much time is remaining so the risk score is basically calculated on what's remaining versus how many days are left to complete them um and then we have a difference between Readiness and end date and this is kind of a subtle difference because some customers the end date and the Readiness date are the exact same thing um but other customers need to make sure that what they're delivering is ready days or weeks before you will actually deploy it so it's not uncommon that I talk with customers where they have a Wednesday Readiness day because they do a deployment over the weekend and they want to make sure everything has gone through the change approvals before that weekend uh deployment so Wednesday is the day that things have to be ready from a release perspective so that they can deploy over the weekend it's a common scenario uh so if you have additional things maybe you have a post uh release review that you want to track that'll be a part of your release process but definitely takes place after the release should be ready ready so again based on your process uh and I'll I'll show you when I get into release execution you may have a difference of these days or they might be the exact same but we can also see uh things about tasks uh any change requests that are open features stories if we're tracking down to that level which this one's not um and then I can move into release execution which is where we have the actual uh process for this release so again this one we're at the end um I've already gone through we had a very very long planning phase uh which we had a series of tasks so I can I can select the phase by just clicking into it I have the tasks which tell me what are the things that we need to do uh tasks can either be what I'll call a regular tasks or approval tasks a regular task is an activity an approval task is something that a person needs to actually do as an approval one of the I believe about a third of respondents said that you've customized release fee to in order to get approval tracking that is out of the box in DPR so you can Define who needs to approve things um and they will get a standard service now approval request um write to them when the um uh you know when basically the task moves to in progress so they'll they'll get that and the task will not move to complete unless the uh approval is approved so if they uh if they don't approve it it will not move forward they it cannot move forward um without that approval in place so we can track all of the activities on more of a you know combine view we obviously have the ability to switch over to a list view if you want to see all of the things that are being worked on uh and then we'll go into policies in more depth in a later one but policies give me the ability let me um this is totally done so I can't add any policies to it but policies are basically the gates that you can use in order to decide whether or not you move from one phase to the next and I've got another example in the second part of this uh uh overview where we'll go into more detail on some policies we can also see the scope of the release so these are all of the features that were added so I can track them from here and if we're aligned with um planning tools which you'll see in my more detailed U view in a moment then you will be able to see those uh here as well and then finally the one I do want to touch on for a little bit longer are change requests so the interaction between change and release we have made more dedicated uh and also streamlined the process for creation from the release side so in uh in release feed2 there is a tab for changes and you could either attach an already existing change or by clicking on button butons enough uh you could make a new change request but the experience wasn't really built to be able to create a change request from release management for DPR it is designed to be able to raise a change from here if you raise a change from s so or from just our standard experience you can still link it to the to the uh release but if you're creating it from here we do the linkage for you uh we also include the more modern um uh change experience where I can have have like all my different change models uh we have our standard changes that are in place um so I could maybe just do a normal change and then fill out the information on the change request so this will be once my change loads I'll give it a a fancy name so we will call this some new change because again I'm good at naming things and I now have a change request that is attached and trackable uh from within DPR I do see some information about the release because you can get to change re quests from a couple of different areas in DPR but I now if I'm looking I can track that I've got two different change requests related to um to this particular release so however many changes you need you will be able to see them here and this includes if they are created from an automated fashion but from a getting started perspective you're able to Define your products you're able to create a release and have a connection with change which change can also look back at the release if you're using it for risk assessment or using it for change policies because again if we move the release Concepts out of change management and into release it really helps to simplify and streamline your change process so this is the getting sighted start um side of uh DPR the next which going back um to some specifics that are that are outof box with DPR that don't have a real outof box relationship is integrating with tools I'm going to use planning tools as an example but I'll also talk through some more advanced policies that you can grow into if you're on the side that said we uh we customized release V2 in order to add an migrations with third party software and then we'll also talk about um the migration so let me move into a different release let's go into fmrf 4.0 all right so this particular um actually let me go into the product talk about the Integrations so for fmr loan origination we have a section here that I skipped over originally that is called external tools this is where we start moving from having a um uh a just kind of just release to connecting with other systems in order to capture additional information so leveraging the devops Integrations which comes with DPR out of the box so there's nothing additional if you're entitled to DPR then you're entitled to these Integrations um we have these concepts of planning tools so this one is connected to uh two different systems one is a Jirus system the other is GitHub we are using this for H for example with a customer um so there's Joe's GitHub and we have a source code repo that we have connected this to we have a couple of pipelines we have both a CI Pipeline and a deployment Pipeline and we're tracking to an artifact repository so if you're a team if you're someone on the team and you're like I have a Ado uh plan that I want to associate we have a button here saying associate plans that will allow you to pull from the list of already known about Integrations so your your service now team is probably going to be involved in setting up the integration for the first time we need things like credentials to to connect but once we know about your Ado connection we know about your jira um server and that's been set up we'll then know about all of the projects that exist in those tools and connecting them is as easy as finding yours on the list uh and then choosing to associate the plan I'm not going to click associate for now because I don't need to import data and spend more time on it but this experience was meant to be something that the teams can manage themselves they you don't need um someone additional in order to get this connected it's the same for all of them for aitor for pipelines for artifacts now what that gets you is the ability to pull in additional things for the release scope it also allows you to pull in um uh additional metrics that could be coming from your build tools so if I want to know uh how things are doing in our pipeline or if I want to know how things are doing with um an artifact then uh this build didn't have a lot of uh of information coming off of it but there were some vulnerabilities found with this build um from a testing persp perspective one of our test cases failed we didn't have any functional or performance tests um we had a bunch of bugs that sodar Cube was listing for us but we will have access to this information from within DPR so pulling things from uh from uh GitHub so the pipelines we're running in GitHub and surfacing what's going on inside of DPR so that's one of the benefits but another benefit is that we're able to from a release execution perspective I can have policies that look at the data that we are getting from those thirdparty systems so I have some policies like our regression tests are passing at a certain threshold that are uh stories have Associated code commits uh so it's compliant down here I have uh no critical vulnerabilities so remember in the dashboard that I was just showing there was a critical vulnerability found because that critical vulnerability was found this particular policy is not compliant and because it's not compliant the release will not move forward without some sort of override so I am logged in as an admin that can override things but if I was a person on the product team or I was a release manager basically a non-admin then this phase will not move forward because it is not meeting our criteria it's not meeting our requirements and these requirements are set centrally so when you define those those templates you define What policies are required and everybody has to adhere to them if that's a required policy so you're able to codify your uh policies and then service now will look at them and enforce that you are following these procedures uh one thing to note is if you are using um integrated risk management through service now these policies do Connect into irm so they can also be used as a part of your um uh controls um so you can Define these controls and then this data will just feed into irm just something to note if you are an irm user uh but leveraging these connections which are now out of box give you the ability to automate where I don't have to have a person manually reviewing that we don't have critical vulnerabilities and ATT testing to it with approvals let's just use data to say whether or not we are compliant or not so that's the more automated side of DPR that you can grow into so we've got about uh we you want to take a one of the question there's two questions one in chat one with a raised hand I figure we can take those quickly yeah sure um let the uh raise hand first I don't know your name it say Samsung but you can talk Samsung SM you want to come off mute all right while they're figuring that out we'll take the chat question then um J question from Jennifer asking if they have predetermined release or product naming conventions that they want folks to select is there a way to bulk upload that or enforce that on some kind of uh basis yeah so from a release naming perspective you could definitely put a business rule in place and in fact one of the things we are looking into in the future is being able to um uh is being able to autogenerate some of the names um but I've uh you definitely could put a rule in that that enforces a convention and for products one of the reasons why we did have it as a request is because it's not uncommon for customers to bulkload the products from another source so if you have another location that they are defined today uh and you want to turn off the ability to create them manually you can certainly do that and just use the data load in order to fill out uh that table now depending on whether those are business applications or uh would be where the information should go because remember any business application you create should also create a product listing in DPR um and the reason I bring that up is because I had a customer that's uh that's going live right now and their products are being loaded in from an external source so they don't want people to be able to create them they are created in the external source and then data loaded into service now so it just magically shows up in DPR so yes you can certainly do that all right uh Samsung doesn't look like they can come off mute so if if you're want to type your question in chat we'll take it there go ahead col keep going forward all right so the last thing that I want to cover um are the migration utilities so when interviewing customers there actually we didn't get a lot of feedback on what we'd want customers to be able to migrate and in fact while we have several customers live now that we're using release management V2 so far every one of them has just decided to start fresh uh so RMV 2 is Legacy information and they implemented from scratch um uh DPR however there are a couple of areas that we see that we can help customers one is let's say you have a release in RMV 2 and it's already laid out with all the phases that you'd expect it has tasks that you'd expect and you want that to be a template well we've added a button uh now you have to have the right role so you have to have an admin role for this to show up but you will add a button that says create template which will basically tell you that the release template it's only going to include phases and tasks um you know content from Child releases is not there and if you click continue this will generate a template from uh from this release so this won't be a very interesting template but if I click create then it will create uh a template for me which will be in DPR and it's actually now going to navigate me into the template experience uh because we do have a dedicated experience to say um you know I now have this it has some phases some tasks um and we have a again a dedicated experience for generating these templates um which allow me to go in and specify what but um uh you know what all of them are and then what the the tasks are I have to complete this before we go forward but if I need to go in and six I didn't put any time that you know the um that we start um and I have Dev Dev should be first let me go and maybe add some dates to these I'll just set them all at five and Dev is really the first so I'm going to move Dev to being up top and then I have test which should be ahead and then we've got three days for uat um this is going to basically allow me to Define what my my faces are and I can say at the end of uat I need to be ready and again now I've got uh I don't think I had any tasks in this but now I I have the starting point of a template that comes from that release so that's one of the migration utilities that we uh that we created uh the other one is very similar but it is for the uh products so you can also import either um uh actually let me go into products um you also can import usually in bulk um did I I must not have turned that one on so there's also one for product that does the same thing that basically takes entries from the product table and has a button that will generate the new application product model so the digital products it will create entries there as well uh those were the two as we were interviewing customers that we got as feedback that might be helpful even though again no one started to use them yet um so the last poll that I um that let me stop sharing and switch over to that do I didn't actually I didn't mean to do that to keep sharing all right you'll launch the pH just a second uh so while we started with these um uh these items to simplify to help streamline uh the move by creating products or creating uh templates um the next thing that we want to know as we wrap up for today are there other things that you would find valuable to help with the migration from RMV 2 into DPR we launched these initial ones but we know there's got to be more so this is a great opportunity to give us feedback as to what other types of utilities would help you with that move bology and I will be reviewing these uh going through because we we own the backlog uh collectively so we'll be going through reviewing these so now is a perfect time to let us know how could we help you migrate from RMV 2 to DPR and then are there other support resources that you would find valuable in helping with this transition they will both lift side by side so this doesn't have to be a uh a uh change over like without uh being able to use rv2 so we just want to understand how we can support customers like you that are using RMV 2 that we want to help move to uh to DPR we give just another another little bit of time while you're responding I'm going to check the Q&A um so I think I've seen this one come up a bit uh what licenses is DPR part of um so the caveat I always give is check with your account team because some customers have you know specific contracts that will make this next step this next statement uh incorrect but but generally speaking itsm Pro or one of the related uh SKS from that uh is what DPR is uh is licensed with but again check with your account team because I've seen a lot of nuances between different customer contracts uh and then with when will DPR allow multiple products to be added to release um this is now the only thing I've gone over that's a part of Futures that is active work we've been doing small pieces along the way um with releasee bundles and then having um included products within a the product entry in November you're going to be able to create uh product bundles so you'd have multiple products but they're they're still managed independently yet bundled for management February is when we uh are planning to have the complete uh capability of multiproduct so multiple products in a uh single release so small small things we've been along the way and February is when it should be um all the features should be completed I'm sharing the poll now okay so there's question about more online documentation um and online content like these types of webinars so we'll definitely um look into these so I I appreciate the uh the feedback to to help us uh get you all over to um to DPR so I think let me see there was a new question that came in um will this webinar be available um kayin these we're we're publishing cor yep yeah so this is being recorded it's going to be uh posted to community if you can actually go to the next slide there yeah perfect thanks K so we have a lot of great collateral on content already on community we actually had a DPR launch and learn series that wrapped up uh last month that has uh deep dive sessions into various aspects of DPR so if you haven't checked out our community page please go there we have a lot of really good content we also have a series of short how-to videos that help uh can help you get started with DPR we also have a number of of blogs and posts that go deeper into DPR Concepts and can helpy hopefully help you understand them a bit better um and then of course uh if you haven't yet start experimenting with tpr in your subproduct environments too uh we have a question from Laura I'll allow you to talk Laura go ahead and come off mute just you're able to are you able to come up me Laura all right while you're figuring that out couple other questions coming into the Q&A uh from Freddy you mentioned upfront that release and management VT will be supported going forward should it be required is there an end of support deadline so the the endex support is each customer's contract uh so you are supported through the end of your current contract um however long that contract is uh and that's the standard policy uh for for supporting um and then are there other migration utilities the or create template so they're two right now creating templates from a release and creating a product um from the products table that can also be done in a scripted fashion so we have uh scripted support as well and that's why we asked the question because even with our release V2 customers that we interviewed uh last year when we were building DPR um no one had any like pressing ways that we could help them migrate and so far every release V2 customer has just started over so I figured this crowd would be a great crowd to ask the question broadly if there would be things that would help you so these are the first two but I doubt they will be the last we're going to go through the responses uh read them over and and see what else we can put in product to help with the migration great looks like there's no further questions and Laura's raised hand was was uh not for questions so I think we are good thank you everybody for joining today's webinar again this recording will be posted to community plus a lot of other great content thank you have a great rest of your day thanks everyone