00197193-01_IM_SIPLACE_EDM_2_0_EN.pdf - 第70页

EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition Additional configuration Some of the modules require that you specify additi onal settings. The affected modules are labele d accordingly in Figure 6-1 . The custom …

EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition

Example of a transition with parameters (some details omitted)

 <parameter key="ignoreFailedDeletions" value="true" />

...

</transition>

6.4.2.2 Workflow modules

Basics

Figure 6-1 shows all currently available modules that can be used to form a workflow. However,

since future requirements with respect to designing processes are difficult to assess, it was decided

to follow an implementation path that allows flexible extension and configuration.

To make reconfiguring the system on-site as easy as possible, all possible states, even those that

are not used, as well as all events and transitions are contained in the standard configuration.

Those transitions that must be executed (shown in the figure without a colored border) as well as

those for the standard flow (highlighted in gray in the figure) are activated. These transitions can be

replaced by any alternative found in the same level of the flow chart. To do this, the "old" transition

is commented out and the new one is commented in. If several transitions belong to a module, then

all these transitions are to be commented in or out accordingly.

An example is shown below to clarify this. The standard flow for the selected objects in the default

configuration appears as follows:

Example of the standard flow

<transition n selectIdentities" currentState="selectObjects" ame="

event="selectIds"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.SelectIdentities

Action,DataExchange">

…

</transition>

<!-- Use fixed selection

<transition name="useIdentities" currentState="selectObjects"

event="selectIds"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.UseConfiguredI

dentitiesAction,DataExchange">

…

</transition> -->

This must now be converted to a fixed set of objects to be transferred. This means that the

configuration must be adapted as follows:

Example of an adapted configuration

<!--

<transition name="selectIdentities" currentState="selectObjects"

event="selectIds"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.SelectIdentitiesAction,DataExc

hange">

…

</transition> -->

<transition name="useIdentities" currentState="selectObjects" event="selectIds"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.UseConfiguredIdentitiesAction,

DataExchange">

…

</transition>

EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition

Additional configuration

Some of the modules require that you specify additional settings. The affected modules are labeled

accordingly in Figure 6-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 6-17: Additional settings for "VDM for CS"

Module: Fixed Template

Key Form Contents

templateName String Name of the application

template to be used

Table 6-18: Additional settings for "fixed templates"

Example forTable 6-18:

</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 6-19: Additional settings for "fixed objects"

Example forTable 6-19:

</customConfig>

EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition

Figure 6-1: Current configuration options for client workflows