Perform AES configuration tasks

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Perform AES configuration tasks

    This guide outlines the essential configuration tasks to set up and manage App Engine Studio (AES) effectively within your ServiceNow environment. Completing these tasks enables your organization to build, automate, and collaborate on applications efficiently while ensuring proper access control and integration capabilities.

    Show full answer Show less

    Key Configuration Tasks

    • Install App Engine Studio: Install AES on development instances using the admin role, which also installs necessary related applications and plugins.
    • Set up Instance Credentials: Create Connections and Credentials aliases of type Credential for each instance used to enable secure integration and communication.
    • Activate Playbooks: Enable Playbooks and the Process Automation Designer plugin to allow process editing and automation within AES.
    • Set up IntegrationHub Spokes: Activate spokes such as Gmail, Google Sheets, Jira, Microsoft 365 Excel, Microsoft Teams, Slack, Twilio, X Spoke, and Zoom to extend integration and workflow capabilities.
    • Review Access Settings: Configure developer access in Flow Designer and Catalog Builder to tailor editing and catalog management permissions according to roles.
    • Set up Instance Scan Cadence: Schedule regular Health Center scans in non-production instances to detect potential issues from AES app development.
    • Manage User Groups in Production and Development Instances:
      • Add users to the App Engine Studio Admin group in production for administrative rights and to receive app-related notifications.
      • Add developers to the AES Users group in development instances to enable app building capabilities.
      • Add users to the AES User Limited group to allow collaboration on apps created by others.
    • Set up Custom Collaboration Descriptors: Define custom collaborator roles globally to enhance teamwork within AES.
    • Manage Template Access: Assign the apptemplateadmin role in non-production instances to control activation, deactivation, and sharing of app templates.

    Key Outcomes

    • Improved Application Development: Streamlined setup and secure access enable developers to efficiently create and collaborate on applications in AES.
    • Enhanced Automation and Integration: Activation of Playbooks and IntegrationHub spokes provides powerful automation and integration tools within workflows.
    • Controlled Access and Governance: Proper grouping and role assignments ensure appropriate user permissions, enhancing security and governance.
    • Proactive Instance Health Monitoring: Regular Health Center scans help identify and mitigate risks arising from app development activities.

    As you work through the App Engine Studio (AES) guided setup, you must perform different configuration tasks.

    Setting up environments, tools, and user access

    The tasks for configuring App Engine Studio are listed below, along with links to detailed instructions for completing them.

    Table 1. App Engine Studio configuration tasks
    Task Description
    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.
    Set up instance credentials.

    For each instance that you're using, create a Connections and Credentials alias. Ensure that the alias type is Credential, not Connection and Credential.

    For detailed instructions, see Set up instance credentials.
    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.
    Set up IntegrationHub 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.
    Review access settings for Flow Designer 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.
    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.
    Set up an instance scan cadence in Health Center. 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.
    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.
    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.
    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.
    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.
    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.
    Learn more about AES configuration Additional ServiceNow resources
    ServiceNow provides several additional resources on configuring and administering App Engine Studio.

    App Engine Studio release notes

    ServiceNow Community site

    App Engine Studio video on adding security