Process Flow to report on actions the day they are entered -

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

Joe Hartney

New Member

Posts: 3

10/28/2015 6:19 PM

A limitation to the PERSACTION table in Lawson that I continue to struggle with is that it does not contain a date stamp for the day the action was entered. I would like to be able to use the date stamp to report on all TERM actions that are entered each day. Our personnel actions can be entered via PA52 or Manager Self-Service and can sit on PA52 for days or even weeks depending on the effective date. TERM actions can also be entered after the fact, i.e., days after the actual effective date. I would like to be able to develop a process flow that emails our security department each day with the terminations entered that day only and includes the date the termination will be effective. I've looked into the workflow that can be created with an action but I'm not sure that is the way I want to proceed. Our actions do not require any type of approval in the system. The HR Associate processing the actions reviews them by running PA100 in report mode and then once she is satisfied that they are all correct, she runs PA100 in update mode. I don't want to create any approval requirement for the TERM actions. Does anyone have any thoughts on how I can accomplish this? We are currently using Process Flow Standard and are still on version 9 of Lawson. I have no workflow set up and do not use any triggers currently.

Thanks!

BarbR

Veteran Member

Posts: 306

10/28/2015 7:22 PM

I agree with wanting date and time stamps on the PERSACTION table! We do processing similar to what you describe in a work-flow enabled the personnel action process flow. You do not need to build in any UserAction or HRUserAction approval steps if you don't need any. The flow only has to do it's analysis, send the email notification, then before the END node use the AGS node to update the Approval Flag on PA53 to release the action for PA100 to process.

Tim Cochrane

Veteran Member

Posts: 154

10/28/2015 7:34 PM

Yes - turn on approvals in PA50 and use a flow. Just because you turn on "Use Workflow" on PA50, doesn't mean the flow has to contain approvals. Instead, you would create a work unit when the term is entered...and you'll have the system date... then a PA53 node to immediately approve the action. Flow might take 2 seconds to complete, and you'll have something you can report from...the work unit start date.

THEN, you create you're email flow that will read the termination work units and send emails to whomever you desire.

Slightly clugy...Yes...but it gets the job done.
I can think of other solutions, but this would be the simplest.

Joe Hartney

New Member

Posts: 3

10/29/2015 6:03 PM

Thanks for the direction Barb and Tim. I'm using an action code we dont use often as a test. The action is named PAYGRADE. I created a Service with the same name and enabled it. I then created a Process with the same name and tied it to a process flow that will just send an email to me. I then changed the workflow flag on the action in PA50 to Y. I entered an action on PA52. Nothing. No work unit was created. Work units are being created from Employee Self Service when an employee adds or changes direct deposit information. I can see that those are working and I know that someone in Payroll receives an email. What could be stopping the work unit from being created with PA52? I looked around a little and noticed that there are no forms defined in Form Definition. Does PA52 need to be defined there? Is there something with the install that I may be missing? I've not used ProcessFlow Administration Tool before so I really don't know if I'm missing something or not. Anything you can think of?

John Henley

Posts: 3353

10/29/2015 6:26 PM

Joe, couple things to check:
1. in bpm / Process Flow admin,
a. did you create blank criteria for the service, and enable (service criteria level definition)
b. did you attach the flow to the service (service process definition)
c. did you define the service variables (service variables definition)

2. on PA52, make sure immediate = N (!)

John Henley

Posts: 3353

10/29/2015 6:31 PM

Posted By BarbR on 10/28/2015 3:22 PM
I agree with wanting date and time stamps on the PERSACTION table!

Hurry up and get on v10 ...

Joe Hartney

New Member

Posts: 3

10/29/2015 6:41 PM

John...Thanks for the info. I have checked everything you mentioned. Yes, everything is set up as you described. I don't have any variables defined on that form but I don't believe I have to. So has a date stamp field been added to the PERSACTION table in v10? That would be great news but we won't be on v10 for 9 months or so. Is there anything else I can check? Do I need to have the ProcessFlow Solutions for HR installed?

John Henley

Posts: 3353

10/29/2015 6:50 PM

Yes, there is a date stamp on PERSACTION IN V10.

BarbR

Veteran Member

Posts: 306

10/29/2015 7:01 PM

Click on the background of your flow in the Designer, and make sure that the Service Name is Action Approval. Not your service name - exactly Action Approval. That is the link to the PA52 Cobol program trigger. Without that, your service won't trigger when an Action is entered on PA52.