This page (revision-11) was last changed on 26-Nov-2021 10:22 by jlawler

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

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
11 26-Nov-2021 10:22 4 KB jlawler to previous
10 26-Nov-2021 10:22 4 KB jlawler to previous | to last
9 26-Nov-2021 10:22 4 KB jlawler to previous | to last
8 26-Nov-2021 10:22 4 KB jlawler to previous | to last
7 26-Nov-2021 10:22 3 KB rforbes to previous | to last
6 26-Nov-2021 10:22 3 KB RForbes to previous | to last
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last AVAILABLE_WF_CUSTOM_FUNCTIONS ==> AVAILABLE WF CUSTOM FUNCTIONS
4 26-Nov-2021 10:22 3 KB JMyers to previous | to last
3 26-Nov-2021 10:22 3 KB JMyers to previous | to last
2 26-Nov-2021 10:22 3 KB JMyers to previous | to last
1 26-Nov-2021 10:22 3 KB JMyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 11 changed one line
P2K_CF_WFGES_ENDDISPATCH Customer Specific Special logic to End the Dispatched status for employees that have had specific work restrictions created.
|P2K_CF_WFGES_ENDDISPATCH|Customer Specific|Special logic to End the Dispatched status for employees that have had specific work restrictions created.
At line 15 changed 2 lines
|NEWHIRE|Generic|Returns TRUE if the conditions for adding a new hire are met. Those conditions are: 1.) the EASD record is being split behind the scenes so the old effective date is the BOT, 2.) the new effective date is the same as the hire date, and 3.) the original hire date and hire date are the same.
|REHIRE|Generic|Returns TRUE if the conditions for adding a new hire are met. Those conditions are: 1.) the EASD record is being split behind the scenes so the old effective date is the BOT, 2.) the new effective date is the same as the hire date, and 3.) the original hire date and hire date are NOT the same.
|NEWHIRE|Generic|Returns TRUE if the conditions for adding a new hire are met. Those conditions are:\\ 1.) the EASD record is being split behind the scenes so the old effective date is the BOT,\\ 2.) the new effective date is the same as the hire date, and \\3.) the original hire date and hire date are the same.
|REHIRE|Generic|Returns TRUE if the conditions for adding a new hire are met. Those conditions are:\\ 1.) the EASD record is being split behind the scenes so the old effective date is the BOT,\\ 2.) the new effective date is the same as the hire date, and\\ 3.) the original hire date and hire date are NOT the same.
At line 23 changed 2 lines
|P2K_CF_RECSTAGE|Generic|Returns TRUE if the application is at the Stage Sequence for the Job Profile specified in the Global Variable RE_STAGE_SEQ. It will also set the Global Variable RE_STAGE_ID to hold the ID of the RST record for use in comparisons in the User Calc.
P2K_CF_RESCHEDASSESS Generic Creates an Assessment Event for any assessments tied to the steps within the current recruiting stage. The Assessment Date/Time will come from the Global Variable RE_ASSESSMENT or the current date if not specified here. IF this is triggered from an Update of the RAP then RAP_ID will be populated BUT if it is triggered on an Insert the RAP_ID can not be populated because the RAP record does not physically exist yet.
|P2K_CF_RECSTAGE|Generic|Returns TRUE if the application is at the Stage Sequence for the Job Profile specified in the Global Variable RE_STAGE_SEQ. It will also set the Global Variable RE_STAGE_ID to hold the ID of the RST record for use in comparisons in the UserCalc.
|P2K_CF_RESCHEDASSESS|Generic| Creates an Assessment Event for any assessments tied to the steps within the current recruiting stage. The Assessment Date/Time will come from the Global Variable RE_ASSESSMENT or the current date if not specified here. IF this is triggered from an Update of the RAP then RAP_ID will be populated BUT if it is triggered on an Insert the RAP_ID can not be populated because the RAP record does not physically exist yet.
At line 27 changed one line
P2K_CF_RE_ASSESS Generic IF candidate failed to get the minimum essential points on an Assessment their application is updated as rejected. For all other gradings their applications are moved up to the next Stage. A rejected application is set with a Status of 80 - Reject, a Reason of 01 - Below Essential Pts, a Rating of 07 - Rejected, and the stage is set to the highest on the Job Profile. A passed application is moved to the next stage sequence above the current stage with a Status of 30 - Pre-Screening and a Rating of 06 - Qualified.
|P2K_CF_RE_ASSESS| Generic| IF candidate failed to get the minimum essential points on an Assessment their application is updated as rejected. For all other gradings their applications are moved up to the next Stage. A rejected application is set with a Status of 80 - Reject, a Reason of 01 - Below Essential Pts, a Rating of 07 - Rejected, and the stage is set to the highest on the Job Profile. A passed application is moved to the next stage sequence above the current stage with a Status of 30 - Pre-Screening and a Rating of 06 - Qualified.
At line 30 changed one line
P2K_CF_HASAPPLIED Generic Returns TRUE if there is at least 1 Application tied to a Candidate. It will return FALSE if the Candidate has not yet applied to any postings.
|P2K_CF_HASAPPLIED| Generic| Returns TRUE if there is at least 1 Application tied to a Candidate. It will return FALSE if the Candidate has not yet applied to any postings.
At line 33 changed one line
P2K_CF_WFQLT_SAP Customer Specific
|P2K_CF_WFQLT_SAP| Customer Specific
At line 36 changed one line
P2K_CF_WFGES_CREATEAAL Customer Specific
|P2K_CF_WFGES_CREATEAAL| Customer Specific