This page (revision-4) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 15 KB Kevin Higgs to previous
3 26-Nov-2021 10:22 15 KB Kevin Higgs to previous | to last
2 26-Nov-2021 10:22 15 KB Lilia Urtan to previous | to last
1 26-Nov-2021 10:22 15 KB unknown to last

Page References

Incoming links Outgoing links
PERSONNEL ACTION
PERSONNEL ACTION

Version management

Difference between version and

At line 57 changed one line
The PA type that was established in the [ISPY] must be associated to the form that the PA change will be done on. This is done in the [IMFN] form, selecting the applicable function from the Pxxx screens. In the field PA Type, there MUST be a PA type (as created in the [ISPY]).
The PA type that was established in the [ISPY] must be associated to the form that the PA change will be done on. This is done in the [ISFPT] form. If the [Personnel Action type|PA_TYPE_CODE] is not associated to a function on the [ISFPT], the Personnel Action will not work.
At line 59 added 13 lines
%%information
__NOTE__: High Line does not guarentee that any custom form created can be adapted to use a PA.
PA Types should not be linked to forms that are not designed to specifically to handle PA's.
This would include:
*Any Non-employee centric screens (ie the employee is not the focus of the screen)
*Any form that has multiple instances of the same table in the [form table usages ||IMFDH] (Multiple P2K_HR_ASSIGNMENT_DETAILS seperated by a different Alias).
*Any admin form not set up as a PXXX function (Do not put a PA on the [IEAS] - Use the [PEAS])
%%
This page (revision-4) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop