Skip to main content
Skip table of contents

7.0.204.x Release Notes

Release Date

Table of contents


Features

RREX-329 – Logging of User that Runs Background Job

An additional column called ‘Executed By’ has been added to the Background Job Log for the user triggering a background job. If the background job is triggered by the job scheduler, the system automation user will be recorded.


Fixes

FCC-765 – Fix for Premium Credit Updated after Cancellation

When using TX premium credit and updating premium credit after cancellation, the ActivateBonds background job would reactivate the bond standing (Active or Inactive) if the last transaction on the bond is the Update Premium Credit transaction. This has been adjusted to not update the bond standing if the bond had already been cancelled.

OLR-710/WEB-647 – Fix for Flat Rate for Renewal

When AddDaysToExpiration setting is set to ‘1’ and the bond type is using a flat rate, the renewal rating would increase slightly if the renewal term contained an additional day of a leap year. This has been corrected to calculate the flat rate appropriately.

RREX-356 – Correction to Account History Questions

  • When addressing AVI-546 in Release 203, an additional issue was uncovered. When processing the following actions, the data for account questions was not being saved into historical tables:

    • Update LOC

    • Suspend

    • Close

    • Reinstate

  • This has been corrected to save the data in historical tables.

    • NOTE: The data from the transaction is saved as the current answer for the question, the issue is only on the transaction history records.

SKY-328 – Adjustment to Account Update People and Companies Pushed from Bonds

  • When performing any of the following actions, the account should not receive an Update People and Companies transaction.

    • Initiate Cancellation

    • Submit Renewal Application

    • Requote Renewal

    • Purchase Quote for Renewal Application

  • NOTE: If any transaction adds a person or a company to a bond, the entity is then added to the account. No person or company can be on a bond without being on the account as well.

WEB-655 – Correction to Total Premium Rule for SureLYNX™ Bonds

When using SureLYNX™, bond configurations using the total premium decision rule, would not evaluate the rule properly, making the bonds refer even if they are passing the underwriting rule criteria. This has been corrected to evaluate the Total Premium rule appropriately for SureLYNX™ bonds.

1

I

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.