Articles in this section

V36.9.0 | Compas Maintenance | Release Notes

🚀What's New in Version 36.9.0?

We are pleased to announce Compas Maintenance Version 36.9.0. This includes a series of enhancements and bug fixes aimed at improving efficacy and functionality.

Disclaimer:

  • All the developments and fixes detailed in the release notes are implemented across all customer environments. However, depending on your company's settings and permissions, certain features may not be accessible or relevant.
  • If new features and tables are introduced for onboard applications, they may be exclusive to the onboard cloud.

🎉Enhancements and New Features

[COMPAS CLOUD (OFFICE)] [NAMES OF NOMINEES NOW VISIBLE IN VISUAL PLANNER]

  • The ability to see the name of the nominees in the visual planner without having to click on the line has been added.
  • When the Show tool tip functionality is enabled (selected as yes), the nominee details appear. See below for examples.

Examples:

0 Nominees: This field shows as it is.

Picture1.png

1 Nominee: This field shows the nominee’s name with the details based on setting (regardless of whether the tooltip is enabled or disabled).

Picture2.png

More than 1: This field shows the nominees and the tool tip (if the option is enabled in the setting). This means it shows the nominee details one by one, along with the setting selected to display more information.

Picture3.png

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. In the top right-hand corner, click the Vessel dropdown menu and select an item.
  3. Click the Visual Planner tab.
  4. Click Settings.
  5. Click the grey box next to Show tooltip (to add a check in the box and enable).
  6. Click Apply.
  7. Hover your cursor over the relevant entry on a line.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)/CSS/ONBOARD] [DANISH PAYSLIP TO APPEAR BASED ON PARAMETER RATHER THAN TAX REGIME]

  • Currently, the Danish payslip appears if the tax regimen is Danish.
  • A parameter-based display has been added.
    • The parameter being ‘Display Danish Payslip’ with default value 'Y' and possible values Y / N.
    • If ‘Y’, the payslip format is displayed for those with a Danish tax regimen.
    • If ‘N’, the payslip format is not displayed for those with a Danish tax regimen.
  • This update has been applied to Compas Office, Compas CSS, and Compas Onboard.

Reproduction steps:

Compas Office

PART 1

  1. Log into COMPAS Cloud (Office).
  2. In the top right-hand corner, enter the crew ID into the Crew: search bar and click the green arrow.
  3. Click the Personal tab.
  4. Click the Additional Information column.
  5. In the Additional Information column, click the Picture4.png edit icon to edit.
  6. In the Tax regime: dropdown menu, select Danish.
  7. Click Update.

PART 2

  1. Log into COMPAS Cloud (Office).
  2. Click on the Payroll dropdown menu.
  3. Click on the Payroll overview menu item.
  4. On the required vessel, click the Picture5.png View Payroll icon of the configured crew.
  5. Click Close Payroll.
  6. Click OK.

Compas CSS

  1. Log into COMPAS CSS.
  2. In the lefthand menu, click Payroll.
  3. Click the Payroll column.

Compas Onboard

  1. Log into COMPAS Onboard.
  2. Click on the Crew dropdown menu.
  3. Click the Crew list menu item.
  4. Click the relevant Code.
  5. Click on the Payroll tab.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [PERFORMANCE IMPROVEMENTS APPLIED TO PAYROLLCALCULATOR.CS]

  • On certain executions, part of the SQL with the PayrollCalculator.cs can fluctuate between 1 and 12 seconds (depending on the data being processed).
  • Code changes have been applied to improve the performance.

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. Click on the Payroll dropdown menu.
  3. Click on the Payroll overview menu item.
  4. Verify the performance of end-to-end flow of Payroll overview module before and after code changes. In particular:
    1. The page should not have any noticeable delays when loading.
    2. The number of records should be the same before and after the changes.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [ADD HIRED BY FIELD AS ENDPOINT IN PROCESS/GENERIC/PAYROLLJOURNALPOSTING]

  • Using the same code, the ability to send the Compas supplier code for an employer to an ERP system (without having to do a mapping between Compas databaseid and erp system) has been added.

Preconditions:

  1. Open Postman and run API endpoint. Send API endpoint: Process/generic/payrolljournalposting.
  2. Check API result Crew details new fields.
  3. Check added field Hire by data.
  4. Check added field Supplier Code.
  5. Check API result for Crew new fields with No hired by.

Reproduction steps:

Contract Detail: Hired by

  1. Log into COMPAS Cloud (Office).
  2. In the top right-hand corner, enter the crew ID into the Crew: search bar and click the green arrow.
  3. Click the Services tab.
  4. Click the Contracts column heading.
  5. Click the pen Edit icon.

