Change the warning message when deleting a saved contract to include "an account MAY exist in Tuition Management".

A common issue in EMS is when a change needs to be made to a candidate's relationships or record, and so a new contract needs to be issued before the first is even submitted.

When admin go to delete the contract there is a message that reads "[contract] has been saved by parent, and an account has been created in Tuition Management. Deleting the contract will not delete the account in Tuition Management and the responsible signer will not be able to complete another Tuition Management Contract for this user for this enrollment year."

This brings a lot of confusion to Support, as many EMS admin do not have access to see the BBTM side to confirm in there is or is not an account for the family for that year.

Please amend the message to read something like:
"[contract] has been saved by parent, and an account may have been created in Tuition Management. Please confirm there is no account for this enrollment year in Tuition Management for this student before proceeding. Deleting the contract will not delete the account in Tuition Management and the responsible signer will not be able to complete another Tuition Management Contract for this user for this enrollment year."

  • Grace Estridge
  • Mar 30 2023
Blackbaud Enrollment Management / Contracts
  • Attach files
  • Bryan Lorenzo commented
    March 31, 2023 22:31

    Brian, that is a great tip I love to share with others!

    Attachments Open full size
  • Brian LeBlanc commented
    March 30, 2023 20:14

    I definitely panicked a bit when I first started working in EMS because of this error. I stumbled across a workaround that should tell an EMS user that a Tuition Management account has not been created: if you edit the contract and the Family ID column is blank, then the BBTM account has not been created yet regardless of what the warning message says. If the Family ID column has a number in it, then the account has been created.

    Of course, the fact that we need to work around this message to prevent panic is its own issue, and should absolutely be addressed by Blackbaud because not only is it confusing, in many cases it is simply not correct.

    Attachments Open full size

Related ideas