AudienceView Unlimited 7 Release Notes

Set HTTPS or SFTP 'Target' destination in the Registry

To improve security and usability for HTTPS/SFTP exports, you can now configure HTTPS and SFTP target destination in the Registry, so users can simply select the destination when they schedule an HTTPS or SFTP report or BI. They do not need to to know the server name, user name or password.

Currently, if there are no targets configured in the Registry, users can still enter the information. In a future release, the ability to enter the information will be removed and the only way to export to HTTPS/SFTP will be to have the targets configured in the Registry. If you use these options, we recommend you add your target configurations before the next release.

The targets are configured in the Registry - System::Configuration::Export Targets node.

•Address: The URL of the target server (without https://).

•Label: The name that displays to users in the list.

•Password: The password for secure server access.

•Target: HTTPS or SFTP

•Username: The user for secure server access

If you only have one target it is selected by default when scheduling a report or BI.

The security of the HTTPS/SFTP export was also improved to prevent protocols other than HTTPS and SFTP from being entered in the 'Target' address field.

Make inserting tags in messages easier.

To improve usability, the list of available tags on the Correspondence - Messages|Build page was reduced to the most commonly used tags from the customer contact and customer address records. Fields selected as result members in the BI query attached as the 'Send To' list are also available (to add event-related fields to the message, for example). Other fields like the ones from the message or schedule configuration were removed.

Online - To improve usability and accessibility, the time dropdowns have been removed from the online calendar date picker.

Online date searches assume a time of 00:00 for the start date and 23:59 for the end date.

This change is in preparation for a full replacement of the calendar date picker in an upcoming release.

Improve security with input validation on fields with InfoURL and ImageURL 'Subtypes'.

InfoURL fields typically labelled 'Additional Info' and are designed to store a full URL or a relative path to an article. Now if an invalid value is entered, the following message appears: The <field name> field must contain an HTTPS URL or a relative path to an article.

ImageURL fields are typically labelled as 'Logo' or 'Image' and are designed to store a full URL or a relative path to an image. Now if an invalid value is entered, the following message  appears: The <field name> field must contain an HTTPS URL or a relative path to an image.

Bluefin - Payment processing was temporarily blocked.

Bluefin detected a suspicious set of characters in a customer input field. After consulting with them a new validation has been added, blocking the angle brackets (< and >) from being entered in online fields like contact, address and payment fields.

RedCard - Contactless transactions with the Ingenico Lane 3000 device along with merchant and customer copy of customizable receipts have been certified.

The Ticket Sales by Price Type and Payment Method report updates

The 'Count' column appears in the output when a Sales Date range is selected. It still does not display when payment methods are selected in the criteria, because a single admission may have been paid by multiple payment methods, and it is impossible to provide unambiguous data in this scenario.

The selected criteria also appears on the report output under the report name.

Ticket transfer prep work.

In anticipation of the upcoming ticket transfer feature some changes were made to Correspondence was updated so that messages can be sent to the transfer recipients as well as to the original order customer. A set of 'Ticket Holder' fields have been added to the Customer 'Object' in the Business Intelligence|Criteria and Business Intelligence|Result Members pages. More details will be provided when the ticket transfer feature is released.

Correspondence - Missing email parameter message.

To improve usability and clarity, the alert that appears in Correspondence when required fields are missing from the BI query (Warning 1611: Missing email parameter) has been replaced with a 4274: The Business Intelligence query being used as the data source for this message is missing a required field.

If the BI query is missing an email field, the message explains that either Default Contact Email OR Contact Email OR Organization Contact Email is required.

Removed an unnecessary validation when a message is saved.

Warning 1613: The query is missing result members that are needed for a complete correspondence record. Continue? has been removed.

Generating an invoice/confirmation sometimes resulted in a JavaScript error if Digital Wallet tickets had previously been issued and then all admissions were removed from the order.

RedCard - To ensure mandatory browser fields for 3D Secure 2 authentication are read from client browsers and passed to the payment gateway, fields are validated in the gateway.

The extraction of client browser environment information is now independent of 3D Secure enabled configuration on RedCard payment method.

If any of the field values are empty, the following message appears: Required payment input field not found in the input record. [Browser Screen Color Depth missing].

An allocation error generated when the price type of a paid admission was changed to a zero value price type.

The upgrade process will identify and fix any orders in this state.