hello and welcome to service now's low code capability deep dive in this nine-part series we're going to take a look at the various aspects of the service now platform that Empower creators of all skill levels with the ability to rapidly build highquality scalable and easy to govern apps devops and the activities and rituals surrounding developing and deploying software is the topic of our next section I will show how the service now platform supports developer collaboration and creativity while providing governance and structure when working on an application developers can invite others to collaborate with them low code creators can use this form to request help from proc coders or pull in Resources with specific expertise such as Integrations security and user experience collaboration around code is also encouraged through Source control service now supports hosted and self-hosted git repositories so that developers work can be committed merged and versioned here I have connected my expense application to a hosted GitHub repository I can create a new branch make code changes and commit them my organization's development process is to create a pool request when it's time to merge back and have it peer reviewed once the pull request has been merged I can can refresh the development environment to pick up the latest changes customers have choice of approach when deploying applications service now provides an outof the-box deployment pipeline through app engine management center or AMC for short deployments through AMC are the recommended pathway for low code applications as AMC integrates seamlessly with ATF change management cmdb and our workflow and approvals engine to deploy an application with AMC creators simply submit the application and a request will be created for review Once approved the application makes its way through each instance in the pipeline where automated and manual checks are performed I'll go into AMC and pipelines in more detail in the platform governance and operation section of this video we recognize that some customers have existing deployment processes or stringent regulatory or industry policies that may require a more procode approach to serve these customers service now provides cicd and Source control apis and Marketplace plugins for all major deployment orchestration platforms including junkins gitlab Azure devops and GitHub actions here is an example of a branch policy in Aur devops which requires that all po requests targeted for the main branch are validated before they can be merged industry standard yaml notation is used along with the service now cicd Ado plugins to run my application's ATF tests validating that there are no errors before I merge this pull request has been validated successfully and is ready to merge new application versions can also be deployed through third party Platforms in this release pipeline and Azure devops Marketplace app for sonar cloud is being used to analyze the code in my service Now application ungated continuous deployment can be set up in a similar Way by triggering a release from any number of life cycle events such as new versions tags or mergers if an application requires roll back to a previous working version this can be requested through the rollback API or manually in the application record there are a number of options for building mobile apps on the service now platform by leveraging service now mobile publishing the existing service now agent and now mobile applications can be branded and republished to the store under their own company's developer account developers can also build their own applications and integrate into the service now platform using the mobile SDK thanks for watching and join us for part seven of our series as we explore platform governance and operations