00196806-01_IM_EDM_1.9_EN.pdf - 第51页

Installation Manu al SIPLACE Engine ering Data Manag er (EDM) Version 1 .9 02/2011 Edition 51 / 65 5.3.2.2 Workflow modules 5.3.2.2.1 Basics Figure 15 sho ws all curren tly available m odules that c an be used t o form a…

Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009

</transition>

Figure 14 Default transition

Specifying "all" for the initial state causes this transition to be used for all states. The transition above

therefore defines a general timeout response. A default transition is only executed when no specific

transition is defined for the particular event. This means you can implicitly define more than one transition

for a state/event pair. However, it is not possible to describe more than one default transition for an event.

Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 02/2011 Edition

51 / 65

5.3.2.2 Workflow modules

5.3.2.2.1 Basics

Figure 15 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 which 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 (see Section 5.3.3).

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:

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

event="selectIds"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.Sel ectIdentitiesAction,Dat

aExchange">

…

</transition>

<!-- Use fixed selection

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

event="selectIds"

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

ction,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:

<!--

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

event="selectIds"

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

Exchange">

…

</transition>

-->

Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009

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

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

on,DataExchange">

…

</transition>

5.3.2.2.2 Additional configuration

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

accordingly in Figure 15. 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 8 Additional settings for "VDM for CS"

Module: Fixed Template

Key Form Contents

templateName String Name of the application template to

be used

Table 9 Additional settings for "fixed templates"

An example for Table 9:

</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

List containing the names of the

objects to be transferred.