Working w/ PF Triggers - PA52

I beleive that the variable oWorkUnit will tell you the one that triggered the flow.

The variables passed to the WorkUnit are available to you (WorkUnit Variables). You can reference these in your flow without having to redefine them. Any other values needed will have to be Queried by a DME call within the flow.

That did it! Thanks

In the long run you might be better off taking advantage of the built-in PA52 work flow trigger. Lawson delivers an "Action Approval" trigger in PA52, which will trigger a work flow whenever a work-flow enabled action is ADDED to PA52. Here is how to set this up on an example action called "StatusChg":
1. In the PF Admin Tool create a service with the EXACT same name including syntax (StatusChg) that looks exactly like the delivered "Action Approval" Service except that yours is enabled. You don't need to set up any Service variables (I'll explain later). Add/Process the Service Criteria Level Definition for StatusChg. Add/Process your Service Process Definition to link the StatusChg Service to your work flow, e.g. StatusChgFlow.xml.
2. When you create your workflow StatusChgFlow.xml be sure to right-click on the background, Select Process Properties, and Select the Service Action Approval (not StatusChg). This is how the PA52 trigger variables become available to your work flow. You can see all the variables by viewing the Service Variables for Action Approval in the PF Admin Tool.
3. Make the StatusChg Personnel Action work-flow enabled - PA50, Setup tab, Use Workflow=Y. This will cause any StatusChg action entered on PA52 to initiate a work unit.
4. One last note: To prevent work-flow enabled actions from being processed by PA100 before the work-flow is complete (you might have an involved process that requires Director or VP approvals that can take a number of days and could cause a late rejection of the action) Lawson adds the action to PA53 in a hold status (approval=N). So at the end of your work flow, when you are all finished, you must release the personnel action by including a Web Run node that updates PA53 to approval=Y. This will remove it from PA53 and allow the action on PA52 to be processed by a PA100.

We have 23 different personnel actions that are web-flow enabled and custom flows under each one - it works just great!

Barb. Thanks for the detailed walkthru. Would you mind if morphed it into an article ?
>

Not at all, go right ahead. It took me quite a while to figure all of this out myself since there aren't any good comprehensive resources - so I'm glad if it can help others.

May I add. In step 4, I use the transaction object to change PA53.1. Here is the code:

 

_PDL=&_TKN=PA53.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&PCT-COMPANY=&PCT-EMPLOYEE=&PCT-ACTION-TYPE=&PCT-ACTION-CODE=&PCT-ACTION-NBR=&PCT-EFFECT-DATE=&PCT-APPROVAL-FLAG=Y&FROM-WORKFLOW=Y&_DELIM=%09&_OUT=TEXT&_EOT=TRUE

Regards,
Jude

I agree that comprehensive resources are hard to find on this subject, but this article helped me the most: Lawson KB #AR_557613 “PA52 workunit setup instructions”
Also, I did presentations at Lawson user group meetings and at CUE how to create PA52 Personnel Action process flows, and am happy to share my attached PowerPoint presentation with the Lawson Guru user community, which includes sample PA52 process flows for personnel actions such as HIRES, REHIRES, TRANSFERS, etc. To update the PA53 Approval code to “Y”, I used a Transaction Node instead of a WebRun Node in the Process Flow Designer, but either one is fine.
________________________________________
Marcy Graham, MBA, PMP | Sr. System Analyst
Electric Reliability Council of Texas | O: 512-248-3895 | C: 512-925-3334 | mgraham@ercot.com<mailto:mgraham@ercot.com>

From: forums-bpm-pflow@lawsonguru.com [mailto:forums-bpm-pflow@lawsonguru.com]
Sent: Wednesday, October 05, 2011 7:53 AM
To: Graham, Marcy
Subject: Re: Working w/ PF Triggers - PA52
[00009104:00016876]

[Image removed by sender. LawsonGuru.com Logo]<https://www.lawsonguru.com/>
Lawson ProcessFlow Forum Notification
A message was posted to a thread you are tracking.
Re: Working w/ PF Triggers - PA52

Posted by: John Henley
10/05/2011 06:39 AM

Barb. Thanks for the detailed walkthru. Would you mind if morphed it into an article ?
>

________________________________

You may reply to this thread via e-mail; please do not remove the message tracking number from the subject line, and do not include this message in your reply. To view the complete thread and reply via your browser, please visit:
https://www.lawsonguru.co...-w-pf-triggers-pa52/

You were sent this email because you opted to receive email notifications when someone posted and/or responded to a message on this forum.
To unsubscribe to this thread please visit your user profile page and change your subscription options.

Thank you,
LawsonGuru.com

If you will be hiring applicants, note that the hkey value for PA52.4 now
requires a value for action number. The last time I checked, action number
was still not on the hkey for PA52.1.

On Wed, Oct 5, 2011 at 12:40 PM, <forums-bpm-pflow@lawsonguru.com> wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> ProcessFlow Forum Notification A message was posted to a thread you are
> tracking. *RE: Working w/ PF Triggers - PA52

> * Posted by: *M Graham*
> 10/05/2011 11:29 AM I agree that comprehensive resources are hard to
> find on this subject, but this article helped me the most: Lawson KB
> #AR_557613 “PA52 workunit setup instructions”
> Also, I did presentations at Lawson user group meetings and at CUE how to
> create PA52 Personnel Action process flows, and am happy to share my
> attached PowerPoint presentation with the Lawson Guru user community, which
> includes sample PA52 process flows for personnel actions such as HIRES,
> REHIRES, TRANSFERS, etc. To update the PA53 Approval code to “Y”, I used a
> Transaction Node instead of a WebRun Node in the Process Flow Designer, but
> either one is fine.
> ________________________________________
> Marcy Graham, MBA, PMP | Sr. System Analyst
> Electric Reliability Council of Texas | O: 512-248-3895 | C: 512-925-3334|
> mgraham@ercot.com<mailto:mgraham@ercot.com>
>
> From: forums-bpm-pflow@lawsonguru.com [mailto:
> forums-bpm-pflow@lawsonguru.com]
> Sent: Wednesday, October 05, 2011 7:53 AM
> To: Graham, Marcy
> Subject: Re: Working w/ PF Triggers - PA52
> [00009104:00016876]
>
> [Image removed by sender. LawsonGuru.com Logo]<https://www.lawsonguru.com/>
>
> Lawson ProcessFlow Forum Notification
> A message was posted to a thread you are tracking.
> Re: Working w/ PF Triggers - PA52
>
> Posted by: John Henley
> 10/05/2011 06:39 AM
>
> Barb. Thanks for the detailed walkthru. Would you mind if morphed it into
> an article ?
> >
>
> ________________________________
>
> You may reply to this thread via e-mail; please do not remove the message
> tracking number from the subject line, and do not include this message in
> your reply. To view the complete thread and reply via your browser, please
> visit:
>
> https://www.lawsonguru.co...-w-pf-triggers-pa52/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
> ------------------------------
>
> You may reply to this thread via e-mail; please do not remove the message
> tracking number from the subject line, and do not include this message in
> your reply. To view the complete thread and reply via your browser, please
> visit:
>
> https://www.lawsonguru.co...-w-pf-triggers-pa52/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Thanks JudeBac - you are right than an AGS transaction call should be used to update the PA53. That is what I use too - I mistyped when I said in my #4 that I use a WebRun node.