ARIS - SHARE YOUR IDEAS
Library objects, like applications, roles, capabilities etc. should only be reused by Process Modelers. In a structured database they are always stored in special groups with only restricted write access.
At the moment every modeler can nevertheless create new applications etc. during process modeling. It is possible via i.e semantic checks to prevent these objects from being published/releases, but it is always work afterwards for Modelers and/or Admins needed.
It would be much better, if Admins are able to prevent that object of special object types can be created from scratch by Modelers.
Very similar or identical to ARISD-I-247 --> can the two be merged and the votes cumulated?
I agree, this is very useful and also the reverse when dealing with BPMN modeling objects like tasks, rules, events where an object should not be allowed to be reused (could be an option within the object configuration).
Agree it would be great to have a solution for this.
However this ("It would be much better, if Admins are able to prevent that object of special object types can be created from scratch by Modelers") applies only to As-Is Process Documentation.
A big aspect of ARIS is To-Be Design. During Design phases, creating new objects is essential.