Perform AES configuration tasks

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 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

    Performing configuration tasks in App Engine Studio (AES) is essential for setting up environments, tools, and user access effectively. These tasks ensure that your development instance is properly configured to support application development and integration features.

    Show full answer Show less

    Key Features

    • Installation: Install App Engine Studio in your development instances if you have admin role access, which also installs related applications and plugins.
    • Instance Credentials: Create a Connections and Credentials alias for each instance, ensuring the correct alias type is used.
    • Process Automation: Activate Process Automation Designer to enable process editing within App Engine Studio.
    • IntegrationHub Spokes: Activate various spokes (e.g., Gmail, Jira, Microsoft Teams) to enhance functionality in Flow Designer and App Engine Studio.
    • Access Settings: Review and enable access settings for Flow Designer and Catalog Builder to facilitate app development.
    • Health Center Scans: Schedule regular instance scans to identify potential issues in application development.
    • User Management: Add users to the App Engine Studio Admin group and other relevant groups to control app development access.
    • Collaboration Descriptors: Set up custom collaboration descriptors to define development collaborators.
    • Template Management: Assign app template admin roles to manage template access and sharing.

    Key Outcomes

    By completing these configuration tasks, ServiceNow customers will establish a robust environment for building applications within App Engine Studio. This setup enhances collaboration, streamlines user access, and ensures that integrations and automation processes are properly configured, leading to a more efficient development cycle.

    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 Flow Designer 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