Application templates can be created and exported from Web AppBuilder, and then shared with a custom template group for use in future applications. This functionality allows continuity between applications made in an organization, and is convenient if the same set of widgets are used in multiple applications.
The first step is to make sure that Portal for ArcGIS/ArcGIS Online is configured with a custom Configurable Apps group. For the templates exported from Web AppBuilder to be available to end-users, they must be shared with the Configurable Apps group specified in the Portal for ArcGIS/ArcGIS Online organization settings. There is a Default group set for this, but it is not possible to share new templates with the Default group. Therefore, a custom group must be specified.
Note: It is useful to name this application in a way that indicates that it is associated with the specific template you are creating, because updating the template requires updating the original application (see below for details). This particularly applies when planning to make multiple custom templates. Only one template can be exported per app, so make sure to keep track of the applications underlying the templates.
This shares the template with the group created and configured in the first section of this article. The template gets stored in the My Content of the user that is logged in when the template is exported, and is listed as a Web Mapping Application.
Note: If Portal for ArcGIS or ArcGIS Online is configured with the default configurable apps group, the following message is received: "Exported successfully! However, it seems that you don't have the permissions to share the template item to the template group specified in your organization. You need to manually add it to the group once it is accessible." If this happens, create and configure a custom template group, then share the template with it.
Only one template can be exported per Web AppBuilder application. If it becomes necessary to update the template, changes must be made to the in the original application, not the exported template. This is why it is useful to have a naming convention that associates each application with the exported template.
Once the template is created and shared, there is the option to use the custom template when creating an application from a template.