00196806-02_IM_EDM_1_10_en.pdf - 第51页

EDM V1.10 / Installation Manual 07/2011 Edition Figure 5-1: Current configurati on options for client workflows 5.3.3 Default configuration See section 6.2 clientWorkflow.xml 51

100%1 / 66
EDM V1.10 / Installation Manual 07/2011 Edition
Additional configuration
Some of the modules require that you specify additional settings. The affected modules are labeled
accordingly in Figure 5-1. The custom section of the application configuration was used to make
room for the additional configuration attributes.
The module VDM for CS adds the VDM Blob handling option to each application template that
affects component shapes. When this module is activated, the Vision data is also transferred for
each component shape pulled.
Module: VDM for CS
Key Form Contents
Configure VDM as described.
Table 5-10: Additional settings for "VDM for CS"
Module: Fixed Template
Key Form Contents
templateName String Name of the application
template to be used
Table 5-11: Additional settings for "fixed templates"
Example forTable 5-11:
<customConfig>
<add key="templateName" value="All Component Shapes"/>
</customConfig>
Module: Fixed Objects
Key Form Contents
objectNames A semicolon-separated (";"), full SIPLACE
Pro path. The following generalized
constructs are allowed for the object names:
Type:* - All objects of this type
Type:Path\* - All objects of this type in this
path (not in subfolders of this
path)
List containing the names
of the objects to be
transferred.
Table 5-12: Additional settings for "fixed objects"
Example forTable 5-12:
<customConfig>
<add key="objectNames"
value="Import\100.gf;System\12.gf;System\100*"/>
</customConfig>
50
EDM V1.10 / Installation Manual 07/2011 Edition
Figure 5-1: Current configuration options for client workflows
5.3.3 Default configuration
See section 6.2 clientWorkflow.xml
51
EDM V1.10 / Installation Manual 07/2011 Edition
5.4 EDM configuration
5.4.1 Application templates
The application templates depict the static part of the customer process that is related to the data.
They primarily define the object types to be transferred and whether or not they will be overwritten.
5.4.1.1 General settings
Figure 5-2: General settings for application templates
The general settings include:
● Type of data transfer. Currently, you can only select Pull Mode or Forced Pull Mode.
● Starting Point specifies the object type for which this template can be valid. A template can
only be valid for one object type at a time. However, it is possible to define more than one
template for an object type.
● Objects found in the Default folder and all its subfolders can be subsequently specified by the
line engineer for pushing from the master.
● An optional comment.
Pull mode
No additional settings can be specified for this type of data transfer between the Master Server and
Line Servers.
52