It is no more possible to add a planned activity if the current activity with later dates exist

It was possible to create overlapping sea-service activities when confirming Promotion & module is set with Global Option Promotion Starts at ETA set

When modifying shift start date & sea-service activity was updated, it could result in modification of Date To of another non-seaservice activity that was changed from current to historical. As the result, even 1-day Travel activity could be extended as if lasting for the long period.

Provided possibility to trace down how a competence record was created and/or modified, introducing database fields CreatedByModule and UpdatedByModule. Corresponding values are used for various sources:

• Competence & Basket datagroups - 5002
• Course Scheduler module - 500380
• Crew list -> Common Entry - 5000
• Tools ->Import Competences - 5003

We now provide validation of Estonian personal ID number according to government standards. The user will be notified if ID doesn’t meet the requirements. Note that Check Person ID Validity must be set under User Options

We allowed activities of Vacation type to be selected as Extra Activity In Between when performing shift sign off operation

When modifying a shift with option Move Subsequent Shifts for shifts with Onboard/Leave activities definition – Leave activities might be deleted with new dates of Onboard due to move.

Promotion link was not drawn on Gantt if the promotion date was shifted. A warning message was referring to a Crew Change date even if Crew Change modules was not used

Moving start date of Promoted To shift backward resulted in 1-day activity overlap like for vessel transfer, although promotion was performed on the same vessel

Travel activity which was extra as per shift definition was not deleted on satellite although deleted on host when removing a person from shift & replication performed.

Before Delete trigger on activities table PW001P03 is split into two separate triggers for proper replication processing:

BD_PW001P03 - a standard autogenerated trigger for replication

BDX_PW001P03 - trigger containing enhanced logic for activity handling

Stack Overflow when adding Disembarkation reason & confirming Sign Off.

Documents that were expired were not displayed upon Documents Expiry check applied in Rotation Planning or Crew Change module. It only occurred if a position had the 2^nd^ level of Required Documents defined in Organization Structure & the requirements were satisfied

SQL error when trying to re-schedule a crewmember that has already been refused to re-schedule on the previous stage

Shifts’ promotion link was lost when moving PromotedTo shift EED and no calling port exists for PromotedTo shift start date

Performing Promotion with new payscale settings resulted in the generation of the new activity with 0 leave days value, although Leave Factor was set for selected payscale

For replication purposes of Crew Station Bill safety levels we provided modifications as below:

• Unique Index IDX_MRLS_SAFETY_LVL_SEQ (MRLS_SAFETY_LEVELS table) - removed
• Foreign Key FK_VRPREQDOC_LVLQTYSL (VRP_REQ_DOCUMENT_LVLQTY table) - removed.
• Foreign Key FK_VRPREQDOC_SL (VRP_REQ_DOCUMENT table) - removed

When replication existed between several sites & CrewID was relinked from one station to another – duplicate records appeared on satellite

List of crewmembers suitable for Preferred Assignment was collected with wrong persons who had never had current or historical sea-service activity at a selected vessel

Module’s Global settings disappeared after upgrade

Terminal value was not shown in segments grid, although existed in booking details

When a person was terminated, his Bio was not sent as an update to Seagull. As the result, he appeared as Active on the interface side

We added field P508 SSS No to the list of fields that can be defined as mandatory under Organization structure > Company > Mandatory Fields > Person > Payroll > Constants for more transparency, as earlier PH nationality was requesting this field as mandatory by default. We also hid this field for persons with a nationality other than PH under Personal Details

Dialog field Termin is set to be mandatory for input when preparing Pensjonstrygden report for Norwegian authorities

Payroll Fields L93, L93a, L22h are improved so that the values are calculated based on Holidays setup for a person’s corresponding Payscale Code. If none then the calculation will be performed based on the General Code setup

Fixed routines Vessel Project & Vessel Location to have numbers 817 and 819 respectively to provide proper access handling

List of Vessel Projects / Vessel Locations was not filtered as per Open Client vessel. It was also possible to create records with vessels different that the open one

Organization access rights were not copied properly

It was possible to perform changes on the Flags tab although access was set to Read in Adonis Control Centre

Start Page module’s icons were not displayed in the Azure environment

If Name Mask definition was modified in Global Options, only the newly created persons were displayed with the newly applied mask. Those existing were shown using the old Name Mask

AV when trying to re-set user’s account settings to the default ones

For Griffin Marine interface the filter From Vessel / To Vessel was not applicable for existing bookings

Fixed error with competences import

As Adonis Personnel Manager has own technical requirements as for the database compatibility version, that must be met, we improved installation/upgrade set to define the proper value if database access allows. If not, a corresponding warning will be shown & upgrade process will be terminated

We enabled the field "Vessel Name" to be displayed in the grid. List will be limited by Open Client if it is a vessel, displaying the entire list of records if not a vessel

Before Delete triggers were updated to avoid failure if values included single quotation marks being a part of the primary key