APM 2022.30.0.45 EAR
APM 2022.30.0.45 Early Access Release 2022.31.3 EAR
Please follow the link below to read more about EAR
Click here to read more about our different types of releases (main release, intermediate release)
Resolved Jira Issues
APM 2022.31.3 EAR (2022.30.0.45)
APM-6493 | Activity data group Confirm functionality did not update the rotation shift linked to the activity being updated. | The Confirm current activity functionality in the Activity Datagroup did not update the linked rotation shift. In this patch, we fixed this problem. When confirming the current activity, the system updates the rotation shift accordingly with the new sign-off date. |
APM-6540 | Activities’ evaluation was performed wrong when sick activity was generated and inserted in the middle of current sea-service | Fixed |
APM 2022.31.2 EAR (2022.30.0.28)
APM-6492 | Payroll fields for contract datagroup don't work in payroll scripts | Fields for various datagroup values returned only 0 in payroll scripts. |
APM 2022.31.1 EAR (2022.30.0.14)
APM-6434 | Seniority counter general code | A new general code Seniority Counter is created under the Payroll section. It provides a user the possibility to set up rules for Seniority calculation when Contracts datagroup is in use. |
APM-6419 | Payscale Table by Payscale code or Rank | Creation of a new contract is improved with the automatic assignment of a payscale, based on his Rank linked under Payscales > Payscale Code > Ranks. If there are several possible assignments, datagroup will offer you the full list for selection |
APM-6417 | Contract Datagroup needs the possibility to copy information from previous contracts (if exist), (by default the last contract) | When creating a new contract it is now possible to copy details from any of the previous contracts, also defining what data you’d like to be copied. |
APM-6416 | Functionality to select columns in contract overview (contract tree) | We added the possibility to customize the appearance of the fields that exist in the datagroup details. Unnecessary fields can now be easily set as non-visible by setting the checkbox flag to OFF. You can switch them back to ON when necessary. This is user-related personalization, so your setup will not affect other users of the datagroup. |
Other Versions