Migrate the "Add Automation Task to Queue" AC using Nintex Migration Tool
Since shifting to work with queues instead of groups/robots (starting from v. 21.4), the "Add Automation Task to Queue" advanced command now requires manual modification that includes migrating it to the new 'working with queues' mode.
Nintex Migration Tool can map the existing Robots fields in the "Add Automation Task to Queue" ACs to the relevant Queues.
So how does it work?-
The tool gets all the available Queues from the Queue manager and all the available Robots/Groups from the Database.
-
Then, it looks for the "Add automation to Queue" AC in all selected wizards (since this AC contains a 'select a robot' field that requires re-mapping to Queue).
-
If the command exist in the selected wizards, the tool converts the Robot field in it to the relevant Queue.
-
Default robot maps to default_queue
-
Group maps to a queue that has the same name
-
Robot maps to a queue that has the same name (if the Robot doesn’t have a friendly name, it converts to the machine name or user name)
-
The required manual modification includes the following steps:
-
Open the Migration Tool
-
Select the wizards that include the "Add Automation Task to Queue" command
What if I don't know what wizards contain the "Add Automation Task to Queue" command?
You can select all wizards to search for the "Add Automation Task to Queue" command and migrate. If you do so, the search-and- migrate process will take longer. The more specific the selection is, the faster the migration process.
-
From the upper tool bar, select the "Migrate to queue manager" option and any other relevant option following the instructions and information in the Using Nintex RPA RPA Migration Tool section.
-
Click Start and let the process complete.