In Bizagi, you create end users and configure their information directly at the Work portal. Within the information you configure for each end user, you may map if these end users belong to any specific Stakeholders.
However, there is an option in Bizagi Studio which allows you to define a condition to automatically map end users into Stakeholders in batch.
Through this option, you will be able to speed up the initial information regarding end users and Stakeholders. When ever a deployment is made that updates the Stakeholders configuration, all users that comply with the conditions (or no longer comply them) will be updated.
Defining conditions for your Stakeholders
In order to define a condition to automatically map users, go into the Expert view and click Entities.
Locate the Stakeholder node and right-click it to select the Stakeholder configuration option:
In this window, you will be able to define a condition that determines which users will be marked for each of the different Stakeholders.
To do this, first select a Stakeholder in the left frame and then create a condition by building graphically an Or/And definition:
The image below shows how the Card Manager Stakeholder should automatically consider all users which have Authorization level set to Card manager OR those users whose Role is Manager.
Notice that this is a boolean condition, and you may use any information belonging to the user such as its role, skill, position, or even custom user properties.
At this point, once a new user is created in your Work portal, if it matches the condition set through this option, then it will be automatically mapped to that specific Stakeholder.
If you wish to run the validation immediately so that it applies to existing users as well, refer to the Migrate users option as described below.
Using the Migrate users option
You may click the Migrate users button to automatically map into a Stakeholders, those existing users whose information currently comply to the condition defined.
Recall that this is done only in the development environment since this button executes immediately the validation to check if current users meet the condition.
You may verify directly in the Work portal that such users are mapped into your Stakeholders, due to that condition definition:
Consider these notes:
1. Manual configuration/revision may still be needed.
Note that there will most likely be additional information which varies from Stakeholder to Stakeholder (and which are not applicable specific to WFUser).
Since this additional information is not present in the WFUser entity, then you will need to enter it manually.
This means that even though you use this feature (with or without the Migrate users option), you may need to edit the information of a user which has been automatically mapped as a Stakeholder.
2. Unmapped users
As soon as a user mapped to a Stakeholder stops meeting a configured condition, he/she will be removed from the Stakeholders configuration. His/her Stakeholder record will be automatically disabled to maintain data integrity.