For locally installed licensees, this hotfix, v1251HF12, can be downloaded from TASK Solution # 96 titled "v12.5.1 General Release Hotfixes" in the "Version Upgrades and Patches" workspace.

The changes addressed in this hotfix include the following:

• Mechanisms were added for notification of the encryption keys expiration. The notification will appear when logging into the Tessitura Security application, and on the Services Dashboard when the encryption keys have not been regenerated in the last year.  A warning notification will appear 15 days before the deadline as well.  If encryption keys expire, credit cards can still be stored and accessed.
  • Please reference the Encryption Keys topic in the Tessitura Online Help System for instructions to regenerate the Encryption Keys.
• In the Tessitura Security Application, the process of recreating data encryption keys has been made more efficient.
• Tessitura now uses a hashed and salted copy of the application password.
• In the API, when the SOAP API calls the REST API (for example, pricing an order using GetCart), encrypted passwords are no longer stored in the database and the SOAP API now reads the hashed password and sends it to the REST API calls.
• For Payment Express EMV devices (Telium only), if the DpsTxnRef field is returned, it will be stored in T_PAYMENT.ccref_no. This will allow the transactions to be refunded using refund prior payment.

For organizations that have installed v12.5.1:

• Although the v12.5.1 upgrade deadline of July 15, 2016 has not changed, the installation of v1251HF12 is optional but highly recommended.  Licensees will be able to upgrade to Tessitura v14 upon its release from the base v12.5.1 General Release without this hotfix in place.
• The v1251HF12 hotfix includes many v12.5.1 hotfixes released to date.  Detailed information about previously released hotfixes that are incorporated into v1251HF12 is available in the hotfix installation instructions document and in TASK Version Upgrades and Patches Solution # 96.
• Any v12.5.1 hotfixes that may be released in the future will require that this v1251HF12 hotfix be in place before subsequent hotfixes can be installed.
• For locally installed licensees, applying this hotfix involves:
  • Executing a SQL Script
  • Updating the Tessitura Client Files in the client distribution folder
  • Updating the Tessitura Security application files
  • Using the Tessitura Installation Manager (TIM) re-install the Tessitura Service (REST), Tessitura Web (Tessitura On the GO), WebApi (SOAP) and the Services Dashboard
  • If you have deployed custom plugins or interceptors, they will need to be re-enabled after installing this hotfix.
• Licensees hosted in RAMP that would like the Managed Services team to install this hotfix should open a TASK help ticket in the “RAMP Support” workspace so that the team can slot your organization into the hotfix installation schedule.

For organizations that have not yet installed v12.5.1 in Production:

For locally installed licensees:

The v12.5.1 General Release upgrade files posted in TASK Version Upgrades and Patches Solution # 93 have been updated to incorporate v1251HF12 and v12.5.1 hotfixes v1251HF1 through v1251HF13.  If your organization has installed the v12.5.1 General Release on your Test system, the Network recommends that you download the updated files from Solution # 93 and re-install the release so that you are testing with the most current code and so that you will automatically have all v12.5.1 hotfixes released to date.  If you have downloaded the v12.5.1 General Release upgrade files but have not yet deployed the release, we recommend that you re-download the updated files so that the installation will be performed using the most current code with all released hotfixes included.

For licensees hosted in RAMP:

From this point forward, all Test and Production upgrades to v12.5.1 in RAMP will be installed with this important hotfix in place.  If you are currently testing v12.5.1, the Upgrade Scheduling team will contact you via your upgrade TASK ticket regarding the installation of this hotfix into your test system.