I have a Create Workflow used to onboard external users into the NERM. Based on the attribute they have after the creation of their profiles, the external users can have different roles and visibility when they log into the platform, but all the roles can create other external users by using the same workflow of onboarding.
However, when an user with the role of Vendor ADMIN logs into the NERM and decides to create a new external users, a condition in the onboarding workflow should trigger (the condition check if in their profile the attribute Vendor Admin is set on Yes) and show them a different form of creation. Below you can see the condition:
The problem is that, after the creation of the Vendor ADMIN user, the onboarding workflow seems to not be able to read their profile attributes, even if the Vendor ADMIN user is a Portal User, so the profile is linked directly to the user.
This is their profile with all the attributes (note: the attributeVendor Admin is not visible in this screen, but it is correctly populated in the tab All Attributes).
You would need a set attribute step for sponsor_vendor_admin_ne_attribute you would choose on the Set As option you would choose the “requesters profile value” and then choose the sponsor_vendor_admin_ne_attribute .
Furthermore, for conditions or actions, Request vs Action values:
Profile is going to reference the profile of workflow. (Meaning for a create , if you haven’t done a profile check/ duplicate prevention check/ or a create action. The profile would be nothing. Update workflows would reference the profile you are executing the workflow against)
Request would reference the value set in the workflow execution.
I think the problem is because the requester’s user page is not directly linked to their profile (as I thought it was), so the system can not process that information. I will try to fix this.