Don’t allow null Loss Date

Feature summary

With the Don’t allow null Loss Date feature, users in the Provider Administrator portal won’t be able to change a claim’s status to Open if the Loss Date isn’t entered for the claim. When a user attempts to change a claim’s status to Open, and there is no Loss Date, an Error pop-up window will open and notify the user that a valid loss date must be selected. See Figure 1.

Figure 1: The Error message that appears when a user tries to change a claim’s status to Open without adding a valid loss date.

 When a valid Loss Date is entered for a claim, users can change the claim’s status to Open.

Note: Users can still move a claim to an inactive status without a Loss Date, such as Pending, Closed, or Archived.

The Don’t allow null Loss Date feature will prevent the potential creation of bad data and reporting errors.

This feature will impact clients on the master branch that manage claims in the Provider Administrator portal. No configuration is required as this is a functional change.

What’s changing

The Loss Date of a claim is required when a user in the Provider Administrator portal attempts to change the claim’s status to Open. If the Loss Date isn’t entered for the claim and a user attempts to move the claim status to Open, then an Error pop-up window will open with the following message:

Please select a valid loss date to continue.

The user will be prevented from moving a claim to Open status until the Loss Date is entered.

Questions

If you have questions regarding this change, please contact your BriteCore support team.