•The Terms of Use can now be customized to include additional terms and conditions for each licensee. The changes need to be deployed by Oceanwide, so please contact your Oceanwide Representative for more information on this feature.
•Numbers in dynamic numeric fields will now have the formatting of the decimal and thousands separators set according to the user's browser settings (1,000.00 or 1.000,00, for example). This formatting will carry through to documents as they are generated, but will not affect documents already generated under different browser settings.
Note: If any additional formatting is applied in the document template based on the decimal or comma separators, there could be some unexpected results when generating the document under different browser settings.
For example:
1. A user with specific regional settings may see a number formatted as 1.000,0000 (one thousand, displayed to four decimal places).
2. A document template is available that expects a number formatted as 1,000.0000 and applies additional formatting to round the value to two decimal places.
3. The user generates the document, but the additional formatting command rounds the number two digits after the period. The document then displays the value 1.00 mistaking the thousands separator for the decimal.
In order to avoid such errors, these types of custom formatting can be removed, or separate document templates can be configured for different regional formats.
•Corrected issue where the Bound Date column in the Policy Transaction Grid would show the last modified date instead of the bound date.
•Corrected issue where bad placeholders in a document would cause an error in the system.
•Corrected issue where requesting a special quote could change the status to Bind Requested instead of Special Quote Requested.
•Corrected issue where changing option list codes could disable triggers using the affected lists.
•Corrected error that would occur when clicking the Renew Now button in the Automatic Processing feature.
•Corrected issue where a rate driver field might not become unavailable in lists of rate driver fields.
•Corrected issue where triggers based on Multi-Selects and Checkbox Groups would only accept one value in the list.
•Corrected issue where using $If functions to retrieve grid values would repeatedly return the value of the first row.
•Corrected issue where changes to Text Area and Date Picker type fields would not disable the Print Document and Bind buttons.
•Corrected issue where the rounding precision was not being applied properly to values called with the Current Term and Previous Term references in calculated fields.
•Corrected issue that would occur when multiple validations referred to a single checkbox group. Not all validations that proved true would activate.