The Hired by field is populated.

Company Details: Supplier Code

  1. Log into COMPAS Cloud (Office).
  2. Click on the Admin dropdown menu.
  3. Click on the Admin panel menu item.
  4. Under the General heading, click Providers Configuration.
  5. On the relevant entry, click on the View Details icon.
  6. In the Providers detail table, see Supplier Code.

The Supplier Code field is populated.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [ENHANCEMENTS MADE TO PAYROLL]

  • The ability to bring all earnings for calculated payrolls has been added.
  • To generate the earnings report, users will have click on the green dollar icon for each vessel/payroll group to compute the payroll manually.
  • When selecting the earnings report, a default checkbox appears which is for “Closed payroll” only, along with another unchecked checkbox for “Calculated payroll”.
    • This means users have the flexibility to select either one or both at the same time but cannot progress with both options unchecked.
  • In the Excel file, a column titled “Payroll Group” has been added.
    • This column can be blank if the crew member does not have this payroll group value updated.
  • The payroll closed on a non-payable movement is also included.
    • This means they have no payroll and will not show in the payroll overview.
    • However, there are some unprocessed paid elements that are pushed to processing. This action triggers crew to have payroll in the respective month.

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. Click on the Payroll dropdown menu.
  3. Click on the Reports dropdown menu.
  4. Click on the Monthly reports menu item.
  5. Enter any relevant search terms. (This includes the newly added fields such as Manning Office, Closed Payroll, Calculated Payroll.)
  6. Click Submit.
  7. Click the XLS file to open.
  8. Search for the Payroll Group column.

-------------------------------------------------------------------------------------------------------------------

[COMPAS ONBOARD] [TIMEOUT PAYROLL_MAIN TO CREW_MOVEMENT FIX]

  • Improvements have been made to support payroll associated with crew movements.
  • Specifically, a periodic query sometimes runs quickly causing a timeout error. Depending on the parameters specified, the query can take 20 seconds plus, which in a wider transaction, causes a timeout.

Reproduction steps:

  1. Log into COMPAS Onboard.
  2. Click on the Payroll dropdown menu.
  3. Click the Payroll overview menu item.
  4. Apply the relevant filters (select Month and Year from the dropdown menus).
  5. Click Generate.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [INTERTANKO ATTRITION REPORT]

  • In the Intertanko report, (column S), the total number of terminations appear correctly, however, when clicking the total number, an incorrect number of names appear.
  • To accommodate this, a new library configuration type titled ‘RESG’ (required migration script) has been added.
    • The library description Termination Status has been added.
  • Users are required to define the status that should be considered as Termination Status. This requires the status code to be configured under Termination Status correctly (see below image).Picture6.png
  • When crew (with a movement added) is associated with a status defined in this new library, it will be counted as “No. of Termination” in the S column (in the report).

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. Click on the Crew dropdown menu.
  3. Click on the Headcount analysis dropdown menu.
  4. Click on the Attrition reports dropdown menu.
  5. Click on the Attrition reports menu item.
  6. Apply relevant filters and from the Report dropdown menu, select Intertanko Attrition.
  7. Click Submit.
  8. Click the white box next to Show ratings (to add a check in the box). The records appear.
  9. To test this:
    1. Choose 2-3 ranks to test such as Master Rank, Chief Officer Rank, and Chief Engineer Rank.
    2. Click on the S column for each rank.
    3. Verify the Movement column is available with the status defined in the new library (Termination Status).
    4. Verify the total number of terminations in the drill down list matches the total count in column S.

-------------------------------------------------------------------------------------------------------------------

[COMPAS ONBOARD] [CABIN ALLOCATION ENHANCEMENTS]

  • In Compas Onboard, the following enhancements have been made to the Cabin Allocation screen.
  • Enhancement 1:
    • Breadcrumb trail: Cabin Allocation screen
    • The CID has been included in the cabin allocations ribbon for all crew with cabin assigned.
  • Enhancement 2:
    • Breadcrumb trail: Cabin Allocaton | Assign cabin
    • The CID has been included for onboard crew, previously the CID was only available for onsigners).
  • Enhancement 3:
    • Breadcrumb trail: Cabin allocation | Apply filter CID/Ranks/Planned changes
    • When the above filter is applied, the system loads the result and filters both the result and cabin on the left-hand side.
  • Enhancement 4:
    • Breadcrumb trail: Cabin allocation | Assign cabin
    • When the page alert for crew is already assigned, the warning should contain details of the already assigned cabin for the crew member being planned for a cabin allocation. See example below.

