How to pass datas throught workflows

Hello,
I have to create an onboarding workflow to register external users on the NERM.
I have configured a main workflow (Onboarding External Users) that sends an email to the user, asking them to accept or decline the policy via a Registration Workflow (MET External Users Policy Acceptance).
The Portal Registration memorizes the value of the attribute and it should send it back once completed, but apparently it does not (since it never enters the conditions “Policy Accepted” or “Policy Declined”).

Can someone tell me what am I missing?

Below the configuration I used:

Onboarding External Users workfow:


Onboarding External Users workfow:

MET External Users Policy Acceptance workfow:

Hi Vittoria ,

Two things:

  • Ensure the attribute that you are setting for the policy acceptance is present in the
    form.
  • For your conditions in the “MET External Users Policy” registration workflow, given that there is not a profile at that point , I would confirm that you are basing your conditions off of the “request” value instead of a “profile” value.

Hi Colton,
thank you for your reply!

I have checked the form and the attribute is there:

For your second point: I have tried to eliminate those conditions, but I am not sure which option is correct here (I used to put it static , since I had those conditions that were supposed to check the value of that attribute):


I can’t find a request value to insert.

This was the condition I used

Thank you for your time.

Thanks for the additional information.

“Policy Acceptance” (not sure type of attribute) will be populated by the user who gets the registration invitation on the request form in Step 1 of “MET External Users Policy Acceptance”.

Now if you need to execute the conditional logic based on the policy accept/rejection, you have a condition labeled “Policy Accepted”, this is your third screenshot. In that condition, you have “Profile Policy Acceptance … equals yes” . Based off of your original inquiry, a Profile will not exist therefore the logic you have in your condition would NOT get executed.

Below is an example of what I am referring to. Notice that I am referring to the “request” value instead of the “Profile” value.:


Do note for conditions, request values refer to values set within the workflow execution. On the other hand, Profile based conditions will reference the profile of the execution and look at the profile’s value for the attribute specified.

Finally, I noticed you didn’t include the entirety of your " MET External Users Policy Acceptance" just the first 3 steps. So I am unsure if you are creating a profile. Which could possibly affect the " Onboarding External Users".