|
Metastorm BPM version 9 has significant new restrictions on
naming of elements. This is based on the architecture employed,
since the many elements will become properties or functions of
the same C# class. There are basic limitations to all names, as
well, that are linked to C# syntax.
On top of this, there is the new ability to provide ‘captions’ to
many components and elements. These are often also changeable
to support different languages supported by the user’s browser.
Some we find are never used in the system at all, however.
There has also been a significant change in the way variables are
referenced. Metastorm BPM is now strongly types, and the
addition of Intellisense to all editing scenarios gives us the
freedom to dispense with the awkward prefixes that abound in
examples from earlier versions. We will certainly be very glad to
see the back of these, although we are sure they will persist
regardless in some quarters.
Because of these changes, we have developed a new set of
naming conventions for Metastorm BPM. These conventions are
designed to minimise the potential conflicts, and give us much
greater ability to distinguish between items when no other
indication is available (as it now is with variables).
These conventions are neither exhaustive or fixed in stone, they
are merely what we have come across that needs a convention, or
indeed, that needs one being dropped!
|
1. Designer User Interface
