Office Suite

Configuration Parameters

The configuration parameters enable you to change the properties of the Office Suite to comply with your needs. The list of the configuration parameters can be accessed with the menu System > Office Suite > Configuration.

The Installation Guide on the Installation CD contains information about the parameters which need to be set for the installation of Office Suite.

Variables

The following list provides details about the individual columns of the configuration table.

Variable

Description of the Office Suite Variable

No.

Sequential number (when the variable is composed of several different elements which are determined separately.)

Value Type

The data type of the value to which the variable should be assigned.

Value

Depending on the type of value, this is either a database field, a default, an environment variable, or a string.

Start

If only a part of a value range should be entered, this can be used to specify the first column of the value.

End

If only a part of a value range should be entered, this can be used to specify the last column of the value.

Cond. Type

The value assignment can be linked to a condition. The type of condition is defined here.

TAB = Table field
CLI = Client environment variable
MAS = Mask name
CRE = Value of current file type (e.g. .doc)
DEF = Value is taken as the default
SYS = Client or server name
OBJ = Name of an entity or type entity

Field

Depending on the chosen Cond. Type, this column contains the respective detailed information:

TAB The name of the table field
CLI The name of the client environment variable
MAS The mask name
CRE The name of the table field in the file type table
DEF No information is needed. Any text entered here is interpreted as comment.
SYS The name of the host variable (DTV_HAST or CLI_HAST)
OBJ No information is needed. Any text entered here is interpreted as comment.

Act. value

This is the value of the condition, e.g. the content of a table field or the current value of a variable.

User

This specifies the user the definition of the Office Suite variables should apply to. If the entry should apply to all users, enter GLOBAL.

Comments

Comments field

 

If the value DEF is entered in the Cond. Type field, the variables are saved as DataView defaults and only become active when the client is restarted.

The following list contains the most important configuration parameters:

Configuration Parameter Description

GDM_ARC_FNC

Function for creating a job for generating a PDF file.

GDM_ARC_NOD

Node where the PDF file is generated (PDF Batch Client).

GDM_CHK_TYP

YES/NO Checks if the file type can be stored in the current doc type.

GDM_CLI_DIR

Field for saving the original file location .

GDM_CLR_FIL

Dummy file for supporting empty directories in structures.

GDM_CRE_SYS_FLD

Field where the application is entered.

GDM_DIR_PTH

Field where the directory path of the file(s) is entered.

GDM_DOC_LIST

Temp file for structure copy.

GDM_EmbedToolBar The button 'Insert from Agile PLM' is active (=1) or inactive (=0) in the MS Office application.

GDM_FIL_FLD

Field name for original name of file .

GDM_FIL_FLD_1

Contents of first field of the file relation in the navigator .

GDM_FIL_FLD_2

Contents of second field of the file relation in the navigator .

GDM_FIL_TIM

No longer used in Agile e6 but required for compatibility reasons!

GDM_FIL_TYP

Name of file type.

GDM_LAY

Field containing the template name.

GDM_LAY_FLD

Logical field for defining if the document is a template .

GDM_LinkToolBar The button 'Link from Agile PLM' is active (=1) or inactive (=0) in the MS Office application.

GDM_MSG_NO

Message answered with NO automatically.

GDM_MSG_NO_BAT

Message answered with NO automatically when sending a file or checking out of lists.

GDM_MSG_YES

Message answered with YES automatically.

GDM_MSG_YES_BAT

Message answered with YES automatically when sending a file or checking out of lists.

GDM_OpenToolBar The button 'Open from Agile PLM' is active (=1) or inactive (=0) in the MS Office application.

GDM_PRI_FIL

Defines printable document types for container documents .

GDM_SAV

Vault for Office documents.

GDM_SaveToolBar The button 'Save to Agile PLM' is active (=1) or inactive (=0) in the MS Office application.

GDM_SNR

Internal file name used for saving the file in Agile e6.

GDM_SRC

Defines the default check-out directory.
GDM_SRC and GDM_SRC_CHK_OUT should always be modified together to guarantee the standard check-out strategy.

GDM_SRC_CHK_OUT Defines the default check-out directory.
GDM_SRC and GDM_SRC_CHK_OUT should always be modified together to guarantee the standard check-out strategy.

GDM_SRV_FIL

Path and name of the Server Protocol files.

GDM_SYS_GRP

Group with the privilege to define templates.

GDM_SYS_GRP_1

Group with the privilege to define new document types.

GDM_SYSTEM_FILE

No application is started for this files when checking out for processing.

GDM_VIE_FIL

Defines allowed formats for viewing container documents.
The value of this parameter has been changed from e.g. PDF, TXT, TIF to %. '%' includes all possible file formats.

GDM_WRK_TIT_1

Bitmap to be displayed in the browser.

GDM_WRK_TIT_2

Title displayed in the browser.

Document Properties

All property elements that should be used in the Office Suite have to be entered in the list of document properties. The entries do not depend on the original program or the template.

Column Name Description
Name List of possible properties that can be selected in the Property Exchange mask for a certain file type. These properties will then be exchanged between the MS Office applications and Agile e6.
Description Short description of the property.
Type

Two values are possible:

  • SYSTEM: are supplied by MS-Office and cannot be deleted.
  • CUSTOM: are defined by the user.

A template can only be used when a property has been defined in this list.