This page (revision-23) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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
23 26-Nov-2021 10:22 31 KB Karen Parrott to previous
22 26-Nov-2021 10:22 31 KB kparrott to previous | to last
21 26-Nov-2021 10:22 31 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
APPROVALS AND AUTHORIZATIONS
APPROVALS AND AUTHORIZATIONS

Version management

Difference between version and

At line 6 changed one line
To outline functionality in the eP2k Professional and Self Service application approvals, using Approval Processes, Approval Steps, Approvers, Designated Approvers, and Approval Records.
To outline functionality in the Personality Admin and Self Service application approvals, using Approval Processes, Approval Steps, Approvers, Designated Approvers, and Approval Records.
At line 22 changed one line
**Approval notification / work flow
**Approval notification / workflow
At line 32 changed one line
Processes are defined in IDAP with a APPROVAL_PROCESS_CODE which is standard to all code fields in eP, a type of approval being defined using the APPROVAL_TYPE and a description.
Processes are defined in IDAP with a APPROVAL_PROCESS_CODE which is standard to all code fields in Personality, a type of approval being defined using the APPROVAL_TYPE and a description.
At line 40 added 2 lines
[Approvals_and_Authorization_01.jpg]
At line 44 added one line
[Approvals_and_Authorization_02.jpg]
At line 46 changed 9 lines
||Abbreviation||Stored Value
|Department Manager|01
|Position Manager|02
|Assignment Manager|03
|First Manager|04
|Specified Person|07
|Spec List Of People|08
|Last Approvers Manager|09
|All Managers|10
[{InsertPage page = 'X_APPROVER_TYPE'}]
At line 68 changed one line
%%information People lists that are generated through ep2k can only be used in this selection. These people lists use the "WHERE_CLAUSE" functionality as defined in [IMDAO]%%
%%information People lists that are generated through Personality can only be used in this selection. These people lists use the "WHERE_CLAUSE" functionality as defined in [IMDAO]%%
[Approvals_and_Authorization_03.jpg]
At line 73 changed one line
When an approval Entity becomes eligible for approval. "Notification approval records" are created. These are approval records with the approval status of "Ready To Be Approved". There is one record for each identity defined as an approver for the first step of approval. These record in conjunction with work flow can be used to notify approvers of pending approvals.
When an approval Entity becomes eligible for approval. "Notification approval records" are created. These are approval records with the approval status of "Ready To Be Approved". There is one record for each identity defined as an approver for the first step of approval. These record in conjunction with workflow can be used to notify approvers of pending approvals.
At line 77 added 2 lines
[Approvals_and_Authorization_04.jpg]
At line 87 changed one line
Designate approvers will have the start and end dates qualified based on the current server date.
[Approvals_and_Authorization_05.jpg]
[Approvals_and_Authorization_06.jpg]
\\
At line 95 added 4 lines
[Approvals_and_Authorization_07.jpg]
[Approvals_and_Authorization_08.jpg]
At line 92 changed one line
When responsibility is transferred from the approver to the designate for a replacement, all approval records previously created for notification are moved from the approver to the designate when the new designate record is saved. This will cause work flow, all approver screens and self service splash "to do" lists to now be full for the existing approvals previously required for the approver. Any new approvals required will create new approval records for the designate and the original approver will not be notified.
When responsibility is transferred from the approver to the designate for a replacement, all approval records previously created for notification are moved from the approver to the designate when the new designate record is saved. This will cause workflow, all approver screens and self service splash "to do" lists to now be full for the existing approvals previously required for the approver. Any new approvals required will create new approval records for the designate and the original approver will not be notified.
At line 113 added 2 lines
[Approvals_and_Authorization_09.jpg]
At line 112 changed one line
[Approvals_and_Authorization_10.jpg]\\
At line 132 changed one line
Approval screens include different types to define, view, maintain and approve. This is possible in both eP and Self service. Some of the main driving screens are listed below for eP. Self service has specific notation to the function name as WV???? and are located on several menus but generally in administrator or manager type roles.
Approval screens include different types to define, view, maintain and approve. This is possible in both Personality Admin and Self service. Some of the main driving screens are listed below for Personality. Self service has specific notation to the function name as WV???? and are located on several menus but generally in administrator or manager type roles.
At line 208 changed 21 lines
RE IRPOA Approve Postings Approval Bar
RE WARPO Maintain Postings Approval Bar
RE WRRAP View Applications By Posting Approval Bar
RE WRRMCA Maintain Candidate Profiles Approval Bar
SA ISPA Maintain Personnel Actions Approval Bar
SA ISPF Balance Pay for Performance Increases Action Button
SA ISRV Record Performance Reviews Approval Bar
SA MSSPA Dialog Action Button
SA WMSRV Review Employee Appraisals Approval Bar
SA WVSRV Approve Performance Appraisals Approval Bar
TS ITAPC Approve Clock Adjustments Approval Bar
TS WATAPC Authorize Punch Changes Approval Bar
TS WATTS Manage Time Sheets Action Button
TS WATTX Manage Time Collections Action Button
TS WMTAPC Authorize Punch Changes Approval Bar
TS WMTTS Review Time Sheets Action Button
TS WVTAPC Authorize Punch Changes Approval Bar
TS WVTSH Approve Employee Time and Exceptions Action Button
TS WVTTS Approve Time Sheets in Detail Action Button
TS WVTTSH View Time Sheet History Action Button
TS WVTTX Manage Time Collections Action Button
|RE|IRPOA|Approve Postings|Approval Bar
|RE|WARPO|Maintain Postings|Approval Bar
|RE|WRRAP|View Applications By Posting|Approval Bar
|RE|WRRMCA|Maintain Candidate Profiles|Approval Bar
|SA|ISPA|Maintain Personnel Actions|Approval Bar
|SA|ISPF|Balance Pay for Performance Increases|Action Button
|SA|ISRV|Record Performance Reviews|Approval Bar
|SA|MSSPA|Dialog|Action Button
|SA|WMSRV|Review Employee Appraisals|Approval Bar
|SA|WVSRV|Approve Performance Appraisals|Approval Bar
|TS|ITAPC|Approve Clock Adjustments|Approval Bar
|TS|WATAPC|Authorize Punch Changes|Approval Bar
|TS|WATTS|Manage Time Sheets|Action Button
|TS|WATTX|Manage Time Collections|Action Button
|TS|WMTAPC|Authorize Punch Changes|Approval Bar
|TS|WMTTS|Review Time Sheets|Action Button
|TS|WVTAPC|Authorize Punch Changes|Approval Bar
|TS|WVTSH|Approve Employee Time and Exceptions|Action Button
|TS|WVTTS|Approve Time Sheets in Detail|Action Button
|TS|WVTTSH|View Time Sheet History|Action Button
|TS|WVTTX|Manage Time Collections|Action Button
At line 230 changed 4 lines
STANDARD FUNCTIONALITY
Empty Approval Step
When an approval process has been initiated each step is displayed in the approval bar which is visible in certain approval screens. Approvers who qualify for approval by the where clause will be notified of a pending approval to be made. After such approval the next step is assessed for the current approvers. If the next step is lacking approvers from either an empty definition or the defined approver is disqualified via a where clause that empty step is ignored.
When a step is ignored it will not show in the approval bar or have approval notification records created. It will appear as if the approval process did not have that step defined. When the empty step is the last step in the process the last approval made will be considered final approval and the approval entity will be updated to the “approved” stage.
!!STANDARD FUNCTIONALITY
!Empty Approval Step
When an approval process has been initiated each step is displayed in the approval bar which is visible in certain approval screens. Approvers who qualify for approval by the where clause will be notified of a pending approval to be made. After such approval the next step is assessed for the current approvers. If the next step is lacking approvers from either an empty definition or the defined approver is disqualified via a where clause that empty step is ignored.
When a step is ignored it will not show in the approval bar or have approval notification records created. It will appear as if the approval process did not have that step defined. When the empty step is the last step in the process the last approval made will be considered final approval and the approval entity will be updated to the "approved" stage.
At line 235 changed 4 lines
Approval Process – Where clause = PEAS Personnel Actions only.
Step 1, Approver = Department Manager (no where clause)
Step 2 , Approver = HR personnel Specific person ( Where Clause – where wage Scale/Step is the last step sequence 3)
The assignment manager creates a new Personnel Action for a salary increase in PEAS for a salary increase to the next step. (2 of 3)
Approval Process - Where clause = PEAS Personnel Actions only.\\Step 1, Approver = Department Manager (no where clause)\\Step 2 , Approver = HR personnel Specific person ( Where Clause - where wage Scale/Step is the last step sequence 3)\\The assignment manager creates a new Personnel Action for a salary increase in PEAS for a salary increase to the next step. (2 of 3)
At line 247 changed one line
!Approver Options
Approvers may be defined with fours options. These options are "up to approval", "allow send back", "allow decline" and "allow change". Only applies to a second level of approval or higher. Once that level of approval is reached the approver will be notified of the pending approval. At that time the approver now has three possible actions to make.
At line 249 changed 3 lines
Approver Options
Approvers may be defined with fours options. These options are “up to approval”, “allow send back”, “allow decline” and “allow change”. Only applies to a second level of approval or higher. Once that level of approval is reached the approver will be notified of the pending approval. At that time the approver now has three possible actions to make.
;Up to Approval:When Up to Approval is checked that approver is eligible to approve entities which they qualify for via the where clause, including entities that are waiting approval on a step with a lower sequence. When up to approval is granted "notification records (approval records)" will be created with a status of "Approval In Progress" (Notification records are discussed further in Approval Notification /Workflow).
At line 253 changed 2 lines
Up to Approval
When Up to Approval is checked that approver is eligible to approve entities which they qualify for via the where clause, including entities that are waiting approval on a step with a lower sequence. When up to approval is granted “notification records (approval records)” will be created with a status of “Approval In Progress” (Notification records are discussed further in Approval Notification /Workflow).
;Allow Send Back:This setting applies to a second level of approval or higher. If at the time of approval the approver does not like what they see the option to send the entity back to the beginning of the approval process is available. This will set all previous step approvals (approval records) to have a status of "Approval Sent Back" which will cause the first step approvers to be notified (via new approval records) to once again approve the entity. Comments as to why the send back was made may be entered if necessary.
At line 256 changed 6 lines
Allow Send Back
This setting applies to a second level of approval or higher. If at the time of approval the approver does not like what they see the option to send the entity back to the beginning of the approval process is available. This will set all previous step approvals (approval records) to have a status of “Approval Sent Back” which will cause the first step approvers to be notified (via new approval records) to once again approve the entity. Comments as to why the send back was made may be entered if necessary.
This option is available in eP as an option in the right mouse click menu over the appropriate step on the approval bar.
This option is available in Personality as an option in the right mouse click menu over the appropriate step on the approval bar.
At line 263 changed 2 lines
Allow Decline
This setting allows the approver to decline the approval entity. The option is applicable to all steps the approver is responsible for. If a decline is made the approval process is complete, no further approval notification is necessary. This option is available in the right mouse click menu. Comments as to why the decline was made may be entered if necessary.
;Allow Decline:This setting allows the approver to decline the approval entity. The option is applicable to all steps the approver is responsible for. If a decline is made the approval process is complete, no further approval notification is necessary. This option is available in the right mouse click menu. Comments as to why the decline was made may be entered if necessary.
At line 266 changed 3 lines
Allow Change
This setting will cause the approval entity to be editable or not during the approval. In cases where the approver is allowed to view only while making the approval.
;Allow Change:This setting will cause the approval entity to be editable or not during the approval. In cases where the approver is allowed to view only while making the approval.
At line 275 changed one line
Once an approval entity has entered the approval stage (explained below) of "Stage_WaitingApproval" CRUD will be controlled to the appropriate approver. This means that only approvers who have rights to approve on the current step with "allow change" rights will be able to edit the information displayed.
Once an approval entity has entered the approval stage (explained below) of "Stage_WaitingApproval" CRUD will be controlled to the appropriate approver. This means that only approvers who have rights to approve on the current step with "allow change" rights will be able to edit the information displayed.
At line 277 changed 2 lines
Approver Derivation
Department Manager - Used for approval entities which are employee based and is the person who manages the department for that employee. Example. If approving a time sheet; the person who manages the department in which the owner of the time sheet works will be the approver. This person is derive by first looking if a specific person has been defined as the manager in IDDP. This is defined by a specifying a person or a supervisory position.
!Approver Derivation
;Department Manager:Used for approval entities which are employee based and is the person who manages the department for that employee. Example. If approving a time sheet; the person who manages the department in which the owner of the time sheet works will be the approver. This person is derive by first looking if a specific person has been defined as the manager in IDDP. This is defined by a specifying a person or a supervisory position.
At line 283 changed one line
Position Manager - Used for approval entities which are employee based and is the person who manages the position for that employee. Example: If approving a time sheet; the person who manages the position in which the owner of the time sheets works will be the approver. This is defined by specifying a person or another position which manages it.
;Position Manager:Used for approval entities which are employee based and is the person who manages the position for that employee. Example: If approving a time sheet; the person who manages the position in which the owner of the time sheets works will be the approver. This is defined by specifying a person or another position which manages it.
At line 285 changed one line
When a specific person is not defined then the first active incumbent found in the Reports to position will be set as the manager.
When a specific person is not defined then the first active incumbent found in the Reports to position will be set as the manager.
At line 287 changed 2 lines
If no active employee is found in that position the manager of that position will be found in the same manner until a position is found where it is not reporting to another position.
Assignment Manager - Used for approval entities which are employee based and is the person who is defined as the manager for that employee on their current assignment details (IEAS).
If no active employee is found in that position the manager of that position will be found in the same manner until a position is found where it is not reporting to another position.
;Assignment Manager:Used for approval entities which are employee based and is the person who is defined as the manager for that employee on their current assignment details (IEAS).
At line 290 changed 6 lines
First Manager - Used for approval entities which are employee based and is the first manager found defined in a pecking order of assignment manager, position manager and finally department manager for that employee. If no assignment manager is found then the manager of the position will be searched, if no active employee is found then the manager of the department is searched. The logic for each is described above. Only the first employee found in this order will be used.
Specified Person - Used for all approval entities, employee based or not. This allows an approval administrator to set a specific employee as an approver.
Specific List of People - Used for all approval entities, employee based or not. This allows an approval administrator to set specific people as an approver. This list of people is defined in IMPL and must be an eP people list (p2k people lists are not supported.)
Last Approvers Manager - Used for all approval entities, employee based or not. This approver type is not intended to initiate an approval process(any approver on step 1). There must be at least 1 approval made on a previous step and only applies if the previous step was approved and not declined or sent back. This type uses the logic in "First Manager" as described above.
All Managers - Used for approval entities which are employee based. This will set each manager found as an approver. The first manager defined on the assignment, position and department will have approval notification record created.
All manager type approvers are searched for based on a date in context to the approval entity. This will be the date used to search date sensitive details.
;First Manager:Used for approval entities which are employee based and is the first manager found defined in a pecking order of assignment manager, position manager and finally department manager for that employee. If no assignment manager is found then the manager of the position will be searched, if no active employee is found then the manager of the department is searched. The logic for each is described above. Only the first employee found in this order will be used.
At line 297 changed 3 lines
Approval Stages
Approval Entities are managed by stages. Simplified for example - “before”, “during” and “after”. Each stage is mapped for each approval entity. This enables each entity to manage them selves to their specific business status descriptions. These are lexicon columns on the entity which describe their status or authorization requirements. The personnel actions mapping is given as an example below. For this example the “before” is stage_WorkInProcess, “during” is Stage_WaitingApproval and “after” is either “Stage_approved”, “Stage_Not_approved” or “Stage_Cancelled”
Personnel Actions – PA Status mappings translating from pa_status to approval stage.
;Specified Person:Used for all approval entities, employee based or not. This allows an approval administrator to set a specific employee as an approver.
;Specific List of People:Used for all approval entities, employee based or not. This allows an approval administrator to set specific people as an approver. This list of people is defined in IMPL and must be an Personality people list.
;Last Approvers Manager:Used for all approval entities, employee based or not. This approver type is not intended to initiate an approval process(any approver on step 1). There must be at least 1 approval made on a previous step and only applies if the previous step was approved and not declined or sent back. This type uses the logic in "First Manager" as described above.
;All Managers:Used for approval entities which are employee based. This will set each manager found as an approver. The first manager defined on the assignment, position and department will have approval notification record created.
All manager type approvers are searched for based on a date in context to the approval entity. This will be the date used to search date sensitive details.
!Approval Stages
Approval Entities are managed by stages. Simplified for example - "before", "during" and "after". Each stage is mapped for each approval entity. This enables each entity to manage them selves to their specific business status descriptions. These are lexicon columns on the entity which describe their status or authorization requirements. The personnel actions mapping is given as an example below. For this example the "before" is stage_WorkInProcess, "during" is Stage_WaitingApproval and "after" is either "Stage_approved", "Stage_Not_approved" or "Stage_Cancelled".
Personnel Actions - PA Status mappings translating from pa_status to approval stage.
At line 301 changed 14 lines
In Progress Stage_WaitingApproval
Submitted Stage_WaitingApproval
Failed Update Stage_Approved
Approved Stage_Approved
Completed Stage_Approved
Not Approved Stage_Not_Approved
Tracked Copy Stage_Cancelled
Cancelled Stage_Cancelled
Personnel Actions – PA Status mappings translating from approval stage to pa_status
Stage_WorkInProcess Pending
Stage_Not_Approved Not Approved
Stage_Cancelled Cancelled
Stage_WaitingApproval In Progress
Stage_Approved Approved
|In Progress|Stage_WaitingApproval
|Submitted|Stage_WaitingApproval
|Failed Update|Stage_Approved
|Approved|Stage_Approved
|Completed|Stage_Approved
|Not Approved|Stage_Not_Approved
|Tracked Copy|Stage_Cancelled
|Cancelled|Stage_Cancelled
At line 316 changed 13 lines
Approval Records
Each stage dictates what approval records are created. The Approval records are what is used to create a visual (approval bar) or report ( discoverer) to show where and who the approval sits, whether it`s before during or after the approval.
The current supported approval record statuses are:
Approval Cancelled
Future Approval
Ready To Be Approved
Approval In Progress
Approved
Sent Back
Approved Sent Back
Approved Historic
Declined
Declined Historic
Personnel Actions - PA Status mappings translating from approval stage to pa_status
|Stage_WorkInProcess|Pending
|Stage_Not_Approved|Not Approved
|Stage_Cancelled|Cancelled
|Stage_WaitingApproval|In Progress
|Stage_Approved|Approved
!Approval Records
Each stage dictates what approval records are created. The Approval records are what is used to create a visual (approval bar) or report ( discoverer) to show where and who the approval sits, whether it`s before during or after the approval.
The current supported approval record statuses are:
*Approval Cancelled
*Future Approval
*Ready To Be Approved
*Approval In Progress
*Approved
*Sent Back
*Approved Sent Back
*Approved Historic
*Declined
*Declined Historic
At line 330 changed 2 lines
Approval Cancelled - used when an entity is cancelled or deleted. All existing approval records will receive this status. (explained in a following section)
Future Approval - used for up and coming approvals to be made for an approver who do not have upto approval. Approval Stages which cause this are Stage_WorkInProcess or Stage_WaitingApproval. For the Stage_WorkInProcess future Approvals are optional and can be controlled but a site preference defined in IMST. Each table where approvers need as much time a possible before the actual approval is required may be defined. in the example screen shot below. Future approval records will be created when either a Time sheet or Personnel Action is set to a WIP status. Example: This may be helpful for managers with employees that have time sheets which have not been submitted for approval.
;Approval Cancelled:used when an entity is cancelled or deleted. All existing approval records will receive this status. (explained in a following section)
;Future Approval:used for up and coming approvals to be made for an approver who do not have upto approval. Approval Stages which cause this are Stage_WorkInProcess or Stage_WaitingApproval. For the Stage_WorkInProcess future Approvals are optional and can be controlled but a site preference defined in IMST. Each table where approvers need as much time a possible before the actual approval is required may be defined. in the example screen shot below. Future approval records will be created when either a Time sheet or Personnel Action is set to a WIP status. Example: This may be helpful for managers with employees that have time sheets which have not been submitted for approval.
At line 334 changed 9 lines
Ready To Be Approved - used for approvers which are required to make approval decisions.
Approval In Progress - used to show approvers with `Up To approval` that there is an approval in progress which they can make an up to approval on.
Approved - used to show a positive approval
Sent Back - used to show the approval process has been requested to start over.
Approved Sent Back - used to show a lower step positive approval has been send back to be re-done.
Approval Historic - used to show and entity has had a positive approval but is no longer needed either through a cancel or deletion.
Declined - used to show a negative approval.
Declined Historic - used to show a negative approval was made and is no longer needed either though a cancel or deletion.
Maintenance of approval records is accomplished in three ways. The first is automatically by the system when an existing IDAP definition pre-exists to an approval process starting and does not change during the approval. Secondly a manual button is on IDAP to update records if the approval process has been updated in any way with approvals in progress.
;Ready To Be Approved:used for approvers which are required to make approval decisions.
;Approval In Progress:used to show approvers with `Up To approval` that there is an approval in progress which they can make an up to approval on.
;Approved:used to show a positive approval
;Sent Back:used to show the approval process has been requested to start over.
;Approved Sent Back:used to show a lower step positive approval has been send back to be re-done.
;Approval Historic:used to show and entity has had a positive approval but is no longer needed either through a cancel or deletion.
;Declined:used to show a negative approval.
;Declined Historic:used to show a negative approval was made and is no longer needed either though a cancel or deletion.
Maintenance of approval records is accomplished in three ways. The first is automatically by the system when an existing IDAP definition pre-exists to an approval process starting and does not change during the approval. Secondly a manual button is on IDAP to update records if the approval process has been updated in any way with approvals in progress.
At line 344 changed one line
The third is to run an update process UDAP. This process is suggested to be scheduled daily to allow start and end dates to be respected in IDAP processes or approvers, where clauses or designate approvers.
The third is to run an update process UDAP. This process is suggested to be scheduled daily to allow start and end dates to be respected in IDAP processes or approvers, where clauses or designate approvers.
At line 358 added 2 lines
!Final Approval
Is a term used to describe any approval process that is in progress which has an approval made where it is deemed the last approval required for the process. This is possible for example in cases of missing approvers or an approval on the last step. Once final approval is made, the approval entity is updated to the "approved" stage
At line 347 changed 5 lines
Final Approval
Is a term used to describe any approval process that is in progress which has an approval made where it is deemed the last approval required for the process. This is possible for example in cases of missing approvers or an approval on the last step. Once final approval is made, the approval entity is updated to the “approved” stage
Approval Work Flow Notification
Approval Records are used in several ways to compliment the approval system. One of the usages is Work Flow. Work flow is provided on the table p2k_cm_approval_records. This enhances approvals by adding all standard features of work flow such as emails, user calcs and in turn procedures.
The term “Notification records” has been used to describe the records created to “notify” an approver, say for example an assignment manager of a pending approval via email using work flow. If on step one an approver is required to make an approval. Once the approval entities stage is set to Stage_waiting_approval, an approval record or notification record is created. This record has a status of “Ready to be Approved” as defined in the lexicon X_APPROVAL_STATUS. Up to Approvers also get a notification record with the status of “Approval In Progress”
!Approval Workflow Notification
Approval Records are used in several ways to compliment the approval system. One of the usages is Workflow. Workflow is provided on the table p2k_cm_approval_records. This enhances approvals by adding all standard features of workflow such as emails, user calcs and in turn procedures.
The term "Notification records" has been used to describe the records created to "notify" an approver, say for example an assignment manager of a pending approval via email using workflow. If on step one an approver is required to make an approval. Once the approval entities stage is set to Stage_waiting_approval, an approval record or notification record is created. This record has a status of "Ready to be Approved" as defined in the lexicon X_APPROVAL_STATUS. Up to Approvers also get a notification record with the status of "Approval In Progress".
At line 354 changed 3 lines
Approval Deletion or Cancellation
Since approval records are used in a few ways to notify approver of pending approvals like screens (SS) and work flow, approval records are maintained in cases where the approval entity is deleted or cancelled. The approval record status is updated to cancelled and will have a comment made if deleted.
!Approval Deletion or Cancellation
Since approval records are used in a few ways to notify approver of pending approvals like screens (SS) and workflow, approval records are maintained in cases where the approval entity is deleted or cancelled. The approval record status is updated to cancelled and will have a comment made if deleted.
At line 362 changed 4 lines
Generic Approvals
It is not necessary to always define an approval processes. When simply a sanity check of the data is required and anyone or everyone is required to review the data on the approval entity before it moves to the next status value, generic approvals may be used.
If an approval entity is moved to the approval stage “Stage_WaitingApproval” and there has not been an approval process defined a generic 1 step approval bar will be displayed. Any user with access to the function and data may approve this type of approval. No approval records are ever created. The status of the approval entity is simply updated to the next stage upon approval.
A generic approval would be displayed as below with the right mouse click menu:
!Generic Approvals
It is not necessary to always define an approval processes. When simply a sanity check of the data is required and anyone or everyone is required to review the data on the approval entity before it moves to the next status value, generic approvals may be used.
If an approval entity is moved to the approval stage "Stage_WaitingApproval" and there has not been an approval process defined a generic 1 step approval bar will be displayed. Any user with access to the function and data may approve this type of approval. No approval records are ever created. The status of the approval entity is simply updated to the next stage upon approval.
A generic approval would be displayed as below with the right mouse click menu:
At line 381 added 2 lines
!Find Block Approval Toggles (Obsolete)
This section has been replaced with the site preference described below available in 4.09
At line 368 changed 3 lines
Find Block Approval Toggles (Obsolete)
This section has been replaced with the site preference described below available in 4.09
Two self service screens listed below have a toggle available for use located in the find block of each function. This toggle enables the data listed in the find block to change dynamically to show “potential” approvals verses “actual” approvals.
Two self service screens listed below have a toggle available for use located in the find block of each function. This toggle enables the data listed in the find block to change dynamically to show "potential" approvals verses "actual" approvals.
At line 372 changed 3 lines
WVDATS Approve Time
WVTSH Approve Employee Time and Exceptions
It is highly recommended that properly built where clauses are used on both the approval process and approver levels. If the refining of approval processes and approvers is not properly done performance will be an issue. Consultants would be a good source to help ensure that all filtering is done properly to avoid any performance problems. Below is an example of too many rows for an approver to manage.
WVDATS - Approve Time
WVTSH - Approve Employee Time and Exceptions
It is highly recommended that properly built where clauses are used on both the approval process and approver levels. If the refining of approval processes and approvers is not properly done performance will be an issue. Consultants would be a good source to help ensure that all filtering is done properly to avoid any performance problems. Below is an example of too many rows for an approver to manage.
At line 391 added one line
!Site Preferences (New as of 4.09)
At line 377 changed 4 lines
Site Preferences (New as of 4.09)
The site preference APPROVAL_WIP_REC now replaces the old simulation logic applied when trying to find the possible approvals an approver may need to make. This logic gives more of an accurate view of the up and coming approvals by monitoring specific tables defined by this preference.
The site preference APPROVAL_WIP_REC now replaces the old simulation logic applied when trying to find the possible approvals an approver may need to make. This logic gives more of an accurate view of the up and coming approvals by monitoring specific tables defined by this preference.
At line 384 removed 3 lines
At line 400 added one line
This page (revision-23) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop