Date

Summary

v12.5.1

v12.5

v12.1.2

In Tessitura v12.5.0 and v12.5.1, communications between the Payment Gateway Service and Tessitura Client, REST API, and SOAP API are encrypted by a certificate issued by Network Solutions, a trusted Certificate Authority.  That certificate expires April 20, 2018. An updated certificate is included here and can be applied by simply adding it to the existing Payment Gateway Service folder.

v1251HF57
includes HF 8, 28, 34, 42, 47

2017-10-12

Web/Cart/Checkout calls in REST now make a call to TXN/Orders (POST) at the end of the checkout process. This allows for a plug-in to intercept the Id of the newly created order.

v1251HF53
removed - included in v1251HF54

2017-10-12

For Payment Express, a new "reversalByRefund" property was added to the Payment Gateway configuration. Set to "Yes" to use a Refund transaction type for reversals, or "No" (the default) to use a Void transaction type. Void transaction types are not supported for all acquirers.  Please note that reversing charges by a Void transaction is new functionality for Payment Express and their test environment does not support Void transaction types at this time.  Please contact Payment Express to confirm that your acquirer supports Void transactions.

v1251HF52
removed - included in v1251HF58

2017-09-28

Increase buffer size for PX EMV transactions to resolve a card reader data parsing error which could cause a number of issues such as failing to delete a token or a double charge.

v1251HF51
removed - included in v1251HF58

2017-08-08

If the credit card processor was set to Payment Express, when running the Credit Card Tokenzation and Deletion Utility, tokenized credit card accounts were deleted even when Review Mode was set to yes.

v1251HF50

2017-06-05

Transactions were being declined by First Data if the zip plus four included a hyphen. Hyphens are now filtered (Payment Express).

For Payment Express, the clientType field is now set to "I" for Ecommerce transactions, and includes better handling of NULL postal codes.

v1251HF49
removed - included in v1251HF58

2017-05-11

When a delivery method is selected on the Checkout screen, the cart gets refreshed to insure fees are processed correctly.Improved TRBO handling of IDTech custom configuration files for non-supported devices.

v1251HF47
removed - included in v1251HF57

2017-05-05

When changing the customer number in QuickSale in a mode of sale where the default delivery method is print at home, the email address does not get set properly. Depending upon the prior order(s) in that order session, it could end up as the email address of a prior customer or as null.

v1251HF48
removed - included in v1251HF58

2017-04-26

This hotfix adds an enhancement to createPayment Express tokens without a $1 authorization.

v1251HF46
removed - included in v1251HF58

2017-04-19

This hotfix enables Tessitura client to work with Vantiv triPOS v5.10+

v1251HF45
removed - included in v1251HF58

2017-03-09

Added IDTech reader support for the Samsung Galaxy Tab S2 8" Model: SM-T713

Improved reliability and supportability of the IDTech swiper detection process. Custom configurations that are not currently supported can be used by putting a configuration file called IDT_uniMagCfg_Custom.xml in the root folder of the tablet device.

Fixed issue that was causing some print operations with multiple tickets to fail after printing only a few tickets.

v1251HF42
removed - included in v1251HF57

2017-03-08

Performance improvements have been made to several procedures to improve API performance at high-volume loads.

v1251HF44

2017-03-08

When keying or swiping a credit card, if the number does not pass validation, the credit card number field is now blanked out. This is to prevent situations that could occur where the validation message could continually fire on an invalid credit card number.

v1251HF43
removed - included in v1251HF58

2017-03-02

In the Payment Window, when there was more then one refund present, refunds following the first one might not process properly. Now, all refunds process correctly when more than one refund exists in the Payment Window.

In the Payment Window, when more than one credit card was authorized (purchase or credit) at the same time, a couple of issues might occur. First, each of the authorizations could be recorded to a single credit card in T_CC_SEVER_LOG. Second, credits could process to a single credit card. Now, each authorization is recorded and processed to the correct credit card account.

In the Payment Window, when using Payment Express EMV software, the final transaction message may not have processed properly if multiple messaged were received by Tessitura from the EMV software. Now, the final transaction message is always processed so that the transaction completes properly.

v1251HF41
removed - included in v1251HF58

2017-02-13

For Payment Express, CVV code mismatches are supposed to result in an automatic refund of the transaction. To make this happen properly, we are not sending anything in the CVV field for the refund transaction.

