good afternoon everyone Carousel technology and service now would like to welcome you to our servicenow federal Tech talk low code application development governance on servicenow joining us today we have Chris gear technical director of creator workflows for servicenow and Daniel bowling senior solution and consultant of creative workflows or service now at this time I would like to turn it over to our first Speaker Chris the floor is yours sounds good hopefully everyone can hear us okay my name is Chris gear and I'm here with Daniel bowling and we are part of our federal Creator workflows team and today we're going to talk a lot about low code application development governance I know in the past we've done a lot of conversations and some webinars around how to build applications on the servicenow platform and today we're really going to be taking that to the next step which is how do we scale that and be able to provide some governance around the low code application development process on the platform so first off from the Safe Harbor perspective we may talk about roadmap items today if we do talk about roadmap items we will call it out and be very clear about that um but uh we will uh you know we will do that just so you're aware that we that may came up come up today is everybody do you hear us okay all right so I want to start off and really talk about hey why are we looking at low code application governance and really is because we're looking at the world a little bit differently today than we have in the past right it's how do we deliver applications in a different way than we have in the past how do we achieve speed efficiency and experience how do we deliver things quickly how do we provide uh our our employees and our customers with more efficient experiences and how do we provide a good experience for everyone to be able to use these applications and what are we looking for and this is what we get asked for a lot from a lot of our customers if we're talking with you know a lot of the leadership is about hey how do we do that but how do we do it by empowering more technologists our traditional software development organizations aren't scaling at the pace that they need to to keep up keep up with the demand for Mission and business applications that are needed how do we modernize core systems without ripping and replacing them how do we wrap a new layer around them so that we can achieve value and we can provide more capability without uh getting rid of those core systems and then also how do we do this all at scale and this is where we're really going to focus today which is we have low code tools to build applications we you know we can do that quickly but how do we deploy them into production at scale in a way that we have the confidence that they provide that they're being done securely and that we've got the oversight needed to feel comfortable about doing it at scale and so that's really where we're going to look today but where does this all stem from wherely where are this all stems from is from the desire for organizations to achieve hyper Automation and Hyper automation is a term that's been around for a little while it's a you know I think it started from some of the analysts um and this is the definition of hyper automation right hyper automation is a business driven disciplined approach that organizations use to rapidly identify that and automate as many business and I.T processes as possible that's the Holy Grail um to being able to uh deliver value more quickly and so looking at it from that perspective how do we you know how do we how do we achieve hyper Automation and when we do that we really look at it from servicenow's perspective as there's a core uh technology uh that's needed we call it the digital Enterprise but then also on top of that there are other technologies that people that organizations need to invest in to ultimately deliver on that hyper automation division whether that be process mining robotic process optimization orchestration Integrations artificial intelligence or process Automation and all of those Technologies come together to be able to achieve that hyper automation Vision but as you do that you know the the environment gets more complex and you need to be able to have more comfortability and more insight into what's going on so today again we're going to really focus on the digital Enterprise and what is the core of a low code application development governance model and what does that look like and just as an example and it was um a lot of you have been on some of our previous Tech talks where we've talked about lots of you know different applications and how to build those applications this just an example of some applications that folks have built in the federal space to give some people some ideas of hey what are the different types of applications that people are looking to deliver on the servicenow platform and these will be in the slides you know in the in the recording but when we look at development on a low code platform and on service now really what we're looking at is since servicenow is a fundamental platform you have all of the capabilities of that platform to be able to use at your disposal for when you're building your applications and you can see some of the stuff down at the bottom whether that be delivering through various experiences web mobile chat Bots text and messaging or reusing existing out-of-the-box capabilities through process automation or some of the intelligence components that are part of the platform what we do is provide you development tools and governance tools to be able to take those that take the platform and build your applications at scale on top of it and being able to do that through a combination of different creators within your organization So today we're really going to focus on that top white box app engine management center which is the tooling that we are looking at to provide governance uh and we're going to go through and talk a little bit about what that looks like and then also show some demonstration of the app engine management center and how it provides a starting point for an organization uh to build a governance model around and I see some questions popping up in the chat we're going to get we'll take a look at the questions as we get closer to the end so when we look at application governance we first have to look at how do people use the servicenow platform in a low code development uh approach and really we see three primary models that people use servicenow from a low code perspective the first one is it's another tool in the it development toolbox maybe you have some c-sharp developers Java developers you know web developers whatever else it might be and you want to add low code as another tool in the development toolbox to be able to tackle uh applications in a in a different approach than you have historically that is a great use and the Dan a lot of people a lot of organizations start that way with low code development maybe you've been successful on that and now you're looking at how do I use low code to be able to allow more distributed groups throughout my organization to be able to build low code applications we kind of talk about that as distributed development and so maybe you've been using it as an I.T tool for a while but you want Mission units or business units that are distributed throughout your organization to be able to build their own applications and you you know an I.T wants to be able to have insight into that and to be able to make sure that those organizations are living within the within the rules and the guide rails that you've put in place and then the third one is maybe your organization is going all the way into a citizen development model where you want to open up a low code platform for uh anyone or the majority of an organization to be able to build applications upon and again in that model having a governance model and having tooling to be able to Monitor and manage all of those applications is absolutely critical but governance tools are important in all three of these different uh the all three of these different scenarios just how they apply might be slightly different so regardless of which one of these three-year organization might fall into what we're going to talk about today is very relevant to that and so that brings us to this this is a software development life cycle uh we did not come up with this this uh you know this model has existed since software was first started being built um every piece of software ultimately starts with an idea and ends with a system being retired or hopefully the system is retired you know when it's outlived its usefulness uh and in the middle right you build validate deploy maintain Monitor and you know and then ultimately retire and there's iteration on that application you're adding features you're you're doing bug fixes whatever else it might be this is the life cycle of software in general and at the end of the day when we talk about low code we're still talking about building software we're still talking about building software applications so just like a job application might go through this process with a traditional devops Pipeline and all the stuff that goes with that a low code application goes through this process as well and how it goes through that process has a lot of similarities with you know a traditional development but it has some differences as well but at the end of the day you still want tooling that can help you in these different phases and that's really what we're going to look at today so we're going to look at local development all the way from ideation and intake all the way through retirement of applications and look at the tooling that we've put in place as part of our app engine management center product that will allow you to get insight and tooling that supports every step in this process in your low code development life cycle and so with that we're going to you know look at it from the perspective of app engine management center again which is some of the tooling that we've built to be able to provide the starting point and the foundation for you to build your governance process around your you know around the local development in your organization and so we're going to do is we're going to jump right in and we're going to look at it and we're going to start with intake and so intake is the where everything starts hey everything starts with an idea and how do you collect those ideas and this is probably the area that differs the most depending on how you're using low code in your environment um and who is providing you know who is providing those ideas and so we're going to look and and show you some uh some capabilities that come out of the box and then you know you can look at it from your perspective and figure out how it applies to your organization but Daniel we're gonna take a look at it now is what do we have out of the box when it go when it comes to intake how can people use app engine management center to manage the idea intake process for low code apps in their organization [Music] yeah absolutely so uh like Chris was saying a lot of these different phases we have different kind of uh out of the box solution tooling that can be configured to your own process and probably one of those things that you definitely uh can configure is this application intake form which comes as a catalog item that's installed with app engine management center uh so I'm going to jump over and everything that I'm going to demo today is going to be just what comes out of the box with app engine management center and then as I'm going through I'll make sure to highlight hey here are these things that you definitely would would want to configure in your environment but we at least provide a starting point so right now I'm logged into the employee Center as an employee Jimmy is who I'm impersonating right now and Jimmy is someone that hasn't done development on servicenow before but is going to apply for what we're going to call citizen development for this request so here's our catalog item that comes out of the box Jimmy's going to fill out this catalog item I'll skip over some of these things here but you can see we've provided a starting point for different questions you might want to ask someone that wants to build an app for the first time on on the platform so it's a process repeatable email Excel based processes how many users are involved maybe whether or not it has sensitive pii data might change the way that you go about the approval process and some other information like that but as it is I'm just going to submit this request so now Jimmy has submitted this request and I'm going to jump into actual app engine management center so now I'm going to be acting as the app engine administrator [Music] and as the app engine administrator I use this tool called app engine management center as kind of my central hub for managing development that's happening uh happening in my instance so we can see from the home page here the overview we have lots of different kind of metrics that are popped up here to bring them to my attention first and foremost but I'm going to jump into requests and this is where I see three different types of requests that can come in intake collaboration and deployment so that first one that was just submitted by Jimmy that time off request we see I can open up that request and now within your process you might have any given number of uh any given number of parameters that you would have in place to approve this request um but the uh you know based off of whoever the user is maybe what department they're a part of uh you can have your own kind of review process But ultimately what you can do is use app engine management center to actually approve this request and a key thing to do when you're approving the request is to make sure you're giving the user the right permissions based off what they're asking to do so I'm going to scroll down here and you see we have four different options out of the box I can improve Jimmy to create slash edit applications I can say I only want him to be able to edit specific applications I can just uh maybe I'm just using this request to document the intake process but I'm going to manually configure permissions myself or I could just not give the request or permission at all so what we're going to do is give Jimmy the ability to create and edit applications foreign and Mark that catalog task complete and I can come back to uh Jimmy's initial request here and now that I've completed that permission selection I'm able to approve his request and there we go so now we have a documented intake process Jimmy we captured information about what he's looking to do we've approved his request and we've actually done some automation on the back end but I'm going to get into that in the next section next section so we'll jump back over to the uh software development life cycle yeah so if you look at intake right I mean obviously that scenario there we showed more of a citizen development model right where maybe you've got or a distributed development model where you've got somebody maybe outside of it who has an idea for a application that they want to see built on the platform they're able to submit that idea it's able to go through a review process and either get approved or rejected you know in the government space maybe the people the group doing that review is a architecture review board or it's uh you know some sort of cab that's looking at those requests and determining whether or not that's a good fit to be built on servicenow whether or not it's an application that already exists and then also what the path forward might that be but it gives you a little bit of a process to be able to follow um or if you've already got another process that you use for uh demand or demand management you can you know just use that process and integrate that with service now as well but that's just looking at it you know looking at it from that perspective if you're not using citizen development you're using it for a different model that intake request still might be useful for you but you might tweak what some of the questions on there are and how exactly it's used but it gives you the foundation to be able to do a light demand management but moving on from there right after an idea is in the system it all comes down to hey you know now you need to build something and when we when we look at building we talk about app engine app engine studio and so um with app engine studio um you've got the ability to be able to uh do the building and you know either start with templates you know start with some of the out-of-box guidance collaboration uh and this is the development Tool uh that we would be using for building um we're not going to spend a lot of time with app engine studio today we've talked about that in some of our previous uh webinars that we can go you know we can go back in and get links for uh but um Daniel after that intake form kind of came in how does Jimmy get access to the tools that he needs to be able to build something yeah so one of the benefits uh app engine management center out of the box once a user is approved based off of that intake intake form uh they're automatically added to the app engine users group and receive this email you can see an example of an email on the right hand side here with a link for them to be able to open up app engine studio in the dev instance so in the the instance that you've configured to be your Dev environment within your pipeline um is what this link will do so it's actually provisioning those user permissions in the dev environment uh so Jimmy you know he's probably never even used your Dev instance before uh but now we've automatically provisioned him there so at the top of my screen if you see the different tab groupings I'm going to jump over into the dev instance that I have here in my in my pipeline and I'm going to go ahead and impersonate Jimmy Jimmy Hargrove and if you click that link in the email it would automatically open up app engine studio for him we're just going to do things the manual way and I will highlight here that of course development is still happening in the dev so this hasn't given uh Jimmy any additional access it hasn't edited its permissions at all in the production instance by default here we're just giving in permissions in the dev instance uh now Jimmy's logging into app engine studio and because we gave him that create app capability yes this create app button and I can put in my time off request app [Music] and like Chris mentioned this adaptive engine Studio we're not going to really spend any time talking about app engine Studio the tool but just wanted to show kind of that access provisioning that happens and then maybe as Jimmy's developing this app he realizes he needs some help in certain areas maybe specifically in integration maybe this app has some sort of custom integration as part of it so he's going to request a collaborator as part of this app so he's going to pick one of his friends let's say Christopher Markham to be a collaborator in this app and instead of editor he's going to make sure Christopher only has permission to do the thing that he is needed to do in this app so we're going to make him an integration specialist so Jimmy just as my end user here doesn't actually have the permissions to give Christopher the integration specialist role but now he submitted what's called a collaboration request so I can jump back over into um app engine management center and as the app engine administer administrator I receive that collaboration request that Jimmy just submitted so I can open that up we see it was submitted by Jimmy to invite Christopher in to collaborate on this app so I'm going to go ahead and approve that and again just like we saw in that intake app uh Christopher is now automatically receiving the appropriate permissions only to be able to edit that app in the specific way he is intended to edit that app so we have a lot of granularity in the permissions that can be granted in that way so I'm going to jump over here and I hope that I didn't beat the automation and impersonate Christopher just to show you that what that experience looks like for him he would have received an email that looked very similar to the one that Jimmy received when his initial request was approved with a link to take him into app engine Studio so now is Christopher I'm opening app engine Studio as expected I don't have the ability to create an app but I do see that time off request app that I was granted permission to and importantly within app engine Studio this ability to edit the experiences and the security of the app is is locked down for me I'm only able to add logic and automation so we're able to get really granular with the collaboration permissions that are granted Within within app engine Studio here no it's really good I think that if we look at that really this is all about making it easier to scale development right A lot of the stuff you've been able to do for a while and be able to Grant people permissions be able to track collaboration requests but it all would have been done manually through emails and spreadsheets and tracking it through that process what we're trying to do here is give tooling that out of the box gives you the ability to manage these processes on the platform so that it's able to reduce the time and effort I forgot to mention one thing to add there in terms of being able to configure it to your process those different levels of permissions that a collaborator will have within an app those are editable and configurable as well so you could create your own custom uh permission that says you're only allowed to edit data or only allowed to build a workspace for instance as part of an application so that's able to be configured as well powerful especially as you open up the aperture as to who might be a collaborator in your environment being able to restrict those restrict people to just the permissions that you want them to have is critical but if we move on from building and we get into validate and then deploy and maintain this is I think where it gets really interesting from an automation perspective right because at this point it's hey you know Jimmy's done building his application he submitted that application uh and he said hey I'm done with this and now you want it to move from your Dev environment to your test environment run some testing and to be able to ultimately get approved and then move to your production environment historically a lot of people would have done that manually with update sets in your Dev environment you would have exported your update set you would have moved that over to your test environment you would have uploaded that gone through the process and then repeated it moving into production some of you have probably moved on to app repo which does provide some ability to streamline that process but what we're going to look at today with app engine management center is a tool called pipelines and it's the ability to build a CI and CD pipeline within servicenow that allows you to fully automate the process of moving an application between Dev and or however many environments that you might or however many instances you might have in your ultimate pipeline So Daniel what does that look like yeah so pipelines uh being configurable what we're going to go through today we have a Dev instance a test instance and a prod instance uh it will show an example of deploying that app that we just created um live right now deploying it from my Dev instance into test and then into prod so I'm going to jump back over to my Dev instance and impersonate Jimmy again uh Jimmy again if you're losing track of the names is the person that uh just initially submitted this uh the intake request and created the created the app himself impersonated the wrong Jenny Jimmy hardgrove so Jimmy Hargrove submitted that request created the um created the time off request app we had Christopher come in and collaborate so now Jimmy comes in and of course we imagine this is all populated and filled out with information and so Jimmy's able to click the submit button here now you can see we have a pop-up here that shows Jimmy what he can expect from his it team maybe the the app engine administrator and platform and or platform team as part of this review process uh but he's able to click submit come down here and he's required to enter very detailed and helpful release note release notes which you'll have to imagine for this demo uh we see the version numbers automatically iterating here uh so our first time deploying this app so from Jimmy's perspective uh he's done his job he built the app and submitted it for review now if you're catching on to the the trend of the demo so far you might be able to guess where I'm going to go next back into app engine management center and Jimmy submitting that request to deploy the app is visible to me here as the app engine administrator I'm able to open up that deployment request and here I see a lot of information about the app that was built I can of course actually open up the open up the app that is requested to deploy here in the dev instance and review it manually myself and any kind of automations or review process renewal process that we want to add into this can be configured but as it is I'm going to click approve here and in approving that deployment request a lot of automation is happening and so I think the best way to describe that is actually using this slide here which looks very complicated and complex the first time you're looking at it but I think we can we can make it make sense uh fairly quickly here so the three gray boxes on the top are three Dev instances that we're going to go through today the dev test and prod instances below that we have app engine management sensor if you've been paying very keen attention you may have noticed app engine management center is running in my production instance but we're using it as a control center across all three of my instances so that's represented by the purple box there and then the app repo which we haven't actually seen yet on the screen the app repo is hosted by servicenow and sits underneath all of these instances so the actual process what's happened here we've used app engine Studio as our tool to build this app we could have also you know used a legacy Studio or Dev Studio or just the next experience UI or a combination of all three of those things to construct the app but from App engine Studio we submitted that deployment request one thing that will automatically happen if you if you did have your app engine Studio Connected To Source control so it automatically commit whatever those latest changes were or an initial commit potentially to your git Repository so we're highlighting that over here that that would have happened if we had Connected To Source control but as it is that deployment request was submitted in app engine management center it also published that app to app repo so we captured that first version of the time off request app was published into the application Repository then I logged in as the app engine admin and approved this deployment request for that app to be published or to be installed in my test instance so that's all the way through this blue line here uh that app the time off request as it was published in the app repo was installed into the test instance and we're still not even done with all the automation that just happened when I clicked that approve button uh because next if you're familiar with the ATF or automated testing framework or instant scan we won't go into too much detail about what those things can do today but just as an example um maybe every one of my custom apps that are deployed across my instances I want to just check to see maybe is was there any any custom script written as part of this app um or are there any external Integrations as part of this app or maybe I'm testing a new user role that was granted and it is a great user's permissions that I'm not comfortable with we can build different instance scans to check for all of those things automatically that way we don't have to do a kind of manual review process of every app that comes through at least for those specific things so when I approved that deployment request installed the app in the test instance and ran ATF and instant scan as we've configured it to run against that application so I'll jump back over here into app engine management center and I'll show after having approved that request I can click on this deployment environment results and in our example here we just ran a single instance scan which you can see returned as have has error false which also means it so did not have an error which is a good thing so we had a one single successful test run against that um against that time off request deployment I'll actually jump into my test instance here this is my test instance and come over to installed here refresh this just to show you that the that app did actually install in the test instance so we're up into the second instance of the chain here wait for that refresh to stop there it is time off requests installed today importantly uploaded by the aemc pipeline user uh so our service accounts actually moving that app from the app repo into the test instance so I'm jumping back into my diagram over here the last piece uh it would actually be deploying it from test or deploying it into prod so once I approve that deployment request to move into test a new deployment request was automatically created to move that same app into prod of course we're not actually moving it from test to prod but we're just going to be installing the app into our production instance from the app repo just making sure that's clear that's exactly the app that was installed into the test instance is now going to be installed into the production instance so so I want to jump over into the pipeline view of app engine management center here are three different instances and I can expand and collapse them to show the different apps that have been requested to be deployed across them so right now it looks like we have uh one other request uh one other app requested to be deployed from Dev into test and here we see our time off request as well as a few others that are currently in test requested to be deployed in the prod so just another way of kind of visualizing and navigating to these requests so I'm going to go ahead and approve that one and that's our final step and again this is very configurable if you have different different types of pipelines or different types of approval processes to go through as part of these um appointment approvals that can be configured but this is just what I've showed out of the box is how that app ultimately goes from App repo into the production instance to where the users can start start using it that's great and I think if we look at that holistically right you know if we look at how things exist today or existed in the past with update sets and being able to manually move files and get them over there's a lot of room for a potential error there's a lot of room for things getting lost there's room for things getting moved and maybe they didn't go through the approval process there's all sorts of you know exception cases in that model so by being able to put a pipeline around your applications and being able to have a lot more control over what moves it just gives you that better insight and control and just comfortability that you know exactly what's going on in between your environment and you know exactly what's going into production because you've got all of the traceability of of all the applications that have moved through all of the steps all right so now that we kind of talked about hey how do you get start with an idea how do you build an application how do you validate it and deploy it and maintain it and you can imagine this might iterate a lot of times now that that application makes it into production Jimmy might go back and do version 1.2 and 1.3 and to be able to push those through and you'd get all of that traceability and all of that history that goes with that and be able to see exactly what happened but now that that application's in production now we need to monitor it and this is where you know a lot of times organizations have the least insight into is hey now I've got a bunch of applications in production what's going on with them right hey when we build this application when the cab approved this application you know the request said hey this application is going to be used by 5 000 people every day tens of thousands transactions is going to be the best thing since sliced bread and it makes it into production is it really being used like that how do you know or vice versa you've got an application that Jimmy built to help him out maybe a personal productivity ad that got approved to go into production but maybe it's actually being used by a lot more people than you originally thought again how do you know that um and then it also takes us into retirement how do you know when applications are ready to be retired from a metrics perspective how are you able to track that and so that's kind of the last piece of some of the tooling that we have provided is looking at how do you monitor applications in production and get the metrics and then ultimately how do you use those to determine if something is ready to be retired or needs to be kept around so Daniel from that perspective once the apps in production what do they get and so a few things that will show app and developer monitoring uh kind of providing a comprehensive holistic view of all the apps and developers that are developing custom apps in your instance as well as the actual usage of those apps that have been deployed as Chris was mentioning so I'm going to jump back over into app engine management center and as the app engine admin I have visibility into all of those things [Music] and I do want to call your attention to the uh these five different kind of tabs that we have at the top here so overview page this is that first one that kind of shows some high level um high level information requests that is where we approved any of the three intake collaboration or deployment requests pipelines that showed that a series of environments that the app went through but see what Chris is just talking about our custom apps page here this is our One Stop Shop to see all of the application all of the scoped applications that have gone through this process in our in our across any of our instances so you can see some high level metrics here with some information showing how they've changed over time we can also look at uh different apps by department so maybe if you're in full-fledged citizen development mode uh interesting to see which departments are developing and ultimately deploying the most applications and then we can also scroll down here and this is just an actual list of all of the apps that are existing at any point in our in our in our pipeline here uh so of course in the most recent one being that one that we just deployed and is installed in our production instance uh that time off request so it's really nice to have this kind of One-Stop shop location to see all of your custom apps uh and I'll jump into that time off request just to show some information available within here uh so we literally just deployed this app so as expected uh we're seeing zeros but we would be seeing the number of users that have accessed the application uh the number of records that have been inserted the number of updates that have happened to that underlying data any user experience analytics dashboards that we have associated with this application so we're able to as Chris was mentioning monitor how often that application is being used and be able to make informed decisions about maybe migration folding it into another app or just retiring it if that's the appropriate decision uh we've only had one version of this app deployed but we can see the deployment history all the different versions that have been pushed through the pipeline and conveniently we can see the actual collaborators that contributed to this app Jimmy Hargrove being the owner and then we also as we saw Christopher came in and acted as that integration specialist So speaking of developers I'll hop into the uh the last tab here the developers tab uh and then so this is you know similar to looking at the custom apps but yeah we want to look from a developer perspective all the 96 developers that I have in my instance here how many are active changes what departments those developers might sit in and then I can come through on a person-by-person basis and actually look at the apps that each person has contributed to um so I'll jump in let me go to Jimmy's [Music] oh let's pick a random one Sydney Carter so here we would see listed any apps that Sydney Carter had worked on or helped with here we go uh so we can see Cindy Carter is one of our uh she's in the I.T department and is one of our lead uh one of our developers that has you know contributed the most to this program so she's developed seven different apps we can see all the different intake requests that Sydney has submitted the collaboration request Destiny has submitted and then of course ultimately the actual deployment requests so it can just be useful to look at a person-by-person view of how they're contributing and how they're they're taking part in Development Across My instance so we worked through uh really all those five pieces of app engine management center the first being the overview tab uh requests here in tank we talked about the very first portion of that software development life cycle then we showed building in app engine Studio what that looks like and submitting a collaboration request again managed an app engine management center and then ultimately deploying that application going through some of those automatic testing what we did today was just uh it was kind of a dummy test of an instant scan but just to show an example of how some of those app tests can be done in an automatic fashion and then ultimately deployed across our environments and just to uh just to keep me honest here I'll go into the uh this is in my production instance and refresh this and show that the uh that time off request app that we all saw what we all created here uh live together during the event actually is installed in my production instance here installed today so all that automation worked and we successfully installed that app into production and then we showed how we're able to uh monitor monitor all of the apps that we've deployed and then ultimately retire them if we so choose yeah I think this has been really great right we've looked at the software development life cycle all the way from intake to retirement and some of the tooling that app engine management center provides you out of the box to be able to address each of those phases now exactly how you use this these tools inside of your overall organization's governance process might be a little bit different might be a little bit unique but the tooling gives you a starting point and information and data to be able to use as part of your governance process and as you can imagine you know from a servicenow perspective everything in the servicenow system is very configurable uh and able to be tweaked exactly to how you want to use it all of this all of these tools is can be used as a starting point and if you need to make changes to what the intake looks like or how exactly deployment requests go through the system and maybe you have some automatic automatic approvals versus manual approvals based off of different data you're able to do that you're able to tailor all of these tools on these processes to your needs just think of this as a starting point that we're going to continue to grow and expand From Here app engine management center is a relatively new capability that started out in San Diego and has been enhanced in uh Tokyo and Utah with further enhancements in Vancouver in the future releases to come so this is really just the beginning and the starting point of all of the governance and management capabilities that we intend to provide on the platform to help you scale your Development Across your organization and from that perspective I think you know uh from a presentation perspective I think we're done we have a few minutes left if there's any questions in the Q a or if anyone has any uh any questions we'll try and take a look at that and address any of those thank you q a and I saw the question um we are servicenow here not not a third party I'm doing this presentation so Chris and I work in a federal creator workflows for servicenow so there was a question that came in about app engine management center requests um tied to uh some of the itsm capabilities so I was telling you something we didn't address today um however it's a great question so when we look at uh when we look at the deployment requests for example um there's some enhancements going on in deployment requests around how it integrates into a broader change management and cmdb system and so there's some of the capabilities that exists today and some of the capability that's still coming but you're able to be you know you're able to link deployment requests into your broader change management system and then you're also able to have applications as they go through the deployment pipelines automatically be published into your cmdb as applications as well so that they're part of your overall cmdb from that perspective there's another question this came in how many is that is the question in how many federal agencies are using um the citizen development model foreign put that in can just add a little bit more detail to that question I'll start to answer the questions assuming that's what the question is uh okay so um when we look at the different development models from a federal perspective um app engine is in the vast majority of federal agencies that have serviced now and they're using it for either extending out of the box applications or doing some level of tailored development a lot of organizations are you doing distributed development so they're doing development from a perspective of central I.T but also allowing different organizations maybe distributed organizations or different bureaus to be able to do development and then there are some that have moved more into a citizen development model quite frankly um you know citizen development is not widespread throughout the federal government as of yet but you know distributed development is actually pretty common and so I think the next question that just came in if I saw it pop up right is uh how common is it to have non-it development folks creating production applications and again that's going to vary widely by organization um some organizations do it quite a bit other organizations don't do it at all um and so there is you know there is a there is a large gap there um I will say though that we are starting to see a trend where it's not necessarily again all the way to Citizen development where maybe a non-it like maybe a business unit user is building the entire application themselves we do see some of that but we are seeing more involvement from the business or the mission where they are collaborating with it and applications in new and unique ways compared to how they've done it in the past so Daniel earlier showed the whole collaboration request we are able to invite people into an application uh development uh process but do it with very controlled permissions and so one of the things that we talk a lot about with customers we actually just were uh Scholars with a customer couple of weeks ago where they're having more and more people outside of the traditional development uh outside traditional development teams whether it be business analysts or you know power users or whatever else it might be be invited in to be able to do things like build screens build reports build dashboards to be able to build the components because they're the closer to the actual business and the mission need and you can bring them in and let them do those tasks maybe without having allowing them to change the data model and so there's there's new and unique ways that we're finding people use these capabilities to kind of grow who can contribute to Applications even in organizations that aren't moving all the way to a pure citizen development model and to Echo that um one thing I've seen a few of my customers uh are starting to get requests from Mission groups who have maybe an embedded partner an embedded contractor that they've worked with historically that also happen to have a professional servicenow development resources so they have professional servicenow developers Mission comes to it and says hey can we build an app on your instance in the you know the platform team is thinking well you know we don't have extra resources extra resources to expend on that app but if you're bringing the resources how can we say yes to that request so that's just another example of like a non-it quote-unquote non-it developer but it still it could even be a professional service now developer developing production apps in your instance and these are some of the tools that kind of help you say yes to those types of requests if you want yeah so the question just came in can we govern changes like configuration and properties using App engine management center so the short answer is app engine Management Center is really focused around scoped application so anything that is par anything that is deployed as part of a scoped application can fall within this process and be and be managed by that um and so you know if you're making configuration options to a screen or to a report or to a table and you're bundling that together as part of that scoped application then yes um but it today it's not going to manage um I'll say data changes uh within um you know within it within a table or within a system property or something along those lines there are other ways to be able to kind of go down that path and happy to talk if you reach out having to talk with you offline about that so I think with that I think we're about out of time so Clarissa I'll turn it back over to you to kind of wrap us up thank you Chris I'd like to thank all our participants as well as our speakers for being with us today we hope the information you received during this webinar has been helpful