Improvements and resolved issues

The FEIN ID field was not masked (XENG-1875)

Issue: The FEIN ID number was not masked in some of the response and request methods inside the Workers' Comp LOB.

Passengers, witnesses, and other contacts were not visible when resuming an FNOL claim (XENG-1895)

Issue: When adding a passenger, witness, or another contact to an FNOL draft claim, if you exited before the claim was complete, on resuming editing, these contacts were not saved.

An FNOL draft claim could not be resumed when a non-policy vehicle was included in the claim (XENG-1897)

Issue: If you included a non-policy vehicle in an FNOL draft claim and exited the claim process before the draft was complete, you could not resume editing the claim. Instead, an error was displayed on your screen.

Claims could not be opened when reported by someone other than the policyholder (XENG-1911)

Issue: When creating a new claim in ClaimCenter, if the Reported by field was set to the name of anyone other than the policyholder, when you tried to open the claim in ProducerEngage, the claim was blank.

Insecure Direct Object Reference (IDOR) in the policy diff (XENG-1912)

Issue: If you logged in as a user and made a request to the getPolicyTransactionsForPolicy API endpoint with the selected policy's ID to retrieve a jobNumber, you could log in as a second user and make a request to the getPolicyDiffWithPrevious endpoint using the previously obtained jobNumber value.

Policyholder account contacts were visible in the getMainAccountContacts request (XENG-1935)

Issue: Policyholder account contacts were visible to other users through the getMainAccountContacts request.

Applications sometimes didn't log out after a set period of time (JUT-20814)

Products this applies to: CustomerEngage Account Management, CustomerEngage Claims Management, ProducerEngage, ProducerEngage Claims Management, ServiceRepEngage, VendorEngage

Issue: When using a Digital reference application on a slower network, you may have encountered an issue where the application logged out after a set period of time, regardless of user activity.

Inactivity logout functionality worked inconsistently (XENG-1756)

Issue: Occasionally the token refresh and logout functionality did not work correctly when the inactivity timeout duration was reached.

QuestionSet didn’t have the capability to parse params

At the moment QuestionSet doesn’t have capability to parse params, and display keys are shown instead of translated string value.