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

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

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
61 26-Nov-2021 10:22 5 KB kparrott to previous

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 42 added 9 lines
New changes with the 4.09.00 release include the following:
*New abilities to update outstanding approval records for approval processes
**A new [Maintain Approval Records|ACT_MAINTAIN_RECORDS] button has been added to [IDAP]. This button allows the user to update any outstanding approval records with any changes that may have been made to the approval process. If the approval process has been changed in any way this button __should__ be pressed.
**A new function called [UDAP] has been created to update outstanding approval records. This function has the same logic as the [Maintain Approval Records|ACT_MAINTAIN_RECORDS] button in [IDAP], it is just in a report update format. The [UDAP] should be scheduled to run every day (preferably early in the morning i.e between midnight and 7am) to ensure that any changes made to approval processes and designated approvers will be picked up and applied to any outstanding approval records.
*Start and End dates are now properly respected. A Process may have a “Start” and “End’ date where it will be considered to be “effective”. If the current approval entity’s AS_OF_DATE falls either between dates if both given, after the start if the end date is not provided or before the end date if the start date is not provided.
*A new [Approval Status|X_APPROVAL_STATUS] has been added called Future Approval. There are 2 types of Future Approvals.
**One is for records in a stage ‘Waiting Approval’, where the record has already entered an approval process and whose approver does not have [UpTo approval|UP_TO_APPROVAL].
**The second type is to indicate any items (ie: PAs or TS) that ‘may’ enter an approval process, such as new unsubmitted time sheets or pending PAs. This type of Future Approval is optional and is controlled by the site preference [APPROVAL_WIP_REC] defined in [IMST]. Each table where approvers may need to see what they ‘may’ have to approve in the near future may be defined. For example a client may define PTS and SPA as preference values.