|
|
|
|
|
The Stages and Actions you can
add are identical to version 7,
with one notable omission. This
is the Sub-Process (formerly
‘Sub-Map’) Stage.
There is a very good reason for
this.
Instead of adding a Sub-
Process Stage and selecting the
Sub-Process, you now can add
all Sub-Process in the Project
from the Process Toolbox.
|
|
|
Sub-Processes are added from
the Home menu.
|
|
|
And appear in the selected or
default Project.
|
|
|
The map looks the same as we
are used to, with no ‘start’
action.
|
|
|
Going back to the Process, or
another Sub-Process (not the
same one, or you get an
infinite loop), you can see the
Sub-Process in the Toolbox.
|
|
|
You drag and drop this to the
Process like any other Stage.
|
|
|
You can see that the properties
are the same as we are used
to,
|
|
|
And you can, in fact, select a
different Sub-Process if one is
available.
|
|
|
|
|
If we set up a Process and Sub-
Process as shown,
(note that we are developing a
naming standard for objects in
Metastorm Solutions, since
there is no way to have two
objects of the same name as
far as we can tell)
|
|
|
Then add the Variables as
shown. This is almost the same
as previous versions, but with
the additional ability to add
descriptions for the variables,
which is welcome.
Notice that you cannot have
the same variables in the
containing Process as the Sub-
Process.
|
|
|
When data is entered …
|
|
|
… the Containing Process table
stores its data, and the Sub-
Process table stores its data.
Although the Sub-Process
variables are added to the
containing Process, like
previous versions, but they are
no longer populated.
|
|
This may make reporting from processes employing Sub-Process a
little different. It does mean, however, that you can have
common data properly stored for multiple Processes, such as for
an approval or audit sub-process, because all Processes
employing this Sub-Process will store their data in the same table.
|
|
|
|
|
|
1. Designer User Interface
