Skip to Main Content
ARIS - SHARE YOUR IDEAS
How can we make ARIS better?
Status Open for voting
Created by Christina Reinshagen
Created on Oct 21, 2022

Prevent Modeler from creating new library objects

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.

  • Nicola Adas
    Reply
    |
    Feb 29, 2024

    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).

  • Frank Engelbert
    Reply
    |
    Jan 2, 2023

    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.