Using Multi Model Audit Trail Setups
Stardust allows to deploy several
different models, for example models having different IDs, into one partition
of an audit trail.
Motivation
Using multiple models in terms of:
- working on separate models to describe business process models at modeling time
- using model elements from other models, like
processes in one model to be invoked as subprocesses from
activities in other models
has the following restrictions:
- Independently deploy and version different interrelated model files is not possible.
- Model versioning in the runtime environment is also performed on the entire model.
To avoid those restrictions, the following
functionality is provided:
- Model elements (process definitions, data types, applications) in one model can be used in another model.
- Parameters can be passed when calling process definitions from different models.
- Several models for deployments in one interaction are accepted.
- Independent versioning of different models.
New Behavior
Models can use model elements from other models, like
for example:
- Processes in one model can be invoked as subprocesses from activities
in another model.
- Applications in one model can be used in processes of another
model.
Benefits
Using multi model audit trail setups provides the option to:
- Structure systems along components with possibly different
development responsibilities.
- Enhance potential for reuse while retaining a holistic end
user view on all processes of the resulting system.
Features
The following features are provided by using multi model audit
trail setups:
- Possibility of cross-references between arbitrary process models
to process definitions, data types and applications
at modeling time.
- Passing parameters when calling process definitions from different models.
- Independent versioning of different models.