- Hi everybody and welcome to the Citizen Developer series of App Engine Management Center: How Are We Going to Set Up a Pipeline? My name is Dale Dunkerley and I have with me Paige Duffey and we're going to run with through with you the lab on how we can set up App Engine Management Center and the pipeline that requires the deployment. So a little bit about me. I'm a principal product success manager within the creator workflows. I work within product success and helping people adopt App Engine, App Engine Management Center and work with citizen development. I've been with the company a few years now. I've been with ServiceNow for over 12 years, but I've also been as part of the partner workspace and also been a part of a customer. Anyway, I will let Paige Duffey introduce herself. - Thanks Dale. So as Dale said, I am Paige Duffey. I am also a product success manager with creative workflows. I have been with ServiceNow for about two years, but prior to that I have worked at a variety of customers for about 13 years. As far as citizen development goes, that's something I have done in the real world as a customer. So quite a bit of the experience that I have and I get to give to you all is from that experience as a customer. So, and back to you Dale. - Well thank you very much. Alright, well let's get on with the lab. So let's look at the agenda of what we're going to get through today. Well first of all we're gonna look at the power of low-code and how we're going to drive that with things like App Engine Studio and App Engine Management Center. Now these particular products have actually been around for a little while, look a few different versions, but the updates to this with things like Vancouver and Washington have made some of this space quite exciting. Paige will then talk a little bit about the importance of governance and talking about app intake collaboration pipelines and deployments. Then to this we'll have some good lab learnings. So what is the power of low-code? Well, ultimately what we're looking for us to do here is do more with less clicks and less code, really. Essentially what we're looking to do is use things like App Engine Studio to generate apps that people themselves can actually maintain no longer having big scripts and you know, really funky sort of tool sets to do tables and all of these other command line types of functions. What we're really looking to do here is do have a lot more citizen developer point and click choice options and data-driven types of app development with the low-code tools we have today. We have things like templates which provide guidance. We have collaboration and also integrate into the existing platform and not just standalone. How does that then kind of get translated more than anything else? Because it's great to build an app, but usually you're doing it in things like development environments and other areas to make sure you're not doing it in production. So we have things like App Engine Management Center, which will actually help us move all of that code or manage all of those apps in its entirety. It'll allow us to understand who's got what access to the environments, what applications are being requested. We'll also look at collaboration tasks. So maybe you will need that actual developer that will actually help you get through all of the different scripting tasks that you may need. Then we'll look at deployment tasks and pipeline monitoring, just how do we actually get an app all the way through from the dev environment through to the test environment and finally into production. But with that, as you can imagine, it requires a bit of governance. Do you think Paige, could you give us a bit of an overview of what's required here? - Absolutely, so we can't really talk about App Engine Management Center without talking about governance. App Engine Management Center is our, you know, tool for governance. As you'll see as we continue on, we will talk a little bit about application intake. That is kind of the first step of governance. We really look at this from the point of view of the application lifecycle and you can't start an application without intake. Part of App Engine Management Center is a plugin called application intake. As you can see, it is a way to collect ideas from developers and then take and automate their permissions into your sub production instances via the same pipelines that we're going to set up. Once we actually have our developers in our sub production instance developing, you may find that they need collaboration. That may be collaboration from other citizen developers. It may be collaboration from other developers within the ServiceNow core team. So another one of the plugins that comes as part of AMC and again is part of that governance is developer collaboration. It's the ability to invite someone into your application as an editor or an owner or honestly any other type of access that you need to give them to manage that app. So maybe you don't want them to be an editor, but you do want them to be able to create a catalog item or edit a catalog item. You can grant that granular access with developer collaboration. And then finally, of course the pipelines and I feel like this is probably what everyone is really excited for, but our configurable pipelines allow for the automation of deployment from your sub production instance into your production instance and they are very, very configurable. So you can have dev test stage production or you can just have dev and test where some customers, they may just have dev and production. You can configure that pipeline to be what you need. On top of making the pipeline what you need as far as the instances go. You can also configure things like instance scan or ATF, so you can run whatever ATF your organization needs or whatever instant scan checks your organization needs. And with that I will pass it back over to Dale to cover what we're gonna learn today. - Thanks Paige, so essentially at the end of this particular lab we're going to be doing three things. We should be able to set up App Engine Studio from end-to-end. You should be able to then create an app inside App Engine Studio and kind of configure it either using a template or by default. And then we'll be looking to move that app from the development environment through the test environment and into the production environment, essentially using that pipeline that Paige described. Okay, so let's get on with the lab and kind of understand what do we need to do first. So the first one we need to do is set up the app engine studio. Now one of the things you need to kind of be wary of is that you'll be working with two separate different instances. The first of the one will be your development instance where you'll do all your work and your development and your app engine kind of work. But essentially the second one will be both a test and production instance where you'll be able to move code from one to the other, but it'll actually function as both of those. Don't worry, we've set it up so you can still get all of the full benefits and features out of both of those particular areas. However, in the app engine studio, it should take around about kind of 20 minutes or so and we hope to see you back in a couple of minutes once you've finished the lab. - All righty, welcome back. So now we're gonna move on into section two. In this section you're going to actually start setting up the deployment pipeline. As a reminder, we do have two instances, dev and test. Your test instance is serving as both test and production. This is really important in this section because you're going to be setting up something in both instances. So pay close attention to the instance you're supposed to use on each step. This section should take about 30 minutes, so we'll see you back in just a few. - And welcome back. Hopefully you've kind of worked through the deployment pipeline. I believe it might have been a little bit challenging in some places, but it does take a little bit of time and there are a lot of components to it, in terms of environments, pipelines, lots of even credential information, but hopefully this section will be a lot easier for you. This is about setting up the application intake. This is about how you can actually set up almost like a set of demand where you can say what app do I actually want and which ones do I want to approve for people to start to actually build in the developing environment before they've even I've given them access. It'll also automate access into those environments if you want that too as well. Anyway, I will let you get on with the lab and hopefully we'll see you in about 10 minutes. I hope you were able to set up that application intake. So now that we have our developers submitting applications and they're ready to go, we can talk a little bit about how to get other collaborators into that application you just created. So in this next section, that's exactly what you're going to be doing. You're going to be creating an application and then you're going to be adding collaborators. It should take about 10 minutes. - Okay and welcome back. Hopefully all of those sections you've done up until now have gone quite smoothly and you haven't had to backtrack a little bit. But if you've completed all four of these sections, essentially you'll be ready for section five. 'Cause essentially everything we've done up until now all leads to this last section. It's about managing that deployment into production. We'll be able to kind of take that particular app that we've got, submit it into deployment requests and into the different areas within and we can close off all of the tasks that are being generated as part of this particular lab. Anyway, won't give too much more away and hopefully we'll see you in about 10 to 15 minutes. - Alrighty, welcome back. It looks like you finished the lab. Now that you've finished every single exercise in our lab, you should be able to set up App Engine Studio end to end. You can also create an app end to end. And then lastly, you can manage that deployment from dev all the way to production using automated pipelines. I'm gonna go ahead and pass it back to Dale to close this out. - Thanks Paige, and thanks to everybody else who's come along to this lab today. Obviously it's something we feel quite passionate about and we feel like this is one of the ways forward in terms of being able to put low-code developments and the the best part of the development into the citizen developer's hands. So to make it easier and better for everybody to be using, thanks for coming in and listening to us and kind of enjoying on this lab. Give us a shout out on either LinkedIn or our email addresses and we hope to see you soon.