6.0.57.x Release Notes

Features

• 5893 – Stopped storing the last four digits of Credit Card numbers from e-SURETY™ databases.

  • The last four digits will still be available through the user interface, but this data is pulled directly from the Payment Processor Provider.

• 5355 – Separated the RunETL job into three separate jobs:

  • RunETL: runs the reporting portion of the original RunETL job. This no longer delivers the TransSync tables downstream via the web service call.

  • TransSync: runs the TransSync portion of the original RunETL job. See details at the end of the release notes for additions made to the web service call.

  • LegacyTransSync: sends backwards-compatible TransSync records for backend systems built for the e-SURETY™ version 5 web service call.

    • These jobs will be scheduled to be run periodically according to customers’ needs. They can also be manually run through the e-SURETY™ User Interface at: All>Background Jobs>Submit Job.

• 5894 – Delete PersonalCreditReports Table from the ETL

  • Due to security improvements, the PersonalCreditReports table was removed from the reporting database.

• 4136 – In TransSync the ApplicantSSNFEIN field is now passed unencrypted.

  • Previously the field had been encrypted.  While this is still encrypted in the e-SURETY™ database, it is unencrypted exclusively while going through TransSync.

• 5346 – Credit Scores are now available through TransSync web service call.

  • Due to security improvements, credit scores had been removed from the reporting database, and hence were no longer available to be sent downstream via the TransSync web service call. Credit Scores are now being sent without being stored on the reporting database.

Fixes

• 5833 – Fixed the State Surcharge from Calculating Incorrectly

  • When using the State Surcharge feature, the fee generated for this was calculating twice as much as the percentage entered for the surcharge. This has now been corrected to calculate a fee based off the percentage entered for the state times the premium amount.

• 5430 – Bond Configurations with Inactive Classes, Categories, Obligees, and Categories are now not available for Purchase or at Maintain Bond.

  • Previously bond configurations with one of their main criteria (Class, Category, Carrier, or Obligee) inactivated were still available to be purchased and maintained.

• 5432 – Fixed the Copy Bond function to be able to handle larger amounts of data being copied from the original bond.

  • When copying a bond configuration with larger amounts of data, for instance thousands of agency assignments,

• 5911 – Fixed the Current Billing Type returning as Null

  • In various scenarios, the default billing type for a bond was being set to NULL when performing a non-payment type action. The value would continue being set to NULL in payment type actions, causing the action to error. This has been corrected to bring in the default billing type when performing a payment type action.

New TransSync Background Job for Web Service Call

• Changes to Web Service

  • All changes are additions.

  • Added CompanyFein to main WarehouseBondTransactionModel

    • There already is a PrincipalSsn field, and the CompanyFein field was in the database, but is now being sent on the web service.  It will be decrypted if the setting specifies.

  • Added Custom fields to the WarehouseCompanyModel

  • The way 'FinishGetBondTransactions' works is a little different

    • Instead of records getting inserted into GetTransSyncHistory when FinishGetBondTransactions is called, they are inserted when BeginGetBondTransactions is called, with the field SuccessfullyProcessed having a value of 0. 

      • If SuccessfullyProcessed is 0, these records are not excluded when calling BeginGetBondTransactions, it is as if they are not there yet.

    • When FinishGetBondTransactions is called, the WebServiceAccessLogId of the last time BeginGetBondTransactions was called for that user is looked up, and those records in GetTransSyncHistory (WHERE WebServiceLogId = x AND UserId = y) have SuccessfullyProcessed updated to 1.  Now those will be excluded.

    • A new Web Service method now exists, FinishSpecificGetBondTransactions

      • This method takes the WebServiceAccessLogId as an argument, so you can target the transaction explicitly. 

        • NOTE that you get that Id when you call BeginGetBondTransactions from the ID field of the response.

      • This is the Preferred way to use TransSync, as the transactional integrity is more secure this way.  FinishGetBondTransactions is for backwards compatibility and should be considered obsolete.

NOTE: TransSync can now be configured to filter the transactions to only include Invoice Events. For this to be set up, please contact the e-SURETY™ Support Team.