when configuring transitions in the workflow, I would like to be able to assign a property value to another property value. This will allow the creation of more templated workflows to speed replication.
Currently, I can only assign a property value from a free text value or user.
However, 'Assigned To' can be assigned from 'Creator'.
In our particular use cases, being able to assign 'Assign To' to another property value will allow us to assign a placeholder property (for example: "Approver") one time in the initialization settings and then use that value over and over in the workflow.
When cloning the workflow to another project, only the assignment in the initialization settings needs to be changed. This offers great flexibility for even more templated workflows.
Hi Stephen,
Let me know!
From my understanding, it sounds like you are explaining the concept of setting the Property Assignment on a Transition button to Use the "Assigned To" Property and then assign it to a User based on some other attribute that is set at the Project level. Is that correct?
Is there a reason you cannot use Role to accomplish this?
Once you Create the Role of "Approver" (or something more specific like "Form Type W Approver") and grant it to User X on Project A and User Y on Project B. you can set your Workflow once and have it apply correctly for this FormType on all Projects as long as that Role is used.
Caitlin