Metastorm BPM solutions are stored in XML files.
Each library and project are stored in their own subdirectory. This
gives us two very important advantages for source control. Firstly
we are able to track changes in most source control systems, such
as visual SourceSafe. Changes line by line can be highlighted when
examining updated files. The second and more practical advantage is
the ability to check-in and checkout individual files as
required.
The Metastorm BPM designer will make any
component read-only if the file is read-only. This clearly
demonstrates to users that the particular component cannot be
edited, but it allows them access to all the properties for
examination. This is very similar to a typical coding project
approach, for example using visual studio. This allows for sharing
of development duties across a large team. As such, Metastorm BPM
is fully usable in a typical development
environment.
With the combined ability to separate many
components into libraries for reuse, this gives us full control
over the development process. It is relatively easy to separate
different tasks according to different skill sets, for example
allowing process designers to do what they do best and design
processes, developers to develop code modules they can employ, and
database designers to create and maintain
schemas.
What is Metastorm BPM?
