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

Installation Manu al SIPLACE Engine ering Data Manag er (EDM) Version 1 .9 Issue 02/2009 50 </ transition > Figure 14 Default transition Specifying "al l" for the initia l state causes this tra nsition to…

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

49 / 65

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

ateListAction,DataExchange" />

<action

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

ction,DataExchange" />

</newState>

</transition>

Figure 12 Example of a simple transition

This transition goes from the clientIdle state to the waitTemplateList state when the pullData event is

triggered. Two actions are performed during the transition, each of which is specified in the class notation

known from the application configuration. The actions are executed in the order they are listed in the file.

<transition name="selectTemplate" currentState="waitTemplateList"

event="templateList"

class="Siemens.SiplacePro.EDM.DataExchange.Actions.AskForTemplateAction,D

ataExchange">

<action

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

ateAction,DataExchange" />

<action

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

ction,DataExchange" />

</newState>

</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 just one "newState" tag as in

the first example in Figure 12, but instead 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:

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>

-->