v1251HF37
removed - included in v1251HF58

2017-01-27

In Orders, if the pricing rule set for the mode of sale contained any rules that the current user did not have control group rights to, rules from the set would not fire. Now, user control group rights to pricing rules do not impact the application of rules to an order, as was the original intention.

The last activity date has been updated to use the database getdate() rather than the application server date and time.

v1251HF39
removed - included in v1251HF54

2017-01-18

The manner in which Seat Server connections are made from the SOAP API has been updated to open and close the socket connection immediately.

v1251HF40
includes HF 29

2017-01-17

In a controlled batch where some transactions authorized and some did not upon close, there were 2 issues that could occur when reloading an order or contribution with an authorized payment. First, if Cancel was clicked, the system would incorrectly try to reverse the payment. Second, if the payment was deleted and then Cancel was clicked, the system would reverse the payment but it would remain as a payment in Tessitura. Both these issues have been fixed.

In the Payment Window, when using the “Refund Prior Payment” button for payments originally made through an EMV device, an error may have occurred. This was due to the Merchant ID of the originating EMV payment method not being written to T_CC_SERVER_LOG. Now, the correct Merchant ID is recorded and no error occurs when refunding prior EMV payments.

Adding and releasing a sub package lineitem seats could incorrectly cause a mismatch between sub-packages in a super package, and was permitted to be out of sync on save. Also, reserving a package seat where one of the underlying performance seats was released in the same session was causing all performance seats for the package not to be properly reserved, causing an error on order save.

In a controlled batch with memberships, where one of the transactions was a gift membership, deleting the gift membership entry from the batch would cause the membership information for all transactions to be removed.

v1251HF32
removed - included in v1251HF58

2017-01-09

In the Incomplete Credit Card Transaction report,rows found in T_CC_SERVER_LOG that match rows in T_PAYMENT (which represents successful transactions) are no longer included in the data set.

v1251HF38

2017-01-09

Failed seats in the rollover process were not properly showing areason message in TX_RO_LOG or the report output. This has been fixed. To assist in troubleshooting, constituent id has also been added to the output of the Subscription Rollover data export.

v1251HF36

2016-12-1

Partially paid orders reloaded via the Web API and then changed and completed via API calls could have payment imbalances.

SOAP ClearCart will not unlock orders currently locked from client application or other non-web source.

Made enhancement to best seating logic to reduce deadlocks under heavy load.

When an existing order is processed in SOAP and the prices are reduced due to a pricing rule, the T_SUB_LINEITEM due_amt is updated correctly.

v1251HF35

2016-11-11

This hotfix updates TRBO to version 1.0.3 adds support for the ET50/55.

TRBO now has the ability to reprint tickets from the current order, in the case of printer malfunctions, for example. A new “Reprint Tickets” button has been added to the Signature page. Clicking on this will send the tickets from the current order to the printer again.

In TRBO, when the Locale setting was set to something other than English (en_US), Cart currency references were listed with a “USD” heading. Now, correct currency symbols are used in the Cart in respect to the Locale setting.

By default, the keyboard selected for entry of a postal code is determined by the locale: Numeric for US and Alphanumeric for other locales. It was impossible to change the keyboard to enter a foreign Postal Code when the locale was set to US. This has been changed and a new control is available to switch between keyboards.

Some timeout issues were present in the TRBO application, causing hanging when error conditions occurred. This has been corrected. Also, a new setting has been added to the TRBO application settings screen: “HTML Timeout”, expressed in milliseconds.

v1251HF34
removed - included in v1251HF57

2016-11-04

In Tessitura On the Go Reporting, when selecting report parameters, the parameter dropdowns were not respecting control grouping permissions. Now, the report parameter dropdowns are respecting control grouping permissions.

v1251HF33
includes HF 31

2016-09-30

In the TessituraWeb NLog configuration file, an incorrect‘FallbackGroup’ target was causing log filesto be written to the wrong location. Now, the log files are written to the correct location and the configuration file has been corrected.

v1251HF31
removed - included in v1251HF33

2016-09-30

At times the customer_no was not passed to the payment gateway from SOAP, which could result in a card not being stored and CheckoutEx4 Web API call was resulting in an error updating the expiration date of an existing token.

