--- sourceDocument: Yokohama Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Components installed with AES # Components installed with AES {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Components installed with AES Activating the App Engine Studio (AES) plugin in ServiceNow installs several essential components, including tables and user roles, to support application development, deployment, and management within AES. These components facilitate managing app creation, deployment pipelines, user access, and help resources. Show full answer Show less ## Roles Installed * **App Engine Studio admin \[appengineadmin\]**: Grants administrative control over AES, including user and configuration management. Assigned automatically to members of the App Engine Studio Admins group. * **App Engine Studio app template admin \[apptemplateadmin\]**: Manages template usage, sharing, and activation. Assigned manually by an admin to specific users. * **App Engine Studio user \[snappengstudio.user\]**: Enables users to build applications within AES. Assigned automatically to members of the App Engine Studio Users group. ## Tables Installed Multiple tables are installed to track and manage various AES functionalities: * **App Details**: Records developer operations during app creation. * **Applications in Projects**: Tracks applications created within AES projects. * **Environment**: Defines development, testing, and production environments for app deployment. * **Deployment Request**: Manages requests for reviewing and publishing apps, allowing reviewers to deploy, accept, reject, or provide feedback. * **Pipeline**: Stores deployment pipeline configurations ensuring only one active pipeline at a time. * **Project**: Contains details about AES development sessions and projects. * **Resources Content and Content Topic**: Holds help resources and their categorizations for AES users. * **Taxonomy, Taxonomy Category, Taxonomy Details**: Organizes and details application files, categorizing them by type such as data, logic, or security. ## Data Preservation Data preservers are implemented for pipeline-related tables (Environment, Pipeline, Pipeline Environment Order, Pipeline Types) to prevent overwriting during cloning on non-production instances, ensuring deployment configurations remain intact. Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles. Note: The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an application](https://www.servicenow.com/docs/access?context=find-components&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). ## Roles installed {#installed-with-aes__section_wly_yyh_wdb} {#installed-with-aes__table_u1t_gb1_wdb__entry__3} | Role title \[name\] | Description | Contains roles | |-|-|-| | App Engine Studio admin \[app_engine_admin\] | Administers AES, including users, app configuration, and other management tasks. This role is assigned automatically to users in the App Engine Studio Admins group. | * sn_request_read * sn_request_write * sn_app_eng_studio.user {#installed-with-aes__ul_bft_gqt_stb} | | App Engine Studio app template admin \[app_template_admin\] | Administers the use, sharing, and activation or deactivation of templates. This role is assigned by an admin to individual users. For more information, see [Manage template access](https://servicenow-prod.fluidtopics.net/kBoHTgI_hbaYUD~sgpXeIQ "Control who has access to templates in App Engine Studio (AES) using the app_template_admin role. App template admins activate and deactivate templates and grant other users access to share their templates."). | * app-template-author * app-template-runner * flow-designer * flow-operator {#installed-with-aes__ul_lcw_hrt_stb} | | App Engine Studio user \[sn_app_eng_studio.user\] | Builds applications in App Engine Studio. This role is assigned automatically to users in the App Engine Studio Users group. For more information, see [Grant user access to AES](https://servicenow-prod.fluidtopics.net/j1wZDHy6MpDML3X7DuuZMw "Control who has access to build applications in App Engine Studio (AES) by adding users to AES Users group or the AES User Limited group."). | * catalog_builder_editor * app_template_runner * sn_g_app_creator.app_creator {#installed-with-aes__ul_zrm_hqt_stb} | [ ] {#installed-with-aes__table_u1t_gb1_wdb} ## Tables installed {#installed-with-aes__section_s1x_dzh_wdb} {#installed-with-aes__table_fbz_45z_vdb__entry__2} | Table | Description | |-|-| | App Details \[sn_app_eng_studio_app_details\] | Details about the operations that a developer used to create an application in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Applications in Projects \[sn_app_eng_studio_project_application_m2m\] | Applications that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Environment \[sn_pipeline_environment\] | Instances that you use for the developing, testing, or launching an application. You update this table as you define environments for App Engine Studio. | | Deployment Request \[sn_deploy_pipeline_deployment_request\] | Requests to review and publish an application that a developer created in App Engine Studio. From the deployment request form, a reviewer can deploy the application to different environments, accept or reject an application, and send feedback to a developer. For more information, see [Managing app deployments using Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/mOR0xcpq2vQl0NSZvWtARg "Review the applications developers build using App Engine Studio (AES) so you can deploy with confidence."). | | Pipeline \[sn_pipeline_pipeline\] | Configurations for deploying applications to different environments. There can be only one active pipeline at a time. You update this table as you create a pipeline for the deployment of applications from App Engine Studio. For more information, see [Managing app deployments using Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/mOR0xcpq2vQl0NSZvWtARg "Review the applications developers build using App Engine Studio (AES) so you can deploy with confidence."). | | Project \[sn_app_eng_studio_project\] | Details about App Engine Studio development sessions. A project is created automatically when a developer creates an application in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Resources Content \[sn_app_eng_studio_resources_content\] | Help resources that a developer can access in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | | Resources Content Topic \[sn_app_eng_studio_resources_content_topic\] | Categorizations of help resources in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | | Taxonomy \[sn_app_eng_studio_taxonomy\] | Application files that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Taxonomy Category \[sn_app_eng_studio_taxonomy_category\] | Categorizations for application files in App Engine Studio. By default, application files are categorized as data, experience, logic and automation, or security. This table includes configurations to support the default user experience for App Engine Studio. | | Taxonomy Details \[sn_app_eng_studio_taxonomy_details\] | Details about application files that a developer creates in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | [ ] {#installed-with-aes__table_fbz_45z_vdb} Note: The following data preservers are added for tables related to pipelines: * Environment * Pipeline * Pipeline Environment Order * Pipeline Types {#installed-with-aes__ul_kr2_g14_trb} The data preservers prevent records in these tables from being overwritten during cloning on a non-production instance. For more information, see [Create a clone preserver](https://www.servicenow.com/docs/access?context=create-new-clone-preserver&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).