Picture8.png

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [ABILITY TO POST/DELETE CALCULATED TAX FROM THE EXTERNAL SYSTEM INTO COMPAS PAYROLL VIA API ENDPOINT]

  • The following enhancements have been made to support the ability to POST/Delete <Tax element name> into Compas payroll via an API endpoint.
  • Enhancement 1:
    • The ability to insert the data received from the external system into Compas through Post API end point has been added.
      • The received wage element ID must be crossed with the wage element (master table). See below for the four types of wage elements we will receive:
        • MSS Employee deduction 
        • MSS Employer deduction 
        • MSS Employee correction
        • MSS Employer correction
  • Enhancement 2:
    • The ability to validate the data received from the external system into Compas through Post API end point has been added.
      • If data received for closed payroll month, system should not allow to insert the data.
      • Acknowledge with message like 'Payroll month is closed, data cannot be Inserted”'.
      • Acknowledge the status message at each hit of the API.
  • Enhancement 3:
    • The ability to delete the data received from the external system into Compas through the delete API end point has been added.
  • Enhancement 4:
    • The ability to validate the data received from the external system into Compas through the delete API end point has been added.
      • Closed Payroll month data must not be allowed to delete, acknowledge with a message like “Payroll month is closed, data cannot be deleted”.
      • Acknowledge the status message at each hit of the Api.
  • Enhancement 5:
    • The ability to store the data in a new table has been added has been added.

Preconditions:

Configure API Endpoint Access

  1. Open ...\CompasAPI\v2\Staging\CompasRestIntegrationService\App_Data directory
  2. Modify {companyShortName}_config.json file, add the following line in the available endpoints as well as allowed endpoint for the users
    1.  "POST"
      1. "process/externalTax"
    2. "DELETE"
      1. "process/externalTax"

Configure Postman

  1. Under environment add the following variables:
    1.  "compasUrl"
      1. sample value: "https://localhost/Compas/compasapi/v2/CompasRestService.svc/" 
    2. "token"
      1. Token value base in {companyShortName}_config file configration under users > token section

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [ABILITY TO PROCESS DATA RECIEVED THROUGH API ENDPOINT INTO PAYROLL MODULE]

  • The provision to integrate the data into payroll module (based on the data process through the API end point) has been added and enabled.
  • With each action performed on the Payroll Overview screen, the system must link the data relationship. 
    • For example, when payroll is closed, the ID (from the main payroll tables) should update in the new table (which holds the data the new table).
    • In the same way, when reopening payroll, the updated payroll roll ID must get nullified.
  • The process should be:
    • New table → Temp tables - when payroll overview is clicked.
    • New table → Temp tables - actual table [payroll main & details] when payroll closed.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [TIMEOUT ERROR | VSLPLAN]

  • A query related to the VslPlan.aspx page was generating execution plan errors. This means it was not benefiting from the optimal plan for this page.
  • Improvements have been made to the query optimization for planned events.

Reproduction steps:

To improve the performance, the following alteration must be made (to position the 2 left joins ‘ON’ criteria.)

FROM:

Picture9.png

TO:

Picture10.png

 

🛠️Bug Fixes

[COMPAS ONBOARD] [UNABLE TO LOAD CABIN ALLOCATION IN ONBOARD QC]

  • Issue:
    • When trying to load Cabin Allocation, a console error was appearing.
  • Outcome:
    • This issue has been fixed.

Reproduction steps:

  1. Log into COMPAS Onboard.
  2. Click on the Home dropdown menu.
  3. Click on the Cabin allocation menu item.

The Cabin allocation page openly successfully without an error appearing.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [PENSIONELEMENTSBACKPAYINTEGRATION PARAMETER NOT FUNCTIONING CORRECTLY]

  • Issue:
    • The ‘PensionElementsBackpayIntegration’ parameter was not calculating any required pension contributions (based on backpay corrections) correctly.
  • Outcome:
    • This issue has been fixed.

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. Click on the Payroll dropdown menu.
  3. Click on the Payroll overview menu item.
  4. On the required vessel, click on the View Payroll icon of the configured crew.
  5. In the Month and Year dropdown menu, select the relevant option.
  6. Under the Taxable wage details section, ensure the Hypotax (base amount) backpay adjustment shows correctly.

The pension scheme is now correctly processed based on the backpay calculations and the base amount is not included as an earning in the payroll.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [TIMEOUT ERROR | PERFORMANCE IMPROVEMENTS]

  • Issue:
    • The BankReceiptVesselMOGroups.Status column that filters out null values, changes the execution plan and takes around 50 seconds to complete.
    • Performance has been improved on Compas.ScheduledJobs.Common > ShipmoneyJob.
    • The following change has been applied within the SQL on the ‘WHERE’ clause:
      • From:
      • To:
  • Outcome:
    • This issue has been fixed.

