app engine studio three very little words generating a very large amount of buzz in the servicenow community and might i add for a very good reason perhaps you've heard of this buzz and are seeking to learn more about this tool perhaps you've arrived here after seeing my first video defining app engine studio perhaps you've seen that and you're seeking to learn more if either of those are true you are in the right place in this short video i will be guiding you through how to build your first app using app engine studio one of the two development environments that service now offers designed purposefully for the low and no code audience my name is laura mcmanaman i'm a seven year member of the servicenow community and your developer advocate of the day and with that being said let's jump right in as a quick refresher app engine studio also affectionately known as aes is a development tool for creators of varying skill levels allowing them to build applications that meet the immediate needs of enterprises of various sizes aes is accessible like every other application on servicenow through the application navigator with the intention of setting up new developers with the servicenow best practices from the beginning of their developer journey you can see that from even the home page this is exemplified in a variety of ways as opposed to leaving the platform to gain assistance or documentation these types of things are now embedded directly into app engine studio if you're seeking great examples for custom maps and various ways that servicenow can address real-life business problems there's also the addition of templated applications in addition to being a phenomenal learning tool these template apps are actually fully functional custom apps as well you can deploy them at any given time both the ones that we supply and even templates that you eventually can create yourself and are a great tool for assessing an internal audience or internal customer for how their lives could be greatly improved through use of servicenow's custom applications let's try out this time-off template application as an example first and foremost developers can set up scopes for their various applications scopes essentially act as your app's membrane securely letting the right users and information in and out within each scope developers are then presented with the four pillars of app development data experiences automation and security the true cornerstones of any phenomenal servicenow custom app as you can gather these pillars are generally organized in the recommended order of operations but developers have the flexibility to begin wherever they prefer the first pillar is data to create a table someone need only have a spreadsheet and servicenow can basically do the rest once established from a single screen the developer can not only further customize the database but simultaneously design the initial interface that users will use and even the automation surrounding this data but that's coming up here in a bit no spoilers the second pillar is experience aka the user interfaces that we will provide to interact with our databases from app engine studio we offer a multitude of options for the various personas that use an app we have workspaces where fulfillers have everything that they need to quickly and effectively complete work orders there are applets which are individual pieces of functionality hosted on the variety of servicenow's mobile app library there are service portal pages designed to be the single source of action for requesters where they can utilize what we are about to build here catalog items even to design something as complex as an experience developers will rely on these wizard style designers constantly guiding them through the why behind every step they need to take to build something to completion the third pillar is automation service now ps the resistance under the automation header we see a few flows each representing a process that has been automated on our platform clicking one opens up the flow designer your one-stop shop for all things automation both inside and outside of servicenow any flow consists of two parts a trigger and a sequence of actions the trigger is essentially what turns the flow on the trigger can be an interaction with a servicenow record like we see here it can be a specific or relative amount of time or a variety of other things what's really amazing is without even having interacted with this form before we can simply read and see what this trigger is this is not some label that was manually typed out as it would be on a variety of other platforms this is a natural language generated title to ensure that any newcomer can get a really good gist of what's going on regardless of their servicenow expertise we can also use this property to translate the sequence of actions of what they are automating actions are simply functions that servicenow is doing on behalf of a person things like updating records managing attachments query for data sending notifications you know all the parts to your job that probably aren't the highlight of your day actions are stored in collections called spokes and many spokes are already included with software that you've already purchased on servicenow if you're an itsm customer there's an itsm spoke if you're hr customer there's hr spoke etc actions can proceed one directly after another but much more commonly is the need to create multiple branches of your process using flow logic any record that you have some sort of interaction with throughout the entirety of your flow is always going to be accessible through the data pane on the right hand side of the screen and you don't even have to go anywhere different to test your flows or even manage the executions of when it goes live flow designer really is the pinnacle of consolidating process management and finally the fourth pillar is security definitely not the flashiest part of any demo but definitely one of the most vital pieces of any good application with servicenow being a role-based system here we not only have the capacity to create brand new roles but intimately control how the ones that do exist interact with everything that we've built thus far now some of you in the audience might be thinking to yourself this is great and all but i've spent my entire career coding is there any way to go deeper than this be not afraid if you recall from the beginning aes is just one of two development environments that servicenow offers for traditional developers aes might be the fastest way to learn the building blocks of what makes a great servicenow application but alternatively your path might bring you to utilizing the more traditional platform studio that servicenow also offers if you would like more information on this more pro coder focused studio studio i will provide a link in the description down below using app engine studio developers can get onboarded on the service now platform lexicon and application file types at lightning speed to start them off on their best foot forward to becoming a phenomenal servicenow developer if any of this has piqued your interest and you're seeking to learn more might i recommend our developer website there you not only have labs guides and docs right at your fingertips you can get your very own free instance of service now in seconds if you liked what you saw here today go ahead and leave us a like and if you're ready to dig deeper also click subscribe thank you so much for joining me here today best of luck on your brand new developer journey stay hungry stay humble and i'll see y'all next time cheers [Music] you