|
The naming of Processes has been the bane of many a Metastorm
BPM developer. Firstly, once it is set, it is set for good. This is
one reason we work very hard to get it right first time.
Unfortunately the business owners rarely understand the
significance of getting it wrong. They then ask, months later, “can
we change the title of this process” (most often not in those
words). Groans ensue.
Well, it’s all over. All of it! We can name the process anything
the users want, even with symbols in it! This is because we now
have ‘Captions’ for our Processes.
The upshot is that we can have what we have been requesting for
a long time, namely a table name that is different from the
Process Name. The facility has always been there, but never
activated in the Designer. Look in the eMap table and you can
see the eTableName field. This can be anything you like (we’ve
hacked and it works).
|
|
|
|
What we now do is treat the Process name itself as a table
name. Typically we group all tables for a particular system by
prefixing the table with the initials of the system. When you have
many systems on the same database, which we will always have,
it makes it a great deal easier to see and select related tables.
In Metastorm BPM version 9 we have decided to do exactly the
same with our Process names.
|
|
|
|
This has the added advantage that the Process Data Business
Objects are much easier to identify in what inevitably becomes a
rather large list.
|
|
|
|
|
|
1. Designer User Interface
