Question

Forms Previous Submitter

Forms

Updated March 7, 2018

asked on April 21, 2016

Why does it seem like previous submitter is actually routing the form back to current submitter? I need to route my form back to the actual submitter prior to the person that is reviewing the form and clicking "return to previous user" . But when I use "previous submitter" it seems to be sending the form back the the same user and not the previous one. Am I just setting up the process incorrectly or does anyone know how I can set up my process to work this way?

Thanks!

1 0

Replies

replied on April 21, 2016

OK, that explains why. If you look at it from the logic of the software, when it gets to the "Contractor To Make Requested Corrections" user task, the previous submitter would be the person who submitted the "FCC to Review and Complete Closing Packet Data" user task.

Is the "Contractor To Complete Closing Packet" always assigned to the same user?

2 0

replied on April 21, 2016

Can you post a screenshot of your process and specify where you are setting the previous submitter value?

1 0

replied on April 21, 2016

Yes! Thanks for taking a look at it!

LF Prev Submitter Issue.jpg (52.96 KB)

| Download

0 0

replied on April 21, 2016

No, its assigned to a team, so we were hoping that this would somehow pick up who from the team submitted the packet as they end up being the one that needs to submit the corrections.

I guess it makes sense that the previous submitter is the "FCC", but for our case it makes it seem like that is the current submitter because they just requested the corrections.

Any suggestions?

0 0

replied on April 21, 2016

You can add a field on the form used in the FCC step and set the default value of this field to use the previous user submission->participant->user name variable({/dataset/_fs_submitter}) as default value. In the Make Requested Corrections step, assign task to this field variable.

1 0

replied on April 22, 2016

Ohhh!! Great Idea!! This worked for us...thank you so much :)

1 0

replied on March 7, 2018

Question about this. Doesn't a field configured with a default value only set once? Even when cleared with javascript. So this would only work one time.

Here is our process. The sales order update task is assigned. When submitted it is sent through a parallel for both approval and re-assigning the update task for future updates.

They want to update the sales order update task to assign to a team but I feel like this will remove the ability to decline, because the previous user token always seems to return the current user, the person who just clicked Decline.

0 0

You are not allowed to follow up in this post.

Question

Question

Forms Previous Submitter

Replies

Sign in to reply to this post.