With the release of version 17.4.1 of Nintex Bot and version 2.4 of RPA Central, we have introduced a new role, Participant.
This new role will likely be used for users who only need to run a botflow and do not design them.
The Administrator will need to install the bot on the Participants machine and then request access from the bot to RPA Central. If the Administrator sends a request to the Participant, they will not be able to download and install the bot.
Participants will need to have the bot on their machine since that is how we name the bot; user account/machine name.
Participants will be able to either go to the URL for RPAC or open the bot on their machine and click the button which will take them to RPAC. They can run it scheduled or manually depending on what options the Administrator chooses for the botflow before they publish it.
While the botflow is running, the Participant will be able to pause and play the botflow. If the botflow fails, the Participant can take note of what happened and what action failed but the Designer or Administrator will need to make changes so that the Participant can run the botflow next time. The Participant will not have any design functionality in the bot.
If you have multiple Participants that run a specific botflow, it could be a best practice to add the bots of each of the Participants to the botflow before publishing the botflow. This way any one of them can run the botflow in the event of the regular user being absent that day.
Keep in mind that a bot that is assigned to a botflow needs to be in ready status and the user needs to be active for the bot to run the botflow. Otherwise, the botflow will remain in Queued status until the user is active again.
RPA Central will keep an internal list of all the bots that are in ready status and the user in active in the order that this happens.
For example: Two Participants, P1 and P2, are assigned to the botflow. Both Participants bots are also assigned to the botflow.
P1 - logs into their machine at 8:00 am
P2 - logs into their machine at 8:01 am
P2 asks RPAC to run the botflow. RPAC will use P1's bot since that person was in first.
If P1 has a botflow with only their bot assigned to it and they now ask RPAC to run their botflow, the botflow will remain in queued status until the first botflow is complete and P1s bot is back in ready status.