Release Notes for 1.19.0

Thursday, November 14, 2024

New Features:

  • 11102– POLICY – Added an adjustment option to payroll reports so you add additional fees or credits based on flat values or calculated percentages
  • 11090 – POLICY – Added the ability to refresh the policy JSON while issuing a policy to capture any changes that may have been made to the insured since the quote was started.  This is also being handled automatically while a quote is new, but having a manual refresh will be helpful.
  • 10965 – POLICY – Adding the ability to issue a waiver – no charge outside of a quote or endorsement – instead of needing to add a certificate.  This is step one, adding the menu item and the initial listing of waivers. Step 2 is to add the detail for a new waiver (coming soon).

Enhancements:

  • 11315 – POLICY – We’ve changed the labels on the incident reporting form to all them to render HTML (safely).  You can now add helpful font embellishments (bold, underline, italic) as well as color – and even an emoji if you are so inclined.
  • 11253 – POLICY – The quote narratives are no longer a separate page on the quote, instead they are housed in a modal that can be opened from any other page in the quote (and moved around as needed).
  • 11126 – POLICY – When moving around in the quote, the data has always been retained in the JSON used to build the quote, but it will now be periodically saved to the database tables as well.  This will make reporting on unbound quotes possible now.
  • 11451 – PORTAL – When completing an incident form is completed online a user can bypass required fields by using the side navigation to jump over a section.  This has been resolved, and now individual fields will still validate as the user completes the form, but before an incident can be submitted it must pass a final validation which will re-check each field.

Bugs:

  • 11383 – POLICY – Fixed the issue when editing a program (admin tool) it would clear the customer id and cause permission issues.
  • 11324 – POLICY – The scheduled payment table was including deleted transactions.
  • 11323 – POLICY – Fixed the issue when posting an ACH batch, it was erroneously displaying as check received.
  • 11319 – POLICY – On the new payment form, it was displaying the Invoice ID instead of the Invoice Number.
  • 11318 – POLICY – The payment listing page was rounding and not displaying the cents.
  • 11305 – PORTAL – The File a Claim button/link wasn’t working on the bottom of the home page but was working on the top.
  • 11295 – PORTAL – The claim notes section can now display more categories, and the note text bubble grows to display longer notes.
  • 11285 – PORTAL – The upload button when adding a file to a claim was not visible. Instead, it is always visible, just disabled until files are added.
  • 11282 – PORTAL – When uploading a file to a claim, the underlying table of attachments was not updating after the save.
  • 11281 – PORTAL – When uploading a file to a claim, the files were being uploaded and stored in Azure and the DB, even if the user clicks on the cancel button.  Files are now not saved until the user clicks on the Save button.
  • 11375 – POLICY – The audit information page would display the first user that would be on the drop-down list as assigned to an audit, even if nobody is assigned.  It will now include a blank and if nobody is assigned to an audit it will not display anyone.
  • 11461 – POLICY – Fixed the “infinite loop” when opening the payment modal can clicking on the Cancel button if the program only has 1 payment option.
  • 11459 – CLAIM – Fixed the upload files issue when adding multiple files at once from the slide out attachments form.
  • 11457 – POLICY – When the user would select the modifier source on a quote, their selection wasn’t being retained when they would return to the page.
  • 11420 – PORTAL – The date of injury date picker on the incident form is now locked down to the current date or older.  Sorry, you can’t pre-schedule your injuries anymore.
  • 11489 – POLICY – The ACH batch detail table was cutting off any amount after a comma in a formatted amount field (i.e. values over $999).