Hello NERM experts, having a little trouble building out a workflow that will link a newly created assignment to a person profile.
In my initial workflow I create a person profile, while also creating a assignment profile in a sub workflow, and establish their relationship using the profile check action step in the parent workflow (person profile creation flow).
In this use case the the person and assignment profiles get created along with their relationship correctly established. See image below for a visual.
What I am needing help with is that a person could have multiple assignments associated with it, and any avenue I have tried in creating a new assignment and associating with an existing person profile I am not having success with.
To add a new assignment I am using a update workflow initially, in order to have the option to create a new assignment action visible on the person profile cube, as seen above in the first image âAdd Assignmentâ. All this workflow does is immediately call a sub workflow to create the assignment while passing the person id the workflow begins from, reference the image below.
The sub workflow then continues with collecting assignment data before creating the assignment, then using the profile check to establish the relationship to the person profile with the person id passed down
The shortest answer is âEnsure that the âpeople/personâ reference from the original person profile is included in the newly created assignment.â
There are multiple ways to accomplish this and generally the preference is:
Get âPreliminaryâ person information (first name, last name, email, phone, etc.) that you want to use for the duplicate person check. This will allow you to determine if this is the same person and an additional assignment or a new person (perhaps with the same name).
If net new person - create a person record and store the reference.
If additional assignment - store the person profile reference.
Call the workflow to create the new assignment profile and pass the reference from above.
Thanks for the quick reply Ed, in your second bullet âIf additional assignmentâŚâ is the update workflow not essentially storing the person profile reference?
In other words, since the parent workflow is acting upon the person profile initially, does that not store the person profile?
Which would allow me to store the person id and pass it down to the sub workflow where the assignment is first created, and then attempts to link the newly created assignment with that passed person id?
Iâm not following the specifics of your question, but essentially each workflow works with a single profile type and you must explicitly âsaveâ to commit this record. It sounds like youâre creating the assignment profile and then updating it to be attached to a person profile. Generally the approach is create a person profile, check for a duplicate (If a duplicate get the reference from the duplicate and discard the ânewâ person profile before saving it. If net new, then save the profile.), call the create assignment workflow passing it the person profile reference obtained earlier and it should automatically be added to the new assignment profile.
I believe I understand what you reference in the needing to commit, as well as the duplicate prevention step.
That being said, does that mean this process (linking a new assignment to a existing person) could not be started from a update workflow?
The reason I am starting with the update workflow, is to have the option for the manager or admin to add a new assignment using the workflow action button from within the persons profile cube as seen in the first image of my original post.
Based on your explanation this wouldnât be possible and would have to be started from the NERM homepage, essentially beginning with a create workflow.
If youâre using the âNew Assignmentâ action button within a person profile, then you should be calling a âCreateâ workflow to create the new assignment and simply pass the person profile reference in the workflow call.
âUpdateâ is only used to modify the existing profile (person in this scenario).
The thing is that is what I am doing, the image below is the run workflow action step in the update workflow. This kicks off the entire âadd assignmentâ workflow that you can see in the second image of my original post.
As you can see I am passing along the person id, atleast I believe it is actually passing the id, and in the sub (assignment) create workflow I reference the passed person id using the profile check action, but it gives me all sorts of bugs.
For reference you can see the the third image of my original post, where I execute that commit you mention before utilizing the profile check to make the relationship.
This makes sense to me because it seems you are saying we need to pass the assignment_rr_person value in order to set it in the newly created assignment profile. Once the attribute is passed, as seen below:
We dont need the profile check step anymore correct? We just need to set the attribute assignment_rr_person to the passed value in the Set Attribute Value action step?
