00194585-05_Installation_Manual_EDM_EN.pdf - 第47页

Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006 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. In Version 1.0 of EDM, the rang…

Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006

</transition>

Figure 13 Example of a conditional transition

This transition performs the state transition while taking a controller into account. This special action

is specified using the attribute “class” in class notation. In this case, there is not only one “newState”

tag like in the first example in

Figure 12, there is one tag for each possible output of the controller.

To handle these tags, the “value” attribute is added to the “newState” tag. A controller always

returns a string, so the result can always be stored in the XML file.

To make it easier for the author of the workflow configuration to handle application cases such as

the transition for all states to valid error states like the ones arising in EDM in the form of timeouts

due to the asynchronous communication, the transitions can also be defined as shown in Figure 14:

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

46 of 65

Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006

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. In Version 1.0

of EDM, the range of possibilities is relatively restricted. 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 in the

VDM Blob extension (see chapter 5.3.3

VDM Blob Extensions). 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.SelectIdentitiesActio

n,DataExchange">

…

</transition>

<!-- Use fixed selection

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

event="selectIds"

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

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

47 of 65

Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006

<!--

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

event="selectIds"

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

DataExchange">

…

</transition> -->

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

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

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

48 of 65