• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Work unit sometimes does not update PA53

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
BarbR
New Member
Posts: 0
New Member
12/6/2011 6:50 PM
We occasionally (maybe once every 2 to 4 weeks) find that the PA53 AGS transaction in the work unit does not update the Approval flag to Y.  Everything in the work unit and IOS log looks normal.  I can cut the AGS transaction call string out of the work unit and paste it in the PF Designer and run it and it works perfectly.  This happens on different Personnel Actions and submitted by different users (and the same PA's with the same users work perfectly most of the time).  I can find no pattern.  Has anyone else experienced this? 
jamesraceson
Veteran Member
Posts: 52
Veteran Member
12/6/2011 7:47 PM
Barb,

Yes I have. There is no "pattern", but sometimes it depends on how much traffic is going on that I have seen it not update sometimes. There will never be any "errors", but it will not update sometimes. What I have found that works is to put in a short query after your update section and see if the update worked. Then put a branch node to check for the wanted condition. If true, continue on. If false, have it go back around and run the update section again.
BarbR
New Member
Posts: 0
New Member
12/6/2011 8:03 PM
Thanks for your reply - it's good to know I'm not the only one - I've opened several cases with Lawson to no avail. Your idea is a good one, but since I can't make it happen on demand I don't know how I'd be able to test the new nodes. Also a daunting task as we have 23 work-flow enabled PA's, which means 46 flows (test and prod).
jamesraceson
Veteran Member
Posts: 52
Veteran Member
12/6/2011 9:08 PM
Barb,

One way to put a dent in the task is to creat a function to handle most of the query calls and save it to the pflow.js file. Inside the function (passing what variables needed) you could have it make the query call to the database, check for your conditions, and then return a true/false. This way it would be a smaller footprint in your existing flows, cut down on the amount of work that you would have to do and would not increase the amount of workunits that are created. Just a thought...