"agsid_RETURN_CODE" is not working

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Shane Jones
Veteran Member
Posts: 460
Veteran Member

    I have a Pflow that has four AGS calls to update information and then I have a Branch that looks to see if any failed

    != 0 || != 0 || != 0

    This is in a branch but does not work....   I just want to send the flow in a different direction if any of the AGS calls fail.

     

    Any ideas?

    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    John Henley
    Posts: 3353

      What version of PFlow?  If LSF9, I have seen some patches for that...

      Thanks for using the LawsonGuru.com forums!
      John
      Shane Jones
      Veteran Member
      Posts: 460
      Veteran Member

        The strange part is that when I remove the branch and just send an email with the RETURN_CODE and the RETURN_MSG....   I get what I would expect to see.   However when I try to direct the flow based on the success or failure of the flow it nevers uses the failure route.   (even though one of the AGS calls fails).

        The following should mean the AGS did NOT succeed:

        agsid1000_RETURN_CODE !=0

        The following should mean that at least one did not succeed:

        agsid1000_RETURN_CODE !=0 || agsid2000_RETURN_CODE !=0

         

        Is my logic correct?   At least then I will know if it is Pflow or if it my branch expression.   I was wondering if I should be using '0' so that the zero is seen as a string or if it should be seen as a number.

        Shane Jones
        Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
        Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
        ** Teach others to fish...
        John Henley
        Posts: 3353
          How do you have the branch node set up? Remember that it goes from top-down, and first "true" condition wins...
          Thanks for using the LawsonGuru.com forums!
          John
          Shane Jones
          Veteran Member
          Posts: 460
          Veteran Member

            It was me....    I included the variable with    - - - - -     should just use the name without the

            Another case of the software being inconsistent in how to write things...   You use the in other nodes but NOT in the branch node expressions.    

             

            Shane

             

            Shane Jones
            Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
            Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
            ** Teach others to fish...
            John Henley
            Posts: 3353
              Ah yes...that one has tripped me up before. Another one to watch for is that field names from related tables in DME queries...They are generated with the ".", and need to be changed to "_" in order be compliant with Javascript. Lawson has finally fixed that one.
              Thanks for using the LawsonGuru.com forums!
              John