If the card details were being saved by the Payment Gateway Service, the account id generated in that process was not being saved to T_PAYMENT. (SCRIPT_ID 2)

v1251HF29
script_id 2
removed - included in v1251HF40

2016-09-12

When executing the Cancel/Write Off Pledges utility, memberships associated with affected contributions were not being recalculated or deactivated despite the Deactivate on Adjustment flag being set for the membership organization. Now, memberships will be recalculated or deactivated appropriately when executing this utility for membership organizations with this setting.

v1251HF24

2016-09-12

Tessitura Service was updated to resolve issues with cache invalidation. Cache notifications should now only take place when there is new data.

Resolves an issue where the interceptor framework was repeatedly reloading plugin assemblies when plugins were enabled. (SCRIPT_ID 2)

If an interceptor raised a PRE PluginValidationException on a request, contained in a Batch Request (POST to Service/Batch), the validation error message was not properly formatted within a BatchResponse. This has been fixed. This was uncovered with a change in v12.5 that used batching on the Constituent General Tab within the client application. Custom interceptors that return a validation error to the client were not being handled correctly on save and would crash the application window. (SCRIPT_ID 2)

If an interceptor plugin modified the incoming request content, the plugin operation would succeed but the updated request content was never used in the processing of the request. This was most apparent on the Constituent General tab of the client application, where interceptors updating data would not appear to work on a save for existing constituent data. (SCRIPT_ID 4)

v1251HF27
removed - included in v1251HF54

2016-08-23

Tessitura Payment Gateway Service now supports CVV and AVS for Payment Express transactions.

Tessitura Payment Gateway Service now supports tokenization with payment plans created on Household accounts through SOAP.

v1251HF30
removed - included in v1251HF58

2016-08-16

Message only rules are now deleted when the corresponding product(s) is(are) removed from the cart.

v1251HF20
removed - included in v1251HF54

2016-07-27

This hotfix updates TRBO to version 1.0.2.946 and addresses a number of issues.

Ticket delivery (print/email) is now bypassed for orders that do not contain at least one performance or package.

If local is set to en_US a numeric keypad will appear when Postal Code has focus.

"Sign Here" appears on the signature screen as a gray watermark. Disappears as soon as a signature is started.

Print and email checkbox states will now persist for a session unless the MOS is changed in Order Settings. Initial state will have Print Tickets and Print Receipt checked if the MOS requires ticketing.

Printer no longer required to create a new order when MOS requires printing since tickets can be emailed.

Numeric keypad for Source on Order Settings screen has been updated to have a Done button instead of Next which closes the keypad. Also, touching outside the keypad in the Cart area will close the keypad and no longer cause the application to lock up.

v1251HF28
removed - included in v1251HF57

2016-07-25

At times the customer_no was not passed to the payment gateway from SOAP, which could result in a card not being stored and CheckoutEx4 Web API call was resulting in an error updating the expiration date of an existing token.

v1251HF29
removed - included in v1251HF40

2016-07-11

Authorization codes acquired from TNSPay virtual pin pad transactions were not accepted correctly by the Tessitura client in v1251HF12.

triPOS debit transactions may not return an auth code. If the auth code is not supplied from triPOS, Tessitura will set it to "AUTHOK" so that it can be saved in the payment window.

v1251HF26
removed - included in v1251HF58

2016-07-06

Payment Express refunds were not always producing an authorization code in Tessitura causing issues with saving the transactions to the database and getting cancelled properly.

v1251HF22
removed - included in v1251HF58

2016-07-06

In Reports and Utilities, when running the Membership Update Utility, Last Activity Date was being updated for constituents whose memberships were updated in previous runs of the utility. Now, only constituents whose memberships are updated in the current run of the utility will have their Last Activity Date updated.

v1251HF21

2016-07-06

In the Payment Window, when using a Gift Certificate payment method, gift certificate numbers beginning with the letter C might not be recognized properly. Now, NScan barcodes are ignored while evaluating gift certificate numbers in the Payment Window and gift certificates beginning with the letter C will be recognized properly.

v1251HF18

2016-06-27

T_PAYMENT_SIGNATURE primary key was changed to identity to avoid attempted duplicate ID use, which would result in failed Vantiv triPOS signature captures.

v1251HF15
removed - included in v1251HF54

