Is it possible to make the use of existing objects from a library mandatory? For example: it is our convention to use existing roles (from a role library) in Enterprise BPMN diagrams. However, designers are able to create a new roles within a BPMN diagram. It would be great if users only can include occurence copies of roles in Enterprise BPMNs.
Best Reply
Hi,
a good way of doing this is through governance measures: Before a process model can be approved run a semantic check, which checks the proper use of library objects. Define rules that a certain object type in the model needs to have an occurrence in the corresponding library model type, e. g. an org. chart for role objects (lanes).
Instruct your users to use the semantic check themselves before they submit a model for approval. Otherwise the submission will run the semantic check and refuse to start the approval.
This works perfectly both in Designer/Architect and in ARIS Portal Designer.
Regards, M. Zschuckelt
3 Replies
-
Hi,
if your users are working with the ARIS Architect or Designer, you can write your own macros to support/handle/restrict every modeling action.
However, this is still not supported completely in the ARIS Portal Designer...
Bye,
Frank
-
Hi,
a good way of doing this is through governance measures: Before a process model can be approved run a semantic check, which checks the proper use of library objects. Define rules that a certain object type in the model needs to have an occurrence in the corresponding library model type, e. g. an org. chart for role objects (lanes).
Instruct your users to use the semantic check themselves before they submit a model for approval. Otherwise the submission will run the semantic check and refuse to start the approval.
This works perfectly both in Designer/Architect and in ARIS Portal Designer.
Regards, M. Zschuckelt
-
Many thanks for your responses! Our modellers work in the ARIS Portal Designer, so I will try the option via a semantic check.