pflow query output "is not defined" error

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Duane
Basic Member
Posts: 17
Basic Member

    I need help on a process flow query. When I run a query against the REQHEADER table, I pull the field ACTIVITY. I do a substring function  - if the ACTIVITY number starts with 01, 02, 03 do this, if not, do another.

    This logic works, however, not all Requisitions will have an ACTIVITY number. So I'm trying to instruct the flow if no ACTIVITY exists, just keep on going.

    So far, I've tried ACTIVITY == "", != "", == "undefined", != "undefined, > "", = "", > null, = null.

    I keep getting the same error in the process flow log - ACTIVITY "is not defined"

    Any suggestions on how to set up this query?

    Thanks everyone!

    Duane
    Basic Member
    Posts: 17
    Basic Member
      I am reading some things on the internet regarding "The main thing to understand is that the environment from the original page request is discarded when the response is sent to the browser." Since I'm trying to use this query output variable after a UserAction node (sends Approve or Reject requisition equest to the Inbasket) have I lost all my query output variables? Do I need to re-query, or just add ACTIVITY to the service variables? Will this maintain it for me throughout the flow?
      Duane
      Basic Member
      Posts: 17
      Basic Member
        I believe that Gary Davies has answered my problem under "Variable disappearing after User Action node" but not exaclty sure.
        John Moren
        New Member
        Posts: 2
        New Member
          To specificy a condition in a Lawson DME query where a table value is blank or not blank the just specify the value and operator in the select statment with nothing following the operator. Like this:

          PROD=PROD&FILE=REQHEADER&OUT=CSV&DELIM=~&FIELD=COMPANY;REQ-NUMBER&SELECT=ACTIVITY!=&MAX=1

          I limited this to one record since there were no other selection parameter on the query.
          Gary Davies
          Veteran Member
          Posts: 248
          Veteran Member

            You don't have to add it to the workunit variables although that would work, you just need to create a variable in the Start node and save the result of the DME query to it before executing any User Actions then reference that variable after the inbasket action.   You may want to requery instead if the activity can be changed in the inbasket.