2016-06-27

If a customer takes close to sixty seconds between each step of a triPOS transaction, the Tessitura transaction could timeout after 100 seconds, while the triPOS transaction could still be completed.In the payment form, if the amount field had focus before pressing the EMV button, the cursor returned to the amount field after the EMV transaction and the amount was editable.Processing an EMV refund with a triPOS terminal now always gives an authorization code of "CREDIT". The authorization code was being passed as a null value from some processors, preventing the order from being saved with a successful refund attempt. When doing a refund by reference, the MOTO Merchant ID was being used in all cases, rather than the Merchant ID associated with the initial charge, which could result the refund not authorizing. This regression bug has been fixed.

v1251HF25
removed - included in v1251HF58

2016-06-20

The Print Server now sends a QUIT command at the end of SMTP messages, which will reduce the length of a SMTP connection. Previously SMTP connections would be dropped after a timeout. This should increase SMTP throughput in high load situations.

v1251HF14

2016-06-03

Tessitura Security application and AP_KEY_RECREATE_2 no longer attempt to encrypt null/bad data and will not drop the temporary encryption key if encryption fails for some reason.As required for PA-DSS certification, added mechanisms for notification of the encryption keys expiration. The notification will appear when logging into the 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. For additional information on regenerating encryption keys see Tessitura Help: Encryption Keys.

Tessitura was using a stored encrypted application password to validate logins. Now a hashed and salted copy of the password is used exclusively.

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.

In the Security Application, when recreating data encryption keys, the process seemed lengthy and included a clean up procedure that was called to reclaim database space. Now, the rewritten process is swifter and eliminates the need for a clean up procedure and the writing of unencrypted data.

v1251HF12
script_id 3
includes HF 2, 3, 4, 5, 6, 9, 10, 11, 13

2016-05-04

Tessitura now sends a required confirm request to TNSPay after receiving a virtual terminal authorization in order to properly capture the payment.

v1251HF10
removed - included in v1251HF12

2016-05-04

The serial port used for a serial cash drawer will be opened when the Order window is opened. It will only be closed when the order window is closed or if an error occurs.

v1251HF9
removed - included in v1251HF12

2016-03-14

In orders, when loading a rollover order without an order date or source, the order was unusually slow to load. Now, the rollover order will load with the usual speed of reloading an order.

In orders, when best seating a line item without a zone selected, rule based fees were not consistently added to the order. Now, rule based fees are consistently added to the order when best seating a line item regardless of zone selection.

v1251HF13
removed - included in v1251HF12

2016-03-06

An intermittent exception was generated when retrieving TR_MACHINE_SETTINGS, resulting in an inability to open the payment window.

v1251HF11
removed - included in1251HF12

2016-02-17

Browser based constituent reports will now open in the default browser for the environment.

v1212HF38

2016-01-28

Pressing +/- on a price type button in any other row than the first was causing the application to hang if a price type from the first row hadn't been pressed first. This has been fixed.

When defaults are loaded, TRBO first checks to see if the default for the organization is defined. If it is not, it will look up the value from the "impresario" defaults.

User Interface updated so that the CVV field will not receive focus when disabled.

v1251HF8
also included in vHF1251HF57

2016-01-25

The version of UP_POPULATE_REFERENCE_METADATA left after migration runs is missing some changes made for TSTATS tables.

v1251HF7

v1250HF27

2016-01-25

The Ticket Sales by Period was not reporting ticket counts properly because the event codes were not properly assigned in the procedure.

v1251HF7

2016-01-25

A call to UpdateSubLineItemPrice marks the SubLineItem to skip pricing. When the SOAP API calls the REST pricing call, which happens on GetCart, these rows along with the SubLineItemDetails should be left untouched. SLI Detail rows are deleted and rebuilt during a pricing call. The issue was that the SLI Detail rows were being deleted but not rebuilt because the SLI was marked to skip pricing. The code has been updated so that the SLI Detail rows are not deleted when the skip pricing flag is set.

V1251HF5
removed - included in1251HF12

V1250HF26

2016-01-14

For triPOS users, automatically detect whether a http proxy server is in use, and if so, use the user's current credentials to authenticate against it. This is necessary for RAMP users.

V1251HF6
removed - included in1251HF12

2016-01-08

