|
|
|
|
Metastorm are aiming at the larger corporate market. Many large
corporations, even if only based in the US, will benefit from the
new multi-language features.
|
|
|
|
Forms can now be edited in as many languages as you like. The
functionality remains the same, as well as the data, but the
captions labels form names, and even field position, may be
customised for each language.
|
|
|
|
|
|
All of the process names, stages and Action names are likewise
editable.
|
|
|
|
|
|
These names are visible in different languages in the client, even
for the same Folders.
|
|
|
|
Most Metastorm BPM systems will have some kind of reporting
needs. Now you can add your own reports into Metastorm BPM
directly.
|
|
|
|
|
|
Since these reports may well use the same Business Objects that
you employ in your processes, much of the development work
can potentially be reused.
|
|
|
|
Metastorm BPM development has up until now mostly been a solo
exercise. There are ways to share development responsibilities,
but they are limited and awkward.
|
|
|
|
Now the various components of a Metastorm BPM solution are in
separate files. These can be easily shared using a source control
system such as Visual Source Safe.
|
|
|
|
Files that are not ‘checked out’ for editing are available and
included in the Project, but not editable. This is also plainly
demonstrated by the shading of the properties and toolbox.
|
|
|
|
|
|
1. The Benefits of Metastorm BPM ...
