App Engine Studio Optional Setup Tasks to Consider
This part of the lab is for information purposes only. No activity required.
As part of your App Engine Studio setup, you will want to potentially explore and configure the following:
Connect spokes in Dev Environment​
This step is not required as part of the initial App Engine Studio setup.
A spoke is a scoped application that contains Flow Designer or Integration Hub actions or Subflows.
System Administrators can connect IntegrationHub spokes to App Engine Studio, allowing developers to integrate custom applications with third-party systems. For example – connecting the Slack spoke allows developers to post a message containing Incident details to a specific Slack channel each time a high-priority Incident is created.
Many Integration Hub spokes are available, but not all need to be connected to App Engine Studio. Review some of the common spokes below and install them based on organizational needs.
| Integration Hub Spoke | Installing this spoke provides developers |
|---|---|
| Microsoft Teams | Actions to support cross-functional communications and collaborations in Microsoft Teams. |
| Slack | Actions to automate the management of Slack channels, users, and software subscriptions. |
| Jira | Actions to automate tasks in Jira for managing users, issues, projects, and software development lifecycle. Synchronize data in ServiceNow with Jira to increase collaboration between ServiceNow users and DevOps teams. |
| Gmail | Actions to automate email and label management in Google Gmail. |
| Azure AD | Actions to automate Microsoft Azure Active Directory tasks for user management, authentication, and group membership. |
| Actions to automate posting messages and media content to a corporate Twitter news feed. | |
| MS 365 Excel | Actions to automate worksheet, table, and cell management in Microsoft Excel. |
As your organization’s citizen development program matures and scales, additional spokes can be installed and connected based on application demand and use cases.
For more information on integrations with third-party systems, see Product Documentation: Integration Hub
Review Flow Designer access settings​
This step is not required as part of the initial App Engine Studio setup.
Review and update App Engine Studio developer access settings in the development environment to Flow Designer Resources and update as necessary.
Developers can leverage Flow Designer capabilities while creating logic and automation for custom applications.
Consider restricting developer access to Flow Designer Resources using content filtering for Flow Designer. This allows administrators to manage access to Flow Designer resources and specify which features App Engine Studio users can leverage while building applications.
Flow Designer access from App Engine Studio can be updated later to provide developers with the editing capabilities that best suit their experience and needs.
For more information on Flow Designer resources, see Product Documentation: Content Filtering for Flow Designer
Review Service Catalog access settings​
This step is not required as part of the initial App Engine Studio setup.
Review App Engine Studio developer access in the development environment to the Catalog Builder tool’s catalog item templates and catalogs/categories and update access as necessary.
By default, App Engine Studio developers can leverage catalog templates to quickly create record producers or catalog items. Developers can also publish catalog items to any catalog. If you wish to limit access to templates or restrict publishing access to catalogs or categories, update the access accordingly in Catalog Builder.
Catalog access from App Engine Studio can be updated at a later point to modify developer access to App Engine Studio catalogs, categories, and catalog templates.
For more information on creating or editing catalog items, see Product Documentation: Catalog Builder
Configure Instance Scan​
This step is not required as part of the initial App Engine Studio setup.
Deploy custom applications with confidence by setting up Instance Scan definitions to monitor instance health throughout the deployment process. Instance scans interrogate your instance for configurations and health issues, allowing administrators an opportunity to address best practices and avoid similar configuration issues in the future.
Instance Scan definitions are executed automatically when App Engine Studio applications are promoted to the Testing instance. Instance Scan results will be logged in the Notes section of the Deployment Request record.
The App Engine Studio application does not ship with any out-of-box Instance Scan definitions (however, a few Instance Scan definitions are installed with the Deployment Pipeline plugin to run basic performance checks).
Work with professional ServiceNow developers to configure Instance Scan definitions and enforce best practices in your environments.
Enable and configure Instance Scan properties in your production instance if you plan to clone!
For more information on managing instance health scans, see Product Documentation: Instance Scan