Template Status

The APCS application when provisioned will be deployed as a Template application with the Template status of Activated. The customer has the option to deactivate the template status meaning it is a fully custom configuration. If it is a custom configuration, the customer should upload and completely maintain the configuration. Regular upgrades or patches will not patch the application and only upgrade the server version.

The following task can be used to activate/deactivate the template status of the application. It is advisable for the customer to decide on the template status before the application is built for the first time. Later, it may be easier to convert from the template to the non-template version without any limitations. But it will not be easy to move from a non-template version to template, if the configuration does not follow the extensibility rules for the template version of the APCS Configuration. See the Oracle Retail Assortment Planning Cloud Service Implementation Guide for extensibility guidelines for the APCS template version; only if the non-template application follows those guidelines can it be converted to template.

The Template Status changing task is available as a Bootstrap task together with Build Application. In the Change template status drop down, select the Activate or Deactivate option to toggle the template status option and submit the task to change the template status. Activate means it is a template. Deactivate means it is a custom (non-template).

The customer can also use the same task and choose List template status to view the current template status of the deployed application.

Figure 2-10 Template Status