Reproduction steps:

PART 1

  1. Log into COMPAS Cloud (Office).
  2. Click on the Admin dropdown menu.
  3. Click on the Admin panel menu item.
  4. Under the System heading, click Scheduled Jobs.
  5. Search for ProcessShipmoneyTransactions and click Enable.

PART 2

  1. Log into Hangfire Dashboard.
  2. Click the Recurring Jobs column heading.
  3. Click the white box next to ProcessShipmoneyTransactions (to add a check in the box).
  4. Click Trigger Now.
  5. Click the Jobs column heading.
  6. In the left-hand column, click Succeeded.
  7. Click ShipmoneyJob.Start.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [TIMEOUT ERROR | PERFORMANCE IMPROVEMENTS]

  • Issue:
    • At times, there was a periodic query that would run quickly. This issue is related to payroll associated with crew movements.
    • Improvements have been made to the query optimization.
      • Breadcrumb Trail: Compas Onboard | Payroll | Payroll Overview.
  • Outcome:
    • This issue has been fixed.

Reproduction steps:

Add the following 2 Indexes to Compas DB:

The IDX_CREW_MOVEMENTS_C1_C2_C7_I60_I61] index is created against the CREW_MOVEMENTS table.
The IDX_PAYROLL_MAIN_C5_C2_C1_C3_C4_C24_I22 index is created against the PAYROLL_MAIN table.

Code to create as follows:
CREATE NONCLUSTERED INDEX IDX_CREW_MOVEMENTS_C1_C2_C7_I60_I61] ON [dbo].[CREW_MOVEMENTS]
(
[CM_ID] ASC,
[CM_CID] ASC,
[CM_MOVEMENT_TYPE] ASC
)
INCLUDE([CM_FINANCE_APPROVED_DATE],[CM_IS_REJECTED]) WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY]
CREATE NONCLUSTERED INDEX [IDX_PAYROLL_MAIN_C5_C2_C1_C3_C4_C24_I22] ON [dbo].[PAYROLL_MAIN]
(
[PM_MOVEMENT_ID] ASC,
[PM_VESSEL_CODE] ASC,
[PM_ID] ASC,
[PM_MONTH] ASC,
[PM_YEAR] ASC,
[PM_CREW_ID] ASC
)
INCLUDE([PM_END_DAY]) WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY]

-------------------------------------------------------------------------------------------------------------------

[COMPAS ONBOARD] [TAX ALLOCATION – MERGE DATA]

  • Issue:
    • In Compas Onboard, the tax allocation tool doesn’t allow different set options to be selected when the data is merged in same jurisdiction.
  • Outcome:
    • This issue has been fixed.

Preconditions:

  1. Change the branch for respective PR.
  2. Complete the schema compare.
  3. Update the dbo.AddTaxAllocation procedure table.
  4. Build the CompasSql.sln and CompasOnboard.sln application.

Reproduction steps:

  1. Log into COMPAS Onboard.
  2. Click on the Payroll dropdown menu.
  3. Click on the Tax allocation menu item.

-------------------------------------------------------------------------------------------------------------------

[COMPAS CLOUD (OFFICE)] [NORWEGIAN PENSION REPORT]

  • Issue:
    • When generating the Norwegian payroll report, it fails due to excess days against the schema (where the schema allows a maximum of 30 days per month).
    • Since the wage matrix is based on calendar days, the system is showing 31.
    • The system should cap the maximum number of income days to 30 in the report.
    • Logic placed: A new parameter titled ‘MaxIncomeDaysNorwegianPensionReport’ has been added with a default value of 30.
    • If income days are more than the parameter value, then it will display the param value else actual income days.
    • If the seafarer has 31 days, the report will not generate.
  • Outcome:
    • This issue has been fixed.

Reproduction steps:

  1. Log into COMPAS Cloud (Office).
  2. Click on the Payroll dropdown menu.
  3. Click on the Norwegian Payroll dropdown menu.
  4. Click on the Reports dropdown menu.
  5. Click on the Pension report menu item.
  6. Pull the report for 3 periods in ODF staging.
  7. Select Employer.
  8. Select the Year.
  9. Select Months (Periods).
  10. Check the checkbox for Exempt PTS.
  11. Click on the Total Pension Fund Amount (View details) option.
  12. Check for the Income days according to the days in that selected month.
  13. Check the export options:
    1. Export to Excel
    2. Export to XML
    3. Export to PDF

Summary

We appreciate your continued partnership and welcome any feedback you have on this latest update. If you have any questions or need further assistance, please feel free to reach out to our support team.

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.