Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Workunit cancelled by ags PA53

 2 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
JudeBac
Veteran Member
Posts: 129
Veteran Member
1/13/2009 1:31 AM

    We are using ProcessFlow 8.03 Pro and j2sdk1.4.2_16. We have a processflow for a Peronnel Action Approval. See below the concerned AGS string. Its is a very simple processflow with query nodes, then an email, then the PA53 ags node, then an email that has the ags return code. The PF is triggered correctly. In the pf admin server, after the AgsPA53, I noticed that the workunit has a status of "Cancel Completed", and then I received an email that the workunit has been cancelled by the processflow administrator. However, the next email I received is the email that confirms the ags return code is 0 and then the PF Admin status changes to "Complete".

    Is there something in the ags that cancels the workunit?

    Additional info: In WF24.1, the workunit has an error message MSG_TYPE_WORKUNIT_CANCEL received for 138  Nbr=1

    Also: the service is a copy of Action Approval. My workaround is to not notify if the workunit is cancelled.

     

     

    _PDL=&_TKN=PA53.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&PCT-COMPANY=&PCT-EMPLOYEE=&PCT-ACTION-TYPE=E&PCT-ACTION-CODE=&PCT-ACTION-NBR=&PCT-EFFECT-DATE=&PCT-APPROVAL-FLAG=Y&_DELIM=%09&_OUT=TEXT&_EOT=TRUE

    Thank you for your time.

    cb

    JudeBac
    Veteran Member
    Posts: 129
    Veteran Member
    1/13/2009 2:26 AM
      Oops, I found it. I am missing this: FROM-WORKFLOW=Y
      and for all you know, it is documented in PF Reference Guide. But how come the sample flo that came with lawson does not have this?
      Michael Thedford
      Advanced Member
      Posts: 19
      Advanced Member
      4/16/2009 9:57 PM
        FYI - The PA52 DOES NOT have this feature added like in the PA53. In my PA flows, if a PA is rejected, the flow will also delete the PA52 record and send out email notifications, other processing, etc... PA52 is coded to immediately cancel the WU if the record is deleted, STOPPING the flow at that point and placing it in the Cancel Complete status, and not continuing on with the additional nodes after the AGS call to PA52. Lawson opened a PT for this and they did not know why it wasn't incorporated into it when the logic was put in PA53. Once I found this out, I had to move my PA52 delete AGS call to be the very last node in the flow, so at least the other processing could complete before the flow stopped in it tracks.