00195366-01_InstallationManual_EDM_en.pdf - 第49页
Installation Manual SIPLACE EDM Edition 11/2006 <!-- <transition name="selectIdentities" currentState="selectObjects" event="selectIds" class="Siemens.SiplacePro.EDM.DataExchange.…
Installation Manual SIPLACE EDM Edition 11/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. 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>
<!-- Pull workflow variants -->
<!-- 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:
48 of 66
Installation Manual SIPLACE EDM Edition 11/2006
<!--
<transition name="selectIdentities" currentState="selectObjects"
event="selectIds"
class="Siemens.SiplacePro.EDM.DataExchange.Actions.SelectIdentitiesAction,
DataExchange">
…
</transition> -->
<!-- Use fixed selection -->
<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"
49 of 66
Installation Manual SIPLACE EDM Edition 11/2006
An example for Table 9:
<customConfig>
<add key=“templateName“ value=“All Component Shapes“/>
</customConfig>
Module: Fixed Objects
Key Form Contents
List containing the names of the
objects to be transferred.
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)
Table 10 Additional settings for "fixed objects"
An example for Table 10:
<customConfig>
<add key=“objectNames“ value=“Import\100.gf;System\12.gf;System\100*“/>
</customConfig>
50 of 66