Amount and Tendered Amount for QuickSale cash payments are now detethered. The Exact button will set the tendered amount to the amount, even if the amount is different from the total due on the order.

V1251HF4
removed - included in1251HF12

v1250HF24

2016-01-07

Browser based constituent reports will now open in the default browser for the environment.

V1251HF3
removed - included in1251HF12

v1250HF25

2016-01-05

Changes to existing orders were not being sent as a PUT to Txn/Orders/##, instead being sent as a POST to Txn/Orders/.

v1251HF2
removed - included in1251HF12

2016-01-05

AP_CLEAR_MIRROR_FOR_BATCH now identifies direct debit accounts by card prefix rather than account type.

v1251HF1

2016-01-05

When closing the controlled batch generated by Direct Debit billing, accounts associated with the pledge or order being billed, and where the item in question was completely paid off, would be deleted unless in use in a different not fully paid automated billing schedule. This has been fixed.

Accounts stored for General Public transactions conducted in a controlled batch are now deleted when the batch is closed.

If tokenization is on, untokenized accounts stored for transactions conducted in a controlled batch are now deleted when the batch is closed.

v1250HF21 script_id 2

2015-12-10

The code which calculated availability during product searches (from both the client and the API) did not perform consistently well, depending on the environment and the number of performances returned. The procedures have now been optimized for more consistent performance.

v1250HF23

2015-12-09

Adding seats to an order in a later session may cause the order to go out of balance.

Returning resold tickets that were originally donated for resale could lead to out of balance orders.

When exchanging seats, if some of the returned seats were donated seats, the totals were wrong, preventing the order from completing.

Procedure and REST service improvements to increase performance in web transactions.

Custom endpoint (PUT and POST) updated to support culture neutral date format when making calls to the database.

v1250HF18 script_id 5

2015-12-07

When closing a controlled batch that has refunds in it, we have seen cases where the credit card processor does not provide an authorization code on a successful transaction. In these cases, the system treated them as failed authorizations rather than successful and attempting to close the batch additional times would result in additional credits to the customer. Now, a transaction with no auth code but a successful result code is treated as successful.

In automated billing, if there was a problem getting an authorization and the credit card server returned a message that was greater than 87 characters, the error text would not get properly written to T_PLEDGE_BILL2 / T_INVOICE_BILL_DETAIL / T_ORDER_BILL_DETAIL and the relevant billing summary report would not indicate a problem with those transactions.

When automated pledge billing was run with an acknowledgement letter selected, some of the data was not being provided to the acknowledgment function properly. This caused trn_no trn_description, cont_amt, and payment_type to be blank on generated letters. In addition, if there was a failed authorization, subsequent rows would be written with a transaction number related to a failed authorization rather than zero.

v1250HF22

2015-12-07

The Performance Seat Release utility left seats that were already printed unreleased and in a locked status.

v1250HF19 script_id 2

2015-12-04

When closing a controlled batch that has refunds in it, we have seen cases where the credit card processor does not provide an authorization code on a successful transaction. In these cases, the system treated them as failed authorizations rather than successful and attempting to close the batch additional times would result in additional credits to the customer. Now, a transaction with no auth code but a successful result code is treated as successful.

v1212HF37

2015-11-20

The Tessitura client, SOAP API, and REST API no longer check external certificate authorities when using the internal payment gateway certificate included in PGS.

v1250HF20

2015-11-03

Due to the complications of sharing tokens between multiple gateway accounts when Element is the processor, the Payment Gateway will not process Tokenize “T” transactions when multiple account IDs are found and will return an exception with details. Please note that if an Element “default” entry exists, it is not included in the account ID count as this is expected to be a fall back account and should match another entry. This change does not affect Payment Express (Asia Pacific & Canada) tokenization, nor sites with a single Element account ID.

In Element, system reversals and reversals involving encrypted readers were not being handled properly.

In the Payment Gateway, if there was a problem with the transmission of track data for a swiped card, the transaction was rejected by Element due to the absence of track data. Applying this hotfix will cause such a transaction from being processed as a Retail transaction eliminating the error.

An error will now be returned from Payment Gateway Service if a token creation request contains a merchant for which no configuration exists.

For Purchases and Credits if an exception occurs (such as an Element communication error), Tessitura will now attempt a system reversal with Element to ensure that the transaction where the error occurred will not settle.

