Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Branch Failing??

 7 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Shari
Veteran Member
Posts: 78
Veteran Member
9/8/2008 7:04 PM

    Anyone ever have a branch fail in PFlow?  I am adding some functionality to an existing flow (Requisition Self-Service) where a certain type of req creates a PO on PO23.1.  The PO creation is not the problem - I create a PO using an AGS Call (in PFlow 9 it's a transaction) which then leads to an assign node.  The assign node works as intended (assigning the ags returned codes and messages).  However, then the assign node leads to a branch - this is where it is failing.  The branch "branches off" to either an email to the PFlow admin or continues with the flow as required.  I use this at every single ags/transaction.  Why would it be failing all of a sudden?? I've tried re-creating it by both copying and rekeying to no avail.  Please help!

    Info:  PFlow 9 (LSF9.0 sp4, Apps 8.0.3) Windows / SQL...

    Thanks!!!

     

    -Shari

     

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    9/8/2008 7:18 PM
      I've had problems like this. One solution is to go through an Assign before going to the Branch (the Assign doesn't have to actually update anything). Another time I made the mistake of using a variable name as a Node name and stalled my Branch. Make sure that's not happening.

      Are you using the "true" value as your JavaScript Expression for the last Branch connection? It's a good practice even if your Branch has a simple "yes or no" conditions.
      David Williams
      Shari
      Veteran Member
      Posts: 78
      Veteran Member
      9/8/2008 7:22 PM

        Thanks, David -

        Yes, I always include a "true" value as the last "catch all" in all of my branchs.

        I'll take a look at your other suggestions and make sure I don't have a variable name as a node name...although, I think the last attempt I made I just let it default...

         

        -Shari

        Shari
        Veteran Member
        Posts: 78
        Veteran Member
        9/8/2008 7:37 PM

          Yes!  That was it - the following query node had the same name as my variable.  Thanks much, David!

           

          -Shari

          KK - Infor
          Veteran Member
          Posts: 61
          Veteran Member
          9/9/2008 3:15 PM
            Shari,
            Could you please put in the conditions that you have in your branch statements.

            KK
            Shari
            Veteran Member
            Posts: 78
            Veteran Member
            9/9/2008 4:24 PM

              KK -

              The first condition is:

              AgsReturnCode != "0" && AgsReturnCode != "116"

              If this condition is met - there was a failure...the admin is emailed the code and message and they have to fix.

              Other wise the condition is a "true" - and the flow just continues. 

              Does this help?  The problem that caused my branch failure was the next node that followed the true condition - the node name was the same as my variable name.

              -Shari

              KK - Infor
              Veteran Member
              Posts: 61
              Veteran Member
              9/10/2008 1:20 AM
                Shari,
                Try without the qoutes.
                i.e AgsReturnCode !=0 && AgsReturnCode != 116


                "the node name was the same as my variable name." -> Do you mean the Assign node's 'Caption'?

                - KK
                Shari
                Veteran Member
                Posts: 78
                Veteran Member
                9/10/2008 12:19 PM
                  KK -

                  The quotes were fine. Yes, the error is that the branch didn't know what to do next...David had suggested I look at the next node and it was, indeed, the query name, not the caption (I rename them for ease of troublshooting and documentation) was the same as one of my variables. That was what was causing the error. Thanks anyway!

                  -Shari