You are viewing limited content. For full access, please sign in.

Question

Question

Auto populate on the second approver when the first approver rejects

asked on March 26 Show version history

This is my process diagram:

I'm having a bug where if the first approver rejects and the requestor revises the original form, the second approver's name is not auto-populated. (But if the first approver accepts and the form doesn't go back to the requestor but just goes straight to the second approver, the second approver's name auto populates.)

I'm using this variable for the default value of the second approver's name:

Please let me know if I can provide further information. I've attached an example of the result when the first approver rejects.

Thank you!

0 0

Replies

replied on March 27

I think I understand your process flow, and kudos for tackling a process without workflow! 

I'm fairly certain that because your process never hits step_id=6 it does not know what would be populated at that step to show on the form. Forms does not "read ahead" in a process since so much of the conditional logic can change with any process step (workflow/form submission/etc.)

Going back to your impressive process without workflow, how is the second approver determined? Do you assign a task to a team and they pick up the process from their inbox? Is it a hard coded name?

When I have built processes like this in the past, I use a field rule "Hide Police Department Approver and > ignore data when hidden > when Police Department Approver is blank" What this does is keep the field blank and not allow a blank default value to be saved at any step in the form until it is available to populate. So once your process hits the second approver and there is a name to populate, it is displayed on the form and will show up on the form that is emailed (to I'm assuming the initiator) upon completion of the process.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.