v1250HF15 script_id 2

2015-11-01

If a membership has no contributions attached to it, its current value when upgrading in Orders will now be calculated by adding the membership and AVC amounts. Please note, manually added memberships do not include a membership or AVC amount and this solution will not affect this kind of membership. This solution primarily pertains to memberships converted from another system.

v1250HF17

2015-10-12

The Pledge Billing report was duplicating authorization requests.

Doing a refund when the card number was picked from the list in the Customer Accounts window resulted in an "Invalid Card" error message.

When adding a credit card account in the account window, if tokenization was off, it was possible to get an error message about not being able to find a payment method for a given payment method group when that error did not actually apply which would prevent the account from being added. This has been fixed.

Order Billing and Invoice Billing using auto-billing were writing transaction and payment rows with an incorrectly rounded payment/transaction amount (14.56 would be written as 15.00, e.g.).

When running billings, if a card was declined, a null object reference error would occur and the billing run would be halted at that point. This has been fixed.

v1250HF8 script_id 6

2015-09-29

Super Package rollovers would fail because it was checking the sub-package incorrectly for mode of sale validation. Note that if the Subscription Rollover Utility is run prior to applying the hotfix the rows indicating an error but no seat numbers from that run will persist in subsequent runs but can be ignored.

v1250HF16

2015-09-24

If a constituent had an existing constituency, a membership level constituency would not be added correctly when adding a new membership or upgrading an existing membership.

When AP_MAINTAIN_CONSTITUENCY deactivates a constituency the end datetime will be set to the current date/time as long as the constituency is currently active. Previously the end date was updated to the current date for existing deactivated memberships.

v1250HF11 script_id 2

2015-09-11

The Printed event for Order History was not being written when a comp sublineitem was printed. This kept the order from being marked for Print at Home delivery by the Print Server indefinitely.

The event Printed in Order Seat History was not being written when printing comp tickets.

v1250HF14

2015-09-10

A regression bug had caused the PluginValidationException to be suppressed.

v1250HF13

2015-09-09

When running the tokenization utility, the act_name field, which holds the name on the card, was blanked out when cards were tokenized. This has been fixed.

v1250HF12

2015-08-31

The Gift Certificate Write Off utility was throwing a foreign key error when run in non-review mode.

v1250HF10

2015-08-31

Orders containing survey data can no longer be loaded in a controlled batch. The Survey window cannot be opened when in a controlled batch.

The Order window Solicitor dropdown was not being populated when the window opened.

v1250HF9

2015-08-12

When returning tickets on the web, the prices were being set to 0 by the pricing call triggered by a call to GetCart. The pricing engine has been updated to skip processing of returned tickets.

When SOAP called REST to price the cart, an error was thrown if a returned ticket was in the cart. This error was being seen when GetCart was called.

v1250HF4

2015-08-11

When using a generic credit card payment method (one without an account type specified), when an account number was specified, either by swiping, typing one in or using the Select Account/New Account button, the payment method would change to a more specific one but certain settings were taken from the generic payment method rather than the new one. The end result could be that it was possible to save the credit card payment without authorizing it. This has been fixed.

When using a card reader with TNS Pay, the card reader window would not process the information returned from the device correctly and would remain open indefinitely rather than automatically closing and relaying the authorisation to the payment window.

v1250HF7

2015-08-07

The procedure WP_GETEXTENDED_ACCOUNTINFO has been optimized to improve the performance of the GetConstituentInfoEx SOAP API method.

v1250HF6

2015-07-16

WP_SAVE_CART was looping when processing on account payments for contributions.

WP_TRANSFER_CART now sets calculate_prices to 1 in T_WEB_ORDER, enabling pricing after the transfer.

v1250HF2

2015-07-09

When SOAP called REST to price the cart, an error was thrown if a returned ticket was in the cart. This error was being seen when GetCart was called.

v1250HF1

2015-07-08

TransferCart will now update the initiator of the order properly based on the most current login.

v1212HF33

2015-05-20

TP_GET_TICKET_ORD_ELEMENTS, the procedure that retrieves data for ticket printing, has been optimized to improve performance when printing lineitems with large numbers of seats.

v1212HF27

2015-05-04

