Process Flow - Return Workunit Task to user that initiated it?

Hi. I'm in the process of building a workflow that needs to have a "Send Back" function. When the "Reviewer" presses "Send Back" action the work unit needs to go back to the inbasket of the person that initiated the request so they can correct the information and re-submit it for review once again. Can somebody hint at the best way of accomplishing this is?

Also...in my version of process flow designer 9.0.1 there is "Work Object" node...but the PFUG manual for 9.0.1 does not have any information on what the "Work Object" node is for?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

robert-canham

We're implementing requisition approvals right now, and we did this by using an unrelease function. This opens the requisition back up so the initiator can modify it and resubmit it for approval. It creates new work units though since it is being released again. It may be different though depending on what type of item you're working with.

As for the "Work Object", that node is used to call a Process Flow from within a Process Flow. There are two ways they can be used, async kicks off a new Process Flow but keeps going on with the calling flow. The sync version kicks off a new flow and waits for it to complete before moving on with the calling flow (this can be used if you want to return information to the calling flow).

0909090854053232.pdf

mguevara

We have implemented requisition approvals the same way as Robert. We have an approve or unrelease option. Our procedures are for the approver to add a comment to why they are not approving before choosing the unreleased option. The flow writes that comment out to the header comments of the requisition and sends the requestor an email stating the requisition was unreleased and includes the comments from the approver. Then the flow ends. The requestor then corrects the requisition and releases it again and a new work unit is created.

Inquiry Tab Placement.docx

jacob-jellison

Thanks for all the feedback. There is no "unrelese" function for a job requisition (PA42) so I'll be creating a special status and then e-mail the initator that they need to correct whatever it is that's wrong with the request.

But your responses clarify something for me. Once the initator corrects the data they have been told to correct and "Submits" then:

1. Old workunit will end
2. Old requisition will go into a DENY status.
3. New workunit assigned
4. New Requisition number assigned

Urgh!

Thanks.

robert-canham

Michelle, out of curiosity, how did you allow someone to enter comments? Did it get written into your display exec somehow?

mguevara

From the Inbasket in portal, the user chooses the messages link and adds a message there. In the flow, we use a Lawson Query node to query the WFMSGDTL file in Logan for the workunit and RM Id of the approver. The id of the approver will be in the MESSAGEHDR.Attach-By field.

I did not create this flow originally. We are in the process of converting to Process Automation, so I am more familiar on how it works IPA as we had to recreate all the Logan queries to Landmark.

robert-canham

Thanks Michelle. We are implementing on IPA right now, and we don't have the time to do that now, but it is something I can look at for a future enhancement.

jreese

Michelle,

Can you please attach the query you are using for IPA for doing this process? I am currently rewriting our ReqApproval flow for IPA and this would be very useful and time saving for me.

mguevara

Sure in IPA it is the Landmark Transaction node: We are using a variable from a previous Landmark Transaction that gets the PfiUserProfile (RM ID)
Here is the transaction string:
_dataArea="" & _module="pfi" & _objectName="PfiMessage" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _pageSize="30" & _filterString="PfiWorkunit="" and AttachBy="" " & PfiWorkunit & AttachBy & Message

Managing Monthly Releases within M3 CloudEdition 2020-05-14.pptx

jreese

Thank you

Copyright © 2025 Infor. All rights reserved.