Filter
Top Products
A.2 Results of Staff Resolution
When FlowMark determines that a particular activity should be run, it goes through
a function called staff resolution. This function determines who should have this
activity as "ready" on their work list. Based on what the process designer has
specified on the two "staff" pages in the activity notebook, such as role,
organization, and skill level, FlowMark determines all the people who should see
this, includes that in the dynamic instance information, and adds it to the database
copy of the users' work list. As you can see, the more people an activity is
assigned to and the more items a person has on his work list, the more space is
required for the database.
A.3 Data Containers
We discussed this in Chapter 10, “Data Container Usage” on page 19. As
FlowMark navigates through the process, your application programs add data to
output data containers. This data is then copied into one or more input containers,
as defined in the data mapping of your process model. The number of fields and
the size of the data provided for string fields, as well as the number of input and
output containers, will help determine the necessary space in the database for each
instance. Since the container creation is dynamic, the containers exist and are
filled only when the process flows down the path where they are defined. For
paths not taken in a particular instance (called dead paths), no containers are
created.
A.4 Other Things
The items mentioned above are the major factors in determining the size of an
instance. But there are others. As mentioned earlier, the use of a subprocess
results in another process instance being created when it is encountered in the
process flow. Bundle activities result in real-time updates (additions) to the
database. And the notification server, if used, can add to the database contents.
26 FlowMark V2.3 Design Guidelines