Preserve the "sub-step" status in Gravity Flow when one or more assignees are changed in GravityView

When using GravityView with Gravity Flow, you may encounter a situation where you edit an assignee field on an entry with GravityView which does not reflect in the Gravity Flow workflow "User Input" step. 

The snippet below (kindly provided by Rob Davis) extends Gravity Flow user input steps so that when there is more than one assignee, the "sub-step" status may be preserved when one or more assignees are changed in GravityView.

Here's an example of the issue in question:

1. A user (such as a manager) assigns three site users (such as reviewers) to evaluate an entry in a Gravity Flow user input step.

2. Two of the assigned users complete the task quickly, but the third is slow or does not respond in a timely manner. 

3. The manager no longer has the entry in their inbox since they assigned it to the three reviewers in the user input step. Fortunately, with this snippet, they may edit the entry in GravityView, change the third assignee to someone else, and update the entry.

4. Without the snippet, the assignee would change in the Gravity Forms entry, but it would not affect the Gravity Flow workflow. The manager or a site admin would need to restart the step, and even after doing so, the fact that the first two reviewers already completed their portion of the user input step would not be preserved. Their status would go from complete back to pending, and they would need to resubmit their user input even if no changes were needed.

With the below snippet, editing and updating the entry in GravityView preserves the completed status of the first two reviewers, and refreshes the entry to recognize the new assignee! 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us