The "Requisitioner" creates a requisition in our procurement system (for financial approval) and also starts a LF Forms process (for technical content approval). A PDF file of the requisition from the procurement system is attached to the LF Form. If the financial approval is rejected, the Requisitioner must be able to "recall" the process so they can provided an updated version of the requisition in the LF Forms process. Has anyone figured out a way to do this, keeping the control with the Requistioner instead of a Forms administrator?
Question
Question
Answer
You can use signals for this. Think of them as radio signals that allow parallel tasks to communicate with each other.
The Req can have a parallel task assigned, where an action leads out to a signal throw event. This broadcasts a signal across the entire process, anything listening on the same channel (configured in the signals) can take action on it.
You can right click on the task you want to interrupt when the signal is received to add the signal listener. Then draw a path from the signal to determine what happens next.
Replies
OK, the signal worked! The "Recall Notification to Reviewers" email goes out to each user.
But then the task says it's "In Progress" but nothing's happening:
I want everyone's tasks to end and go through the Rejection route. Here's the logic behind the "Approval Routing":
Is there something wrong there? I tried just ending the task once after emailing the reviewers, but that just terminated the process.
Figured it out! I needed to change my Recall Signal Throw Event to skip the merge and head straight to Approval Routing!
My preference would be to use a different parallel for the Recall Task, instead of sharing the one called Approvals. Approvals should only have 4 outgoing paths and 4 paths that close out at the Merge step.
The parallel used for the Recall Task can have no closing object and simply go to a termination.
You can also add another signal after the merge task that signals to close the Recall task.
Thank you. Can I have two broadcasts? In the image below, the items circled in RED are working beautifully. Now I'm trying to set something up where the Requisitioner Recall Task will disappear once all the approvers have completed their tasks. See items circled in PURPLE. It doesn't appear that the Requisitioner Recall Task is no longer listening.
Thoughts?
I all set! Found my issue. Had to move the Complete Signal Throw Event to the approved path of the Approval Routing.