Start Template File Import

Explanation

This activity starts the import of Company Template related files.

It is expected that the files to import are valid Company Template files created using either the Export Company Template to File Assistant or the Company Template Merge Assistant. Company Template translation files must have been created using the Export Company Template to File Assistant.

The following is performed by the import activity:

• The template ID found in the files is checked for existence.
  If the template already exists, then the user will be prompted to verify that it is OK to overwrite the existing version. 
   
• Next, it is verified whether the current user is privileged to perform the import.

• Normally, only the user who created the template can import his or her templates. 
• A company template super user is allowed to import any template.
• A system template can only be imported by a company template super user or by the application owner.

• Note that import always means overwriting an existing template with the same ID.
  Since information in a company template is defined per component, it is possible to modify the template for a single component, and thus keep the template data for all other components as before. 
   
• For each component, the following detail information will be defined:

• Version of the component
• Logical Units in the component being a part of the template
• Template detail data for each Logical Unit

• The component name and component version specified in the template file is verified during import by checking registered components and versions. It is not possible to import data associated with a component that is not registered in the Component Registration window. The component version in the file must be the same as the registered component version. If not, errors will be generated in Company Template Log.
  
  However, when an old version of a component is imported, which is not a part of the template in the database, then all information for the component will be imported. This situation may occur if a template is removed in the Company Templates window and an old template file is available. This means that you are able to preserve the template data valid for an older component version and correct it manually to fit the current version of the component.
  Note that in this case the template will be marked as not valid since it contains component versions that do not match registered component versions.  
   
• Each logical unit of a component is verified by checking the registered logical units for the component. It is not possible to import data of a logical unit that is not registered. Registration here refers to the Component Registration window. 
   
• During import of a template, the PROG entries will be defined in the company template translation framework, for all the basic data entries that support company translations. The PROG entries actually represent the translatable terms or attributes that exist in a company template. 
   
• If the company template translation files are imported, then these files will add translations of the basic data entries to the company template translation framework. 

Prerequisites

A Company Template file and/or Company Template translation files must have been selected.

System Effects

If the import is successful, the company template in the file will be available in the system along with the associated translations.

Window

Import Company Template File Assistant

Related Window Descriptions

Import Company Template File Assistant

Procedure

1. Start the import.
2. Confirm message displayed at the end of the activity. The following type of messages are possible:

• A message stating that the import was successful.
• A message stating that it was impossible to perform the import since the file was impossible to interpret.
• A message stating that the import was completed with errors.

3. If errors occurred and a log identity was supplied, continue with the Check Template Log activity.