Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Updating PA07.1 with Process Flow

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
David Britton
Veteran Member
Posts: 53
Veteran Member
12/5/2011 8:08 PM
    I am trying to update PA07.1 (Competency Proficiencies) using PFI.

    I need to "Add" a Proficiency and Status to an existing Competency (defined earlier with HR81.4). The problem I am encountering is that the PA07 form requires an Inquire prior to Adding the proficiency. I can't figure out how to do the Inquire.

    On my first attempt I created a transaction node with a Method of "Change" but I get an error that an inquire must be made first.

    I then created a transaction of type Inquire but then I get an error that Line FC was invalid (I had the "A" for Add in the Line FC field).

    Next I tried creating 2 transactions, the first an Inquire with Line FC blank as required, then a transaction with the Change and Line FC set to "A". I again received the error about needing to inquire first.

    I then tried creating an "Inquire" Query (rather than transaction) on PA07 followed by the PA07 transaction. Still got the "must inquire first" error.

    I then tried moving the Transaction inside the "Inquire" query loop and still got the "must inquire first" error.

    I am now out of ideas. Any help will be greatly appreciated.
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    12/6/2011 11:23 AM
      I think I got around a similar issue by using an _EVT=ADD instead of CHG - otherwise leave the rest of the DME call the same for a normal change on the existing form.
      David Williams
      David Burnham
      Basic Member
      Posts: 9
      Basic Member
      12/6/2011 12:53 PM
        In general there are a number of hidden fields on the screen that an inquiry fills out and allows the screen to do the update. To find the hidden fields copy the inquiry transaction from process flow and past it into a browser. The xml that is returned will contain all of the fields for the screen including the hidden fields. You then need to populate your change with the values (variables) from the inquiry. That should take care of the "Must Inquire First" message.

        Be carefull not to hard code these fields unless you know exactly what they are doing. On some screens there are switches that will override warnings that have the "ok to continue" message.
        David Britton
        Veteran Member
        Posts: 53
        Veteran Member
        12/6/2011 9:12 PM
          Got it to work by adding the following to the end of the AGS call:

          &_IGNREQD=true

          I found this by creating an AddIns upload and examining the query string it generated.