20 February 2017

Renewal processing

  • When a term was set to Non-Renewal, users could manually create a renewal revision without updating the prior term's renewal status; this led to a few processing issues. This change improved the process in two ways. First, when a policy's term is set to Non-Renewal and a user manually creates a renewal revision, he/she will receive a popup that reads, This term is marked as Non-Renewal. Are you certain you would like to renew this policy?. Second, if the user clicks Yes, BriteCore will automatically update the previous term from Non-Renewal to Renewal.