# Office Suite

## Property Exchange

In order to transfer document properties, all properties in Office Suite, which should be transferred to a template, must be entered in the property exchange list. The property elements are defined in the Document Properties tab of the Office Suite Configuration mask..

The property to be used within a specific template is defined in the Property Exchange mask (System > Office Suit > Property Exchange).

Used | Specifies if the template element is active or inactive.
Pos. | This value is important for the RELATION relationship type. It can be used to control which position in the assignment should be taken. If the value 0 is specified, a query is performed. Enter 1 here for the DOCUMENT relationship type.
Put | Specifies that this value should be passed from Agile e6 to the MS Office application.
Get | Specifies that this value should be passed from the external application to Agile e6.
Name | Name of the property template as defined in the Office Suite Configuration mask. If no property templates exists for the Office application or if you wish to support documents created with an undefined template type, a generic template can be created for each file type. This must be given the name <SUFFIX>-FILE (e.g. PPT-FILE).
Field | Name of the field in Agile e6 to which the property value should be assigned.
Relation | Controls the type of assignment. DOCUMENT: The data is retrieved from the current document mask or is written into the corresponding field. RELATION: The data is retrieved from a table with a relationship to the document. This property is only valid in connection with the GET operation.
Function | The data is determined by a LogiView which is specified here. Get avalue for a CUSTOM PROPERTY that is transferred to your office application. Input parameter of this procedure is the CID of the current document (GDM_DOC_CID). The procedure result has to be assigned to the default GDM_ATT_CURRENT. If a function is entered in this field, the Relationship field has no meaning and is ignored.
Type | Specifies if this is a system property or property set by the user (SYSTEM or CUSTOM)
Description | Descriptive text

### Metadata Transfer to Excel

The metadata defined in Agile e6 (Office Suite) are entered as document properties in Excel. The corresponding cell (property) is specified in order to enter these properties into an Excel document. Office Suite then ensures that the cell and the property are linked.

If an Excel file does not contain the name of the MS Excel template as other Microsoft Office applications, it cannot be identified by the Office Suite. This information is usually used in the Office Suite to select an existing template definition whose included allocation rules are used for exchanging property information.

To support this function, it is possible to define a custom property with the name GDM-TEMPLATE with the definition GET (read at check-in). The name of the used template can now be added to the property within the Excel file.

If the allocation is made manually, it is suggested to enter the necessary settings already in the template.

Header and Footer

6 attributes can be defined in the Office Suite configuration which can be used as headers and footers in Excel.

- XLS_FOOTER_RIGHT
- XLS_FOOTER_CENTER
- XLS_FOOTER_LEFT
- XLS_HEADER_RIGHT
- XLS_HEADER_CENTER
- XLS_HEADER_LEFT

### Identification of Metadata with Functions

If an information cannot be identified directly from the table field, it is also possible to define the current value of the property with a function. No entries are made in the columns FIELD and RELATION. In the column FUNCTION a LogiView procedure is entered which calculates the value.

The shipped version contains the LogiView compound GdmData which supplies some exemplary procedures with information on the usage of the field "Function".

| The procedure and the compound are only examples and should not be used, as the LogiView code of the Office Suite is usually replaced at update. You need your own logic model for your procedures.