Start Template Export

Explanation

This is the last activity in the Export Template to File process and the following is performed:

• The existence of the the source template is verified.
• For all active Logical Units in all active components that support Company Templates, an export view will be used to extract data associated with a particular Logical Unit from the selected source template.
• The processing is done per component and the processing order is determined from the relationship between the component and parent component as defined in the Component Registrations window.
• Within a component, the processing order of Logical Units is determined from the Execution Order, as defined per component in the Component Registration window.
• Only components selected in the Export Company Template to File Assistant dialog will be processed. 
• Depending on the export mode, one basic data template file per component or a single template file is created. The export mode also determines whether or not translation files will be created.
  Basic data Company Template files will be named according to the following formats:

• CompanyTemplate_<Template_Id>.ins 
  e.g., CompanyTemplate_STD.ins
  This will be used if you have selected to create a single Company Template file.
  
• <COMPONENT>_CompanyTemplate_<Template_Id>.ins
  e.g. ACCRUL_CompanyTemplate_STD.ins
  This will be used if you have selected to create one Company Template file per component.
  
  <COMPONENT> will be the registered component name in uppercase.

If translations should be exported, the created files will be named according to the following formats:

• CompanyTemplate_<Template_Id>_<Lng>.ins 
  e.g. CompanyTemplate_STD_en.ins
  This will be used if you have selected to create a single Company Template file. This file will contain all translations to one specific language related to basic data for all selected components.

<COMPONENT>_CompanyTemplate_<Template_Id>_<Lng>.ins
e.g. ACCRUL_CompanyTemplate_STD_en.ins
This will be used if have selected to create one Company Template file per component. In this case, the translation file only contains translations to one specific language related to basic data for one specific component.

Company Template files can be installed via a delivery in Build Place. For details, refer to Build Place Deliveries/Ordering Deliveries in the Technical Documentation for IFS Cloud. Additionally, users can import company templates through the Import Company Template page, provided the file is in JSON format. Both INS and JSON file types can be exported using the Export Company Template Assistant.

Prerequisites

A source template must have been selected, the export mode must have been defined, components and languages to export, as well as the output directory must have been defined.

System Effects

N/A

Pages

Export Company Template

Activity Diagrams

Export Template to File