Form functions – templates

The following functions in the function bar refer to the template, up to and including "Editing":

Check in

Checks a file from the local user system in to the database. This way, you can store templates in the database or update documents in the database with a new version.

Attention

Attention: The file of the current record in the database will be overwritten.

Check out

Checks out files from the database to the local user system. This stores a copy of the file from the database in the local file system for editing it. The status of the document record is then “in treatment”. Checking it in again will set the document record’s status back to “in development”.

Save as

Saves the file locally to a destination of your choice without changing its status.

View

Opens the document (usually the template) with the corresponding application. If it is a writable document, it is displayed write protected.

Edit

Temporarily checks out a template and opens it with the linked application in write mode. The status of the document changes to in the processing. With BIRT, the template and the pattern data are copied to the local BIRT workspace, which is predefined by the PSA_BIRT_CLI_TMP environment variable. You can then manually open the template in BIRT designer. With Microsoft Office, the system will remind you to check the document back in. With BIRT, however, you need to save the template in the designer and then manually check it in to the CRM.

Attention

Attention: Using the Edit document function, you are working directly on the data file from the database. All changes are saved immediately in the database, and the older template is replaced when you close the template and check it in. If you are uncertain, you should check out the template first and edit the copy. This has the advantage that you always have the original template in the database and will replace it only by means of the Check in form function.

XSL

These functions refer to an XSL style sheet at the loader object, with which the XML markup is processed for the respective reporting tool. Experienced XSL developers can copy existing style sheets and adapt them according to their own specifications. One can modify the XML markup by omitting levels or adding calculative fields, for example.

View

Opens the XSL document as a template in the web browser if an XSL document is assigned to the loader object in the database.

Check out

Saves the XSL document locally as a template to analyze or edit it.

Check in

Checks an XSL document from the local user system in to the database. This saves XSL documents to the database or updates files in the database with a new version.

Attention

Attention: This replaces the file of the current record in the database, which may cause hundreds of templates using this XSL to become unusable with one click. It is strongly recommended to create a backup before.

Delete

Deletes the XSL document of the template irreversibly from the database.

Add an element

Elements correspond to files that are stored as BLOBs (Binary Large Object) in the database. You can collect BLOBs using drag and drop in the Template elements tab by dragging files from the local file system to the tab.

The Add elements function opens a file selection dialog for selecting a file. A BLOB is automati­cally created, saved in the database, and added to the Template elements tab. These elements are later available for selection, just like other data in the CRM template assistant.

Show meta data

Here you can open a dummy XML document in the browser. This includes the complete data structure from the loader object. It is assumed that each subclass has exactly one record. In place of the real data, the external name of the field filters are displayed, followed by the data field titles in brackets. When you are processing a Windward template, you can find the metadata again in the data structure window of the JustRelate CRM Template assistant.

Note: With Word’s mail merge, this function is obsolete because Word as a data source requires a CSV file. Exter­nal names in loader objects are used to provide the template developers with an easy-to-understand alter­native to the somewhat cryptic CRM data field names.

Convert to DOCX

See also: Using Windward as the report engine, Template updating