Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Version History
Version 1
Next »
Patch 2020.50.2
10th December
| APM-4039 | Added the restriction if the onboard user modified a shift the remaining shifts are modified. | It is now possible to define that a Rotation Plan can only be maintained on the main site, when several replication sites are used. If a plan is set with this option, no shift modifications can be performed if a user logs in from a Satellite site, not from the Main one (Host).
- Use Maintained By Main Site ribbon menu (proper access should be set for a user for routine 370 in Adonis Control Centre)
- Check if a plan can be maintained by main site only from the corresponding grid column
| Actions |
| APM-4543 | New payroll field calculating total weekend and holiday in a payroll period. | Added payroll field L93t to return the number of weekend days + holidays in the payroll period. The days are calculated based on the calendar linked to the persons payscale if no link exists the calender in the person's client (organization) will be used. | Actions |
| APM-4611 | Cannot transfer imesheet to payrol with property 'IsPublicHoliday' | Issue found & fixed during int.testing for proper interaction with new APP method's property | Actions |
| APM-4600 | APM-4596 Payscale code is not fetched to the autogenerated entrie | Fixed issue that auto-generated entries were created with empty payscale if target activity didn’t have them assigned. Now Personal Details settings are used | Actions |
| APM-4601 | APM-4588 Error when processing timesheets to payroll | Memory error when processing a timesheet and grid is refreshed | Actions |
| APM-4568 | APM-4561 Entry Codes generated regardless of the limitation in the setup in Payscales | Fixed situation when Payscale Table/Code are empty in activity, but payments were generated despite the limitation in the setup for auto-generation in |
