I have a form that has a primary and secondary approver in the same approval step. If the primary approver approves it then it goes down one path and if the secondary approver approves it then it goes down another path. I have a gateway immeadiatly following the approval process that is to route the process based on the above mentioned paths. The issue I have is that the Previous Tasks variables are not available to the Gateway. Why does a Gateway not have access to the immeadiatly proceeding tasks? How can I route the form based on which of the two people approved it?
Question
Question
Replies
Can you attach or post a screenshot of your process? It would be easier to understand that way.
I just want a Gateway to be able to see who approved a form in the previous task. Is there a way for a Gateway to know that?
I don't believe that is one of the variables that is available. You could have a hidden field that populates with the currentuser variable though and then use the conditions of a gateway to make a decision based on that? It should fill with the username of the person that did the approval.
That's what I ended up doing. I created a field called CurrentApprover and set the default value to currentuser. I didn't set it to read-only, so that it gets updated at each step in the approval process, but did set it to hidden so it wouldn't change the form look. So far that seems to work but hopefully the next version of forms will give us more access to the previous task variables. Thanks for the help.
I had made a feature request for something similar, but it would allow a gateway to make evaluate all previous variables. So that way if a process needed to make a decision that was 3 tasks previous to the gateway, it could. Laserfiche replied and said they are looking at making all of that information available through variables in a future version.
Nice work. That idea encompasses mine but adds so much more. Hopefully we get it in the next release.
That ended up not working. It put in the value but never updated it as the form went through the approval process. Part of the issue is that it can be rejected at many places and forced to go back through the whole process and thus I really need that variable of who clicked the approve button during a user task.
I am still running into this issue and am hoping Laserfiche is working towards a solution that allows Forms access to more variables from the approval tasks. Currently I have a form that requires 3 approvals. However if the departmental director approves the form at any step, they want it to bypass all other approval steps. Without having access to the tokens of the previous approver in Forms (writing a workflow that runs everytime to provide this is not a viable option for such a basic request), I do not see how this is possible.