Manager Self-Service - Personnel Actions

I am sorta "typing" from the hip.... But what if you just changed security in lsa to be add only for pa52?

We did remove the Change function. But it still leaves the issue of the Add button. If we remove the Add functionality, then managers will not be able to add personnel actions via MSS.

You really can't prevent managers from either changing or adding PA's in inbasket *without* doing some type of customization.

If you tried securing the PA52's for Adds and Changes, you would run into the issue of Adding a PA52.

So,...

If you really don't want approvers changing or adding a PA in the inbasket, you could create a custom PA52 form using Design Studio, and remove the add/change/delete buttons.




[quote]
Posted By dtracey on 04/04/2011 08:36 AM
We have been developing the MSS-Personnel Actions task without customization, including related ProcessFlows. In doing so, we encountered two major system issues; 1) if we left the PA52 Change function available for MSS-inbasket view, a manager could make changes to the original action at any time while the action was going through the approval process within the process flow, 2)the PA52 Add functionality allows the submitting manager to add new actions via the inbasket view. Our intent was NOT to allow changes or additions via the inbasket view.

Lawson is proposing we purchase their customization solution. Looking for feedback from other clients who are currently using the MSS-Personnel Actions task. Did you customize? If so, has the process been working successfully? What issues have you encountered?

Is there anyone who is using this feature and DID NOT customize? How did you get past the two obstacles noted above?
[/quote]