Hi @Praveen123,

If your smartobject has those fields to store the FQN and DisplayName, there should not be any issues. Once you transfer the data to your variables in your workflow, you can simply use the smartobject method to store those fields. 

Kind Regards

Prineel

Only gotcha I have seen in the past is if you can action the work item without opening the form.  This would bypass your form actions for capturing the user id and passing it to the workflow.

If you’re attempting to gather that information within the workflow after the task was completed by a user, you could use the Task User object within the context browser on the right hand side. I believe these values will automatically map to the user who most recently actioned the task. I use a SmartObject method right after the Task to update relevant data within my SmartObject based on the Task User who actioned the Task. 

Another option would be to update your data from within the Form itself. You can utilize the Current User variables within the SmartForm to update relevant data once you submit your form.

presend2 wrote:

If you’re attempting to gather that information within the workflow after the task was completed by a user, you could use the Task User object within the context browser on the right hand side. I believe these values will automatically map to the user who most recently actioned the task. I use a SmartObject method right after the Task to update relevant data within my SmartObject based on the Task User who actioned the Task. 

Thanks for replying. Problem with using the Task User object is it doesn’t have the actual user details if the task is assigned to a role which has AD group according to this post -

(see the last reply in there).

I haven’t personally tried it though so might give this a shot too and see what it comes up with. We are on 5.2 version.