Is there a way to fetch the user “Assigned To” after the Human in loop is completed in the Action center. I tried to get the output data object out from the wait and resume task, and i couldnt find the variable or way to get the “Assigned to” user name from the Action center.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Not sure if there is a simpler way to do this, but you should be able to get more info about a task by using Orchestrator HTTP Request.
Endpoint would be - “odata/Tasks(taskId)” where taskId is the action object id and in the response you have a field called AssignedToUserId.
As I imagine the UserId by itself is not exactly what you need, you can call the orchestrator for more details on that user with “odata/Users(AssignedToUserId)”.
Doing it this way is not exactly as straightforward as a theoretical ActionObject.AssignedToUser would be, but I hope it gets the job done for your usecase.
Action Center users will now receive built-in notifications through two channels, in-app and email to notify them with the most relevant events like Action assignment (bulk& single), Action forward and Action un-assignments. Users can manage their own preferences for opting-in or opting-out of these notifications from user profile itself. All cloud customers will have this feature enabled without any pre-requisites or changes in the workflow.
Maybe it’s because of the permissions. Now that you access information about users your executing user (typically robot role) needs view permissions for those to. You also need permission on Action Assignment.