AudienceView Unlimited 7 Release Notes

It is now harder for malicious users to exploit the system to rapidly test large volumes of card payment transactions.

The number of card payment transaction attempts which can be made on a given order is now limited to 6, by default. If the limit is exceeded, the You have exceeded the allowed number of card payment attempts message appears, and the order is discarded.

The limit is configurable by role. We recommend keeping this limit set to 6 or less for any role used online.

The 'Use Terminal?' check box has been added to payments windows.

To eliminate the ambiguity between terminal (payments made via a pinpad/machine) and MOTO (payments made in the Desktop) transactions, the 'Use Terminal?' check box was added. The check box must be selected when processing in-person, electronic payments using any terminal on any of the supported payment gateways.  

You can and should default the check box so it is always selected:

1.Open Application Security from the Desktop.
The User|Search page appears

2.Select the Group tab.
The Group|Search page appears.

3.Search for and select the group taking payments.
The Group|Basic page appears.

4.Select the Attributes tab.
The Group|Attributes page appears.

5.Select TSpaymentMethodBO from the list on the left side of the page.

6.Click 'Add Rule'.
A set of fields appear.

7.Search for and select the Payment Types: Credit Card: Use Terminal payment type from the 'Attribute Name' field, using the format.

8.Enter a T in the 'Default Value' field.

9.Click 'Apply'.
A window confirms that the group was updated.

10.Click 'OK'.

11.Repeat the process for any other payments take through a terminal.
For example, the check box should be defaulted for Debit transactions in Canada.

The 'Use Terminal?' label can be changed using the Registry - Registry::EN::Application::Customer::Order node's 'use_terminal' field.

The Export and Extract workflows in the Desktop have been improved.

Now only the relevant inputs display when the user chooses to Export or Extract target.

The areas affected by this change are:

1.Scheduled Reports

2.Business Intelligence Export function (both Classic and New BI)

3.Business Intelligence Extract function (both Classic and New BI)

4.Export function for configuration objects

5.Customer Biography and Donor Biography

HTTPS and SFTP Export and Extract targets must be set in the Registry.

Work was started in the previous release to improve the security and usability of the Export and Extract functions by adding the HTTPS and SFTP export target configuration to the Registry

Individual users can no longer set the HTTPS and SFTP target details when executing the Export or Extract. HTTPS or SFTP targets must be configured in the Registry before execution.

If no targets are configured in the Registry, the No targets configured for this target type message appears.

For upgrading clients, any existing HTTPS and SFTP target configurations on scheduled jobs with an end date in the future have been migrated to the Registry. The name of the target has been formed from the target type and the server name, plus the user name if there are multiple targets with the same type and server name.

It is easier for customers using the Digital Ticket delivery option to  add their tickets to their Apple Wallets.

When a customer chooses a digital ticket delivery method, and when Apple Wallet is enabled, the Add to Apple Wallet links now display on the order confirmation page (viewOrder.asp) when the order is created.

An unexpected Printer and/or stock selection required message displayed when reprinting an order with an Email delivery method, and where the order contained one or more items which did not have a ticket template or ticket stock configured.

The printing behaviour has been simplified by allowing orders with an Email delivery method  to print without generating the message, even when a template or stock selection is not configured for one or more items in the order.

After running certain reports a database connection could become unstable, and on the next action a 3025 error This record has changed since the last retrieval would appear.

RedCard - 3D Secure payments were causing an error because browser information was not collected when a default payment method was used.

Browser information fields are saved when the order is saved so that the mandatory browser information is sent to the payment gateway for 3D Secure authentication.

Braintree - Online payment plans and saved payments perform 3D Secure authentications conforming PDS2 SCA compliance.