Passing arguments in Reframework from Process Transaction to Set Transaction Status

I’m having problems passing arguments in a reframework RPA. I created an out argument in the process transaction workflow that uses flowchart to invoke 3 workflows. In the last workflow, I create an out argument - out_Ebs_Account_Disabled. I see that this arguement is populated. I defined a variable, ebs_Account_disabled in the process transaction workflow. This variable is not populated. I would like to use the argument in the SetTransactionStatus workflow so I define an argument in_Ebs_Account_Disabled in that workflow. Unfortunately the argument is not populated in the SetTransactionStatus workflow and I’m not sure why?

did you already make sure that ebs_Account_disabled in the process transaction workflow is populated with a value yet?
did you already checked that you inputted ebs_Account_disabled as the value for in_Ebs_Account_Disabled for each Invoke SetTransactionStatus in Process Transaction (success, BRE, Exception)?

Ebs_Account_disabled is not populated in the process transaction workflow. It is populated in the 3rd workflow, W003 after invoking UiPath_EBS_UserAccount_EndDate workflow in the process flowchart. I’m guessing this is why it’s not populated in the invoke SetTransaction Status. Maybe it would be help to understand how arguments and variable works between workflows, invoking the Process and SetTransactionStatus

Thanks,

Tammie

You could learn about the directions of arguments in

or learn it from UiPath Academy in Arguments Course.


Basically,
In → used to pass the value of a variable in your current Workflow to be used in a Workflow you Invoked.
Out → used to pass a value in your current workflow to be used outside of your current workflow.
In/Out → has both properties.

From your screenshots, I didn’t find any UiPath_EBS_UserAccount_EndDate workflow being invoked. If i had to guess, your problem is passing a value from Workflow W003 to be used in SetTransactionStatus workflow, am i right?
If yes, here’s the solution:

  1. Make an out argument in W003 named out_XX, for example.
  2. Make an out argument in Process.xaml workflow named out_YY. Use this out argument as the value for out_XX when invoking W003.
  3. Make a variable in Process Transaction state in Main.xaml named ZZ. Use this variable as the value for out_YY when invoking Process.xaml.
  4. Make an in argument in SetTransactionStatus workflow named in_AA.
  5. Back to Process Transaction state in Main.xaml. Use ZZ variable as the value for in_AA when invoking SetTransactionStatus.xaml.

The flow of passing data should be like this:
out_XX->out_YY->ZZ->in_AA

Actually UiPath_EBS_UserAccount_EndDate workflow is being invoked from W003 – DisableEBSUser workflow. I’m actually made an out argument in UiPath_EBS_User_Account_Enddate. I need to pass this back to used in SetTransactionStatus workflow. Would the solution still be the same? I’ve watched videos and user UiPath academy but still having problems with getting the value passed back to SetTransactionStatus.

Thanks,

Tammie

Thanks,

Tammie

In the UiPath_EBS_User_Account_Enddate.xaml file, have you assigned the value to the out_argument?

Either through an assign activity or through the arguments panel?

I see that on this higher levelDisableEBSUser you map the argument to a variable in that flow. But I’m not seeing that you map the value to the out_argument.

Also as a tip, as per general guidance, best to name your output arguments with ‘out_’ prefix. Makes it a bit easier.