I think you are on the right track. The Update workflow is run from a Profile, so there should be no need to “search” for the profile once the Update Workflow is started.
In general, we would see the flow of an Update Workflow like this:
- User searches for an selects the Profile they want to update from the Dashboard (Profiles Tables, Search Bar, Advanced Search, etc)
- On the Profile Page, they can select the appropriate workflow for the Update they want to perform
In that workflow would be the actions for the values you want to update. For example, We often see a configuration like the below for a general-use update workflow:
- Request Form action - The page/forms configured for this action contains all of the attributes that a user might want to update, such as Start / End Dates, email addresses, Job title, etc.
- Approval Form action - Once the request submits their requested changes, an approval will go out to a Manager or Admin user role to confirm the changes can occur.
- Update Action - if approved, the updates take place on the profile
If you want to see the old values along-side the new values for an attribute, you may need to get a bit creative with using multiple attributes for values or utilizing liquid to display the values.
For example, with liquid ( Liquid Template language use in NERM ), you can display the Profile’s value of an attribute vs the Request value. So, in the above example, if we changed the end date; {{ profile.end_date }} would hold a different value than {{ attribute.end_date }} during the step 2 Approval form if it was changed during the Step 1 request form.