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

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
4 26-Nov-2021 10:22 1 KB khiggs to previous
3 26-Nov-2021 10:22 1 KB rforbes to previous | to last
2 26-Nov-2021 10:22 658 bytes jmyers to previous | to last
1 26-Nov-2021 10:22 445 bytes jmyers to last

Page References

Incoming links Outgoing links
AUTO_APPROVAL(System_Preference)
AUTO_APPROVAL(System_Preference)

Version management

Difference between version and

At line 11 added 8 lines
When an Approval Entity is set to the approval step of ‘Waiting Approval’, the approval engines will search for an appropriate IDAP definition. For cases where there is either no pre-defined approval process qualified to be used or no approval process has been defined for the entity, a ‘Generic Approval’ will be required.
With the AUTO_APPROVAL preference, no ‘Generic Approval’ would be required. If either there are NO pre-defined approval processes or no defined approval process qualifies by priority and process level Where Clause, the approval entity is advanced directly to the ‘Approved’ approval step.
__Exceptions to the Preference Logic__
The AUTO_APPROVAL preference is applied to all Approval entities. The Approval entity time sheets have a specific logic located within the ‘Submit’ action buttons on the functions listed below.
The Submit action will assess whether the user has been defined as an approver. If the user is an approver, the time sheet will be automatically given approval. If the user is ‘Final Approver’, the time sheet will advance to ‘Approved’ status. If the user is not the ‘Final Approver’, the time sheet will remaining in waiting for further approval.
This page (revision-4) was last changed on 26-Nov-2021 10:22 by khiggsTop