•A Sequence Number can now be assigned when selecting Integration Configurations within the Workflow Management page. If multiple integration configurations are set to activate on the same Event with the same Perform setting, the sequence number will define what order they activate. This allows later integrations to depend on the results of earlier integrations, including evaluating the trigger to determine if the integration activates at all.
•A new placeholder has been added to identify the selected language of the user's browser. The [[UserCultureCode]] placeholder can be used in calculated fields to pull in the browser language code when the fields are updated. The placeholder returns the language in the short code, such as en-us. Some uses for this information include triggers and filters on combo boxes.
•A new email event type has been added to send emails when a transaction goes into Underwriting Required status. The Get Quote / Recalculate Quote – To Underwriting Required event is now available when creating an email configuration. Note that if the user has the ConfirmMaxReferralLimit1 security right, the transaction will go straight to Referred status instead of Underwriting Required, and emails for this event will not be sent.
•A Trigger option has been added to the Master Cover - Quote Option screen, allowing quote options to be included or excluded based on transaction details when the quotes are calculated.
•To ensure that users from insurer companies do not see quote information from other insurers, the Premium Widget has been modified. Whenever more than one insurer is attached to a master cover, even across quote options, then users from those insurer companies will not be able to see the premium value in the Premium Widget. They can still use the Quote Summary to see the premiums for individual quote options to which they have access.
If only one insurer company is attached to a master cover, then users from that company will be able to view the premium. This change does not affect client or distributor users.
•The Emphasize Actions feature from the Screen Management page has been extended to custom integrations. When configuring a Custom integration, the Emphasize Action checkbox can be selected to add a button at the bottom of the screen with the same label as the custom option in the Actions widget. If the option in the Actions widget is unavailable, the button will not be displayed.
•The label on the Code field for client companies can now be customized separately from other Code fields throughout the system. The Label_AssuredCode entry has been added to the language file in the Custom Labels page. Any changes to this label will apply wherever the code for a client company is displayed.
•The Bind action for integration configurations now applies to binding Cancellation and Reinstatement transactions as well.
•Automatic e-mails are now included in the E-mails list within the submission. The Type column has been added to the E-mails list, displaying whether the e-mail was generated automatically or manually.
•Previously, e-mails attached to a transaction were only visible to the sender and recipients. The Master Cover – E-mail Configurations page now has a new panel, E-mail History View Criteria, which allows the selection of security roles. Users with at least one of the selected security roles will be able to view the generated e-mails.
•The Enable Data Import feature, allowing users to import data directly into a grid, has now been enabled for View Grids.
•When creating or viewing a client company, either through the Client menu or within a submission, the Code field is now displayed. When creating a new client company, the code can be provided or the system will automatically generate the code on saving.
When viewing a client company created before this update, if a code does not already exist it must be provided before saving the company. If the code for an existing company contains invalid characters, they will need to be corrected before the company can be saved.
•The Custom Columns in Submission/Policy Grid panel in the Master Cover – Policy Settings page contains additional columns that can be customized and included in the submission list. The number of text columns has been increased from three to ten.
•The Allow Insurers to Edit Clients checkbox in the Miscellaneous Settings panel of the Master Cover – Policy Settings page has been changed to Allow Insurers to Create / Edit Clients. This setting now allows insurer users to create new clients within a submission in addition to editing existing clients.
Note that this only applies to new submissions created after activating this option. It will not allow changes to pre-existing submissions.
•When using the Accept Compliance action on a transaction, an Acceptance Reason must now be provided. The reason will be available in the Policy Information window, accessed through the Policy Information widget, and can be pulled into documents, e-mails, and fields.
•The Field Initial Value Settings panel in the field configuration page and the Policy Settings panel in the panel configuration page have been expanded to include Cancellation and Reinstatement transactions.
•The ability to view, create, edit, or delete Distributor configurations in a master cover no longer requires create or edit rights for the master cover itself. The ViewMasterCover right is required to access the master cover, but then the ViewMasterCoverDistributors, CreateMasterCoverDistributors, EditMasterCoverDistributors, and DeleteMasterCoverDistributors rights control the management of distributors within the master cover.
•Whenever sidebars are available, containing widgets or additional content, they can be pinned or unpinned using hidden icons at the top-right of the sidebars (the icons appear when the mouse pointer passes near them). When a sidebar is pinned, it remains open and the main screen adjusts to fit. When a sidebar is unpinned, it collapses to the side and the main screen fills the space. The unpinned sidebars can be expanded or collapsed as needed, overlapping the main screen when expanded. This feature can be disabled in the system configuration, managed by your Oceanwide Representative.
•The Reject Cancellation option, available when viewing Cancellation – Quoted transactions, has been replaced with the standard Delete option. This does not change the results, as both actions deleted the cancellation transaction, leaving the policy in effect.
Note that the Reject Cancellation option was associated to the CancelPolicy security right, while Delete is associated to the DeletePolicyTransaction security right. Users who had the ability to reject cancellations may not have the ability to delete them.
•The main menu bar at the top of the page can now be hidden. The ViewTopMenu security right has been created and added to all existing security roles by default.
Without this right, the menu bar is blank, even if the user has the rights to view other features within the system. Features can only be accessed through direct links, such as bookmarks or the policy links that can be included in emails. The menu bar may be turned off to control access when using the Single-Sign-On (SSO) feature.
•An optional configuration has been added to the core system settings. When enabled, completing a custom integration will automatically recalculate the quote if the current screen is set to recalculate in the master cover. For information on this setting, please contact your Oceanwide Representative. This does not apply to E-Signature integration types.
•When Policy Number Source in the Master Cover is set to Manual, any Renewal transactions will now take their policy number from the selected field. If the field value changes from one term to the next, the policy number will change.
•Corrected error that could occur on calculating quotes for two submissions received simultaneously through a web service.
•When importing transactions to update existing transactions, any fields with the default Read-Only setting will not be updated. Importing new transactions will still update these fields.
•Corrected error that would occur when importing policies for a master cover in Test mode.
•Corrected issue where the technical coverage would not match the effective coverage.
•Corrected issue that could occur if no taxes were applied to the New Business transaction, but were applied in an Endorsement. The endorsement taxes would not be counted in the term, affecting cancellation transactions.
•Corrected error that would occur when trying to auto-expire a quote on a deleted transaction.
•Corrected issue where setting a master cover to live without making any changes would not be recognized.
•Corrected error that could occur when exporting a master cover that included a tax code with more than 50 characters.
•Corrected error that could occur when publishing a workflow.
•Corrected issue where scheduled jobs might not run if a related insurer was removed from the master cover.