Hi Community,
We have discovered a very strange and unpleasant issue in ARIS 10.2025.10.0.320004173 on-premise.
The task itself was quite simple: we extended the method for the Organizational chart model type and added additional allowed connections between Role and Organizational unit, specifically:
- Role → Organizational unit: is organization manager for
- Organizational unit → Role: is composed of
From the method configuration side, everything looks correct. The connections are added to the model type configuration and are visible there.
However, another user with full access was not able to create or delete these connections in the model.
This user had:
- ARIS Architect license
- full database permissions
- all function privileges are enabled
- access to everything that should normally be required for modeling
After a lot of testing, we found something very strange: these connections can only be created or deleted if the Process Governance function privilege is enabled for this user.
This was confirmed experimentally. Even if the user has only the ARIS Architect license, with all other function privileges disabled, but Process Governance enabled, editing these connections becomes possible!
To be honest, this looks very odd, because Process Governance is related to ARIS APG, and, as far as I understand, should have nothing to do with method extensions or the ability to create a normal modeling connection in an Organizational chart.
The bigger problem is that users with an ARIS Designer license do not even have the possibility to enable the Process Governance function privilege. As a result, Designer users cannot use these newly added method connections at all.
So effectively, if we have 1 Architect and 10 Designers, only the Architect can use the new connection, while all Designer users are blocked. This makes such method customization almost unusable in a normal project setup.
What makes this even more confusing is that we found this issue specifically when adding new connection types to the method.
Other method extensions seem to work normally. For example, adding assignments to objects or adding attributes works without any problem. Designer users can use those changes normally, without any dependency on Process Governance.
Even more interesting: we have another customer environment where Process Governance is not available at all, and the same type of method extension works correctly. A new connection is added to the method, and it becomes available for Designer users both with the full method filter and with a customer-specific filter.
That is why this behavior looks very much like a bug.
Maybe we are missing some hidden configuration or dependency, but from the administration point of view, this looks extremely inconsistent.
Has anyone faced something similar?
Any comments or suggestions from the community or SAG would be highly appreciated.
Best regards,
Florian Gerdes on
Hello Alexander.
For me that sounds strange but might be intended. When modelling an APG Workflow we are using special function symbols for automated tasks, notifications, manual tasks, end events and many other cases. Those symbols (standard objects like function/event) are only available for users with the APG license.
Also in the APG you use the model type "organization chart" for roles/departments and so on to great APG specific users or usergroups. So maybe (I don't have an overview) of this, you used connections, which are only meant to be used for such APG cases.
From my perspective you have 3 options:
I hope that helped.
Kind regards,
Florian