May '23 Increment release notes

Requirements status is visible in the admin panel for each entity for different insurance plans. This is visible for Insurance Agents, Operations, and Producers. So the user can know at any moment if all prerequisites are fulfilled before the binding process starts.

When submitting Request Coverage, we have enabled multiple endorsements to be added to one request to reduce the steps. In this way, the user doesn’t have to submit and keep track of numerous Coverage Requests

The coverage request screen is now changed to monitor the progress of the request. And it is renamed from "Pending Endorsement" to "Coverage Request." The screen is automatically refreshed every minute, and the user can be on track with everything happening with coverage requests. Statuses are updated when some action is finished (whether Producer, Agent or the system itself does it). For example - when Producer signs the SCE form in DocuSign, Agent will see that information as new status on Coverage Request Screen.

After the Agent reviews the request, an SCE PDF form is requested from the AIP. When SCE is generated on the AIP side, the user can see and download the form in the LIA application. This form is sent to the DocuSigning process when Agent decides it is ready for e-signing.

The agent and Producer must sign the SCE form before it’s sent to AIP. The process of signing starts with the Producer and, afterward, is sent to an Agent. When SCE is signed, it is sent as a finished signed document to all Agents (primary contacts and agents marked for notifications) and to the Producer

Also, after e-signing, LIA will automatically upload the SCE form to the AIP when the DocuSign process is finished.

When AIP approves Endorsements and becomes officially purchased, they will be imported as Active endorsements in the LIA application. Endorsements are then connected and continuously kept in sync with the AIP.

All actions in LRP binding process are accompanied by emails sent to all roles included

Increased accuracy of all endorsements now being accounted for in the tool so the producer and the agent know the status and the progress of the endorsement

The binding process increased accuracy and saved the agent time when going through the endorsement process.

Both processes have helped the producer engage more with each endorsement they write.

🐛 Fixed the issue with the wrong display of Total values on the Endorsement graph, as it was showing Total values instead of per cwt. @marko.peranovic

🐛 Fixed the issue with the display of wrong data on the Endorsement graph. The graph displayed data from the previously selected operation. @marko.peranovic

🐛 In Market Dynamics, if 1st level was saved as a preference, it wasn’t displayed the same as it was in the dropdown table. Now 1st level is displayed the same on the all-screen as it is in the list. @luka.ferlez

🚸 To help users to understand better what the Deductible category means and what it is presenting, we have added an info option by the Deductible label. This info option will describe how Deductible is used in Market Dynamics. @marko.peranovic

🚸 In order to avoid having an overlap when a wide range of years is selected, the text for year direction is changed when a certain year range is selected. @patrick.kossi

🐛 Fixed issue when the Price Trends page is opened - the expected quarter wasn’t shown as the nearest quarter ending. Now, when it is open, it will show the correct quarter to have a better comparison right away when the page is opened. @ivana.kristo

🚸 Email notification is added when coverage is requested from the producer. Now the producer will get additional confirmation that his Coverage Request was forwarded to the Agent. @luka.ferlez

🐛 Fixed issue when matching operations in AIP Sync. Now when the operation is matched, the user will see all other available operations for matching instead of displaying that there isn’t anything more to match. @ivana.kristo

🐛 Fixes issue with Contact display after refresh. When a page with Contacts is manually refreshed, the Contact displayed becomes invisible. Now this problem is solved, and when the page is refreshed – all Contacts connected to that Operation are displayed. @marko.peranovic

🚸 Fixed issue with occasional popping up message „Invalid Practice code“ when working in the application. @patrick.kossi

🚸 We have changed the day when weekly reports are sent to have more time for communication with clients who receive weekly reports. Reports are moved from Friday to Wednesday, giving more time to discuss available offers and options to purchase endorsements. @mladen.sasa @marko.peranovic

🐛 Fixed the issue of displaying the wrong date when existing endorsements are edited. The problem is solved, and now when editing, viewing, and seeing additional endorsement information, it is displayed with the correct Sales Effective Date. This is solved for DRP and LRP endorsements. @luka.ferlez

🐛 Biometric login fix - In new release a bug occurring during usage of Face ID on iOS devices was fixed. The issue occurred in some cases where biometric authentication would receive an error from device, due to possible issues from the device itself. The application was not able to present that error, and unfortunately stopped at that point while trying to switch to standard login with credentials. @patrick.ruzman

🐛 Change of API endpoints - With the new release, a new set of server API endpoints were placed, in order to achieve better performance in retrieving required data. This results in overall better experience for the user. This way application is set up to date with the web. @patrick.ruzman

🐛 Market dynamics details fix - Together with the change of API endpoints, some data schemes were also changed with time. Due to these changes, mobile application was not able to render details for Market dynamics, and showed only a blank view. The model for retrieving data was changed to required one, as also the business logic responsible for presenting data was refactored. Refactoring was done in order to reduce code amount and complexity, to achieve better performance and better user experience. @patrick.ruzman