Custom templates in App Engine Studio (AES) support most features and metadata, including, but not limited to tables, forms, roles, ACLs, record producers, simple workspaces, flows, and actions.

Custom templates can be created in two ways, either from scratch or using an existing scoped application as a starting point.

When you create a custom template, the pre-scan checks to make sure that everything in the application is supported. There are three possible outcomes.

  • All items are supported: The custom template is created. All the objects are available in the custom template and in apps created from the custom template.
  • Some items aren't supported: You can continue to create the template but a few items are not available in the custom template. There’s no impact on the custom template or the apps created from the template.
  • Some items are denied: You encounter an error message and cannot continue further until the errors are fixed. The author must change the app, if it was created from an existing app or the template, if it was created from scratch.
Note: Creating an AES template using an application that contains a workspace is not supported.

For more information on the template creation process, see Build a custom template.

Supported metadata

Skipped features and metadata

The template creation process only skips items that should not impact the template or apps created from the template.