We’ve a client in Australia who’s looking for advice and guidance on creating role-based views in ARIS Connect through login recognition and filtering of data for role specific artifacts.
Does anyone have any knowledge if and how this can be done and what has been the best practice in this?
Look forward to your views, comments and advice
Matias Kokko on
Hi,
The basic principal is that you have to map ARIS users to Role objects that are used in the process models. Then the (EPC) models where roles are present will be available for the user when view filter is enabled. Same logic also populates the My Content tab.
Mapping between users in UMC and modeled Role objects is done by using the attribute "User/User group association". E.g. if a user belongs to the UMC user group "Sales managers" he will see the processes where a Role object with attribute value "Sales managers" exists.
The mapping between UMC user groups and Roles can also be done via location. E.g. Role belongs to Org unit which is connected to location that is mapped to UMC user group with the "User/User group association" attribute.
Filtering does not affect all model types (e.g. VACDs are always visible). Also I don't know the full list of model and item types that are affected by filtering, but I do know it can all be modified in the Connect configuration.
-Matias