3DSecure verification fields are now url encoded when being passed from Payment Gateway to SecureCXL by default to ensure that special characters are transmitted properly. To turn this off, set urlEncode3dsFields=”No” in the SecureCXL configuration section in the Tessitura Installation Manager in text view.

v1212HF26

2015-04-23

This hotfix allows additional ini settings related to deadlock wait time and retry count as well as changes to ticketing procedures to limit the number seating and order save deadlocks.

v1212HF23

2015-03-20

All performances in a package are now seated as expected when running automated seating.

v1212HF24

2015-03-09

An unusually high number of Price Events was causing TP_GET_ALL_PRICES to return slowly.

v1212HF22

2015-02-23

Card type BIN ranges are now completely governed by the card_mask and prefix in TR_ACCOUNT_TYPE. Previously, the Payment Gateway did additional validation on known BIN ranges, but that validation has now been removed.

v1212HF21

2015-02-20

Merge errors caused by Artifax Integration components have been resolved.

v1212HF20

2015-02-10

The code which ensures that inactive rows are sorted to the bottom of dropdowns had an error in which the sort expression it builds would grow over time. This was not a problem in most places as it is only built once or twice, however this process was called after each order which resulted in a very long sort string and increased sort times. This was especially evident when there were large number of rows in a DDDW, like order category.

When entering QuickSale orders, the credit card account was not being referenced in T_PAYMENT.

In some situations, the client application may hang when attempting to edit performances within an existing flex package.

v1212HF14

2015-02-03

With Gift Aid functionality enabled, saving a change to an existing order with a previously saved Gift Change transaction would fail incorrectly.

v1212HF18

2015-02-02

Deleting a zone in certain facilities was executing too slowly, resulting in timeouts.

v1212HF17

2015-01-21

The GetNFSPackageDetail method did not return price types properly marked for package level offers.

v1212HF15

2015-01-19

FS_GET_DEFAULT_VALUE and FT_CONTROL_GROUPS have been optimized to improve the processing speed of Extractions and User-Defined Output from a List.

v1212HF13

2015-01-16

The v12.1.2 upgrade and install release files included a partial set of Plugin Sample files. This hotfix zip contains a full set of Plugin Samples. There is no update to the Tessitura system.

v1212HF12

2015-01-16

When Subscription Renewal Notices were run for a constituent with a sort name of more than 30 characters, a truncation error would occur.

v1212HF11

2015-01-09

The first update to a new Campaign Expense will now succeed without an error.

v1212HF10

2015-01-08

Running Print at Home with a Max Orders Return value caused the process to time out with large volumes of data. Also the order selection logic has been changed so that the Past Days setting applies to the Order Date in the case of unprinted orders and to the Reprint Request Date in the case of reprinted orders. So, for example, if the Past Days value is set to 4, the server will poll for PAH orders with an order date in the last four days AND for orders where a PAH reprint was requested in the last four days, regardless of the order date.

v1212HF16

2015-01-07

Default client NLog logging level has been changed from Trace, which is the highest verbosity level, to Error.

v1212HF9

2014-12-11

This hotfix reverts SOAP pricing away from CLR/REST to the original stored procedures and improves best seating in some cases.

v12-CLR-OFF

2014-12-02

Random Selections were not working correctly in Extractions and were instead only selecting the first n% ordered by customer_no.

v1212HF6

2014-11-21

In some situations, particularly with Plans of Primary Affiliates, the Portfolio window load time was very long.

v1212HF5

2014-11-21

The FT_GET_PRICES function was not performing optimally in all situations which could lead to issues with slow performance during periods of heavy web API use.

v1212HF4

2014-11-19

If an error occurs in pricing, a line item can be left without a valid due amount. This ultimately could cause an External Exception sending a message to the pole display which crashed the application.

When returning a seat in benevolent mode and then adding additional seats to the order, an error would occur. Example error: nvo_bo_order.uf_price_order_via_service.77: Pricing could not be retrieved for sub line item 2089.

v1212HF1

2014-11-07

Adding, editing or deleting a Gift Aid declaration would hang on larger systems if indexing was recently rebuilt because of an optimization issue in AP_UPDATE_GIFTAID.

v1212HF3

2014-11-05

When setting the AVS flag to Precheck, the Element transaction was getting authorized for $0 and rejected by Element.

v1212HF2