|
Install App Engine Studio in your development instances.
|
You can install the App Engine Studio application \(com.snc.app-engine-studio\) if you have the admin role.
The application installs related ServiceNow® Store applications and plugins if they are not already installed.
For detailed instructions, see [Installing App Engine Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/install-aes.md).
|
|
Set up instance credentials.
|
For each instance that you're using, create a Connections and Credentials alias. Verify that the alias type is **Credential**, not **Connection and Credential**.
For detailed instructions, see [Set up instance credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/connection-alias.md).
|
|
Activate Playbooks.
|
You can edit processes in App Engine Studio, but you must activate Playbooks for App Engine Studio and enable the **Process Automation Designer for App Engine \[com.glide.pad.license\]** plugin to get started. For more information, see [Activate Playbooks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/activate-process-automation-designer.md).
|
|
Set up Integration Hub spokes.
|
Activate spokes to enhance your Workflow Studio and App Engine Studio experience with integration-specific content.
The following spokes are available for use with App Engine Studio.
- [Gmail spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/setup-gmail.md)
- [Google Sheets spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/setup-gsheets.md)
- [Jira Spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/jira-spoke-v3-0-2.md)
- [Microsoft 365 Excel spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/setup-office-365-excel.md)
- [Microsoft Teams spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/microsoft-teams-spoke.md)
- [Slack spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/set-up-slack.md)
- [Twilio spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/setup-twilio.md)
- [X Spoke \(formerly Twitter Spoke\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/twitter-spoke-ol.md)
- [Zoom spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/setup-zoom.md)
|
|
Review access settings for Workflow Studio in your development instance.
|
Enable your developers to use the editing capabilities that best suit them. For detailed instructions, see [Review Flow Designer access settings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/user-access-flow-designer.md).
|
|
Review access settings for Catalog Builder.
|
Enable your developers to add items to the appropriate catalogs and categories.For detailed instructions, see [Review Catalog Builder access settings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/catalog-builder.md).
|
|
Set up an instance scan cadence.
|
Schedule regular scans of your instance so that you can identify possible issues that arise from application development in App Engine Studio.For detailed instructions, see [Set up an instance scan cadence in Health Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/hs-landing-page.md).
|
|
In your production instance, add users to the App Engine Studio admin group.
|
Add members to the group so they can review app- and deployment-related requests. Also, define a contact email address for the group.
For detailed instructions, see [Add users to the App Engine Admin group](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/add-users-to-admin-grp.md).
|
|
In your development instance, add developers to the App Engine Studio users group.
|
Enable developers in your organization to build applications in App Engine Studio.
For detailed instructions, see [Grant user access to AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/grant-aes-access.md).
|
|
In your development instance, add users to the App Engine Studio User Limited group.
|
Enable developers in your organization to collaborate on applications that someone else created in App Engine Studio.
For detailed instructions, see [Grant user access to AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/grant-aes-access.md).
|
|
Set up collaboration descriptors.
|
Set up custom collaboration descriptors in the global scope for use in App Engine Studio.
For detailed instructions, see [Set up custom collaboration descriptors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/set-up-custom-collaboration-descriptors.md).
|
|
In your non-production instance, specify an app template admin.
|
Grant the app\_template\_admin role to users who will manage template activation, deactivation, and sharing in App Engine Studio.
For detailed instructions, see [Manage template access](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/manage-template-access.md).
|