Assign stakeholders by condition in test and production environments

Last Year


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 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 you deploy a Stakeholders configuration for the development environment, you need to follow the steps mentioned below, to update all users that comply with the conditions (or no longer comply them). Thus, users in the project that meet said conditions will be assigned to a Stakeholder configuration. Users than no longer comply with the conditions, will be removed.

Applies to

Bizagi 11.2.2
Bizagi 11.2.3
Bizagi 11.2.4

What you need to do?

Follow the next steps in order to assign stakeholders by condition:
1.    Go in Bizagi Studio to the Expert view and click Entities. Locate the Stakeholder node and right-click it to select the Stakeholder configuration option.

2.    Select the Stakeholder for which you want to configure a condition and then create it by building graphically an Or definition.

In this example, the Card Manager Stakeholder should automatically consider all users which have Authorization level set to Card manager OR those users whose Role is Manager.

3.    Deploy your Project in the environment where the synchronization is going to be done.

4.    The stakeholders mapping must be done in the Management Console. However, this option must be activated through a key found in the appsettings file. Locate the Management Console appsettings file in your computer and open it.

5.    Locate the MigrateUsersToStakeholder key and set it to true.

6.    Open the Management console and click Migrate.


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.

3. Stakeholder definitions
Currently the And conditions for stakeholder definitions is not working. For the stakeholder definitions, use only Or conditions.

4. Manual stakeholder assignations
The stakeholders assignment in the Work Portal has priority over the assignment done automatically.

Rate this Article:


Last Modified:Last Year
Last Modified By: JuanG
Level: Beginner
Article not rated yet.
Article has been viewed 588 times.