4.5.2 Core Enhancements

Importing Assured Companies and Settling Agent Companies via Data Importer

[OMS-9, OMS-10, OMS-1070, OMS-1152, OMS-1228]

Two new Template Types have been added to Data Importer, Assured Company and Settling Agent Company. Similarly to the Shipment Template, users can create templates for Assured and Settling Agent Companies in order to quickly import large batches of data.

Note that when either Assured Company or Settling Agent Company is selected, the Policy widget on the right of the screen does not display.

When importing an Assured Company, the Insured's EDFs can be imported and mapped as part of the process. The following are mandatory fields that must be mapped during the process:

• Owner Company Client Code or Parent Company Client Code

• Assured Company Name

• Assured Company Client Code

• Assured Company Country

The user must enter the Owner Company Client Code for an Assured Parent Company or the Parent Company Client Code for the Assured Company Subsidiaries in the upload spreadsheet. Companies in the same hierarchy must be entered in hierarchical order. The system will process the spreadsheet data from the first row onward.

The system will create the Insured EDF field mapping based on the current user’s Owner Company and the EDF availability. Only values for Insured EDFs that are available to all policies can be uploaded.

The upload spreadsheet will have the EDF field names available as headers, and the user will provide the values for each Assured Company where applicable.

Users can also import new Settling Agent Companies via Data Importer using the provided template. The following are mandatory fields that must be mapped for the import:

• Owner Company Client Code
• Settling Agent Group Client Code
• Agent Company Name
• Agent Company Client Code
• Agent Company City

• Agent Company Country (Two-letter ISO Code)

  Note that users can enter multiple two-letter ISO codes, separated by a comma, in the Country of Service field.

Note: The Data Value Mapping screens and functionality has not been implemented for the Assured Company or Settling Agent Company import.

• For details on creating new template types for Assured Companies and Settling Agent companies, see the Managing Data Importer Templates section.

Create and Update User APIs

[OMS-1230, OMS-1231, Oms-1502, OMS-1503]

Two new APIs for POST Create User and PATCH Update User have been added to allow users to create a new user and associated password or update an existing user within the system. Note that the newly created user will have to be assigned the rights to login to Extranet and/or ClientSide, as needed.

The User APIs require the user calling the APIs to have the Manage Employee security right in order to create a new user, either Non-Assured or Assured. If the user does not have the appropriate rights, the system will return an error message; "User does not have security rights to create a new employee."

Additionally, the current user must have access to the assigned company for the new employee being created. If not, the system will return an error message; "The company client code {0} is either invalid or not in scope."

The following rules apply when creating new users via API:

• If the Company type mentioned in the API is a Licensee company then the created employee will be a Licensee employee.

• If the Company type mentioned in the API is an Assured company then the created employee will be an Assured employee.

• If the Company type mentioned in the API is a Proprietary company then the created employee will be a Proprietary employee.

Upon creating the new user, the system will validate that the User Type entered for the Employee Type is valid. The system determines this based on the logged in user's Employee User Type and follows the system's hierarchy as Company Administrator, Administrator, Power user, and Private user. Note that there are two exceptions; Licensee users do not have the option of a Private user type and Proprietary users can only be assigned the Power user type. If an invalid user type is selected, an error message will display, "The User Type is not a valid option."

The employee's User ID must be unique across the system, and if not, the API will return the corresponding error message.

Finally, the policy associated to the employee being created must be within the scope of the logged in Assured user, otherwise, the system will return an error message; "The policy number is either invalid or not in scope."

Once the new user is successfully created, the password is assigned following the existing system password management rules and the user account is active.

The following are mandatory fields that must be included in the request for the Create User API:

• FirstName

• LastName

• Email

• UserID

• UserType

• DefaultCurrencyISO

• CompanyType

• CompanyClientCode

When the EnableDigitalPlatform setting is True, the system will create the employee and associated user password that was requested in the API in ICS as well.

• For details on using the new APIs, see the corresponding Swagger documentation.

Integration User Setting

[OMS-1148, OMS-1149]

A new checkbox to identify which users are being used for integrations so that they are not included in the Auto User Deactivation job has been added. The new field, Integration User appears on the Employee Profile page under the Employee Preferences panel. Note that from the user's own Profile page, the field appears as read-only. This field is exposed in the Create and Update User APIs.

When the setting is active, the automatic job that is run when updating employee users will omit the Integration Users.

• For details on viewing the new setting, see the Modifying Your User Profile section.

Language File Updates

[OMS-1518]

All new labels, system warnings, and messages introduced for the new release were translated into the eight other languages offered by the Oceanwide Marine Suite and were added into the existing core language files.

The following list includes all labels, system warnings, and messages that have been translated: