The following table outlines the changes made in AudienceView 7.13.0:
NEW |
Desktop - Batch Event Update Basic The Event Configuration application Events|Batch Update pages (introduced in AudienceView 7.10.0 under AVD-12831) have been extended to include elements found on the Events|Basic page. The Event Configuration application Events|Batch Update|Basic page allows you to add, remove and update the basic information for any set of events, including events from multiple series and multiple venues.
Users start by selecting the fields that they want to update from the 'Available' fields list, and moving them to the 'Update' list. Once the selection is complete, users click the 'Continue' button.
The selected fields are then displayed under single-value fields or multi-value fields sections according to the field type. For single-value fields, users enter the new value for each field. The new value always overwrites existing values. If the new value is left blank, any existing values in that field for the set of events will be removed.
For multi-value fields, users can choose to either Add, Remove or Replace values. If Add is selected, the values are added to whatever values already exist in the field. If Remove is selected, the values are removed from the field. If Replace is selected, the values overwrite all existing values in the field. To access the tool, Events Batch Update Limits must be enabled for the Application Security application Group|Content page's Event Configuration property.
Known Limitations
The field labels in Batch Event Update are managed independently from the field labels on the main event pages. To keep the labels synchronized, any label changes made for the Event|Basic page in Registry application Registry::EN::Business Objects::TSperformanceBO node should also be made in the Event Basic Primitives list.
There is no upfront validation for fields where the acceptable values are dependent on the values in another field. For example the 'Contract' field on an event only accepts contracts which are valid for the organization set in the 'Organization' field. The Batch Event Update tool will allow users to select an invalid contract, but the update to that field will fail when the tool is executed. |
AVD-12845 AVD-12854
|
NEW |
Extract BI queries to JSON. The Business Intelligence JSON Report Extract (text/json) 'Extract Template' has been added, allowing you to extract BI queries in the JSON format. |
AVD-13754 |
IMPROVEMENT |
Update the Event Configuration application Event|Sales Status page The Event Configuration application Event|Sales Status page has been improved so that sales data is more granular. 'In Flight' admissions are now displayed separately from 'Sold' admissions. Columns have been added to display a count of admissions on offers and a count of admissions on hold. The limitations around role access to holds have been removed. Now the 'Held' count will include all admissions that are held and not sold, in flight or on offer, regardless of whether or not your role has access to sell the hold. |
AVD-14173 AVD-14174 |
IMPROVEMENT |
Data Monkey - Allow Data Management jobs to use source files located on HTTPS and SFTP servers. HTTPS Server or SFTP Server can now be selected from the General Configuration application Scripts Definition|Edit page's 'Source Type' dropdown. When the data management job is created, users will be prompted to enter a 'Source File Name', 'Username' and 'Password' when the data management job is created. The 'Source File Name' should be the server name and the path to the source file in the format serverName/pathToFile (e.g.sftp.audienceview.com/SFTPfolder/source.csv). The 'Username' and 'Password' are the valid credentials for the remote server. |
AVD-14338 |
IMPROVEMENT |
Payment Gateway - Clean up payment gateway fields in the Registry. Redundant and unused fields have been removed from the payment gateway nodes. Fields that require specific values are now read-only. |
AVD-14938 |
IMPROVEMENT |
Remove venue restiction section from the Application Security application Roles|Basic page. The ability to restrict venue access by role has been removed from the Application Security application Roles|Basic page. Venue access can still be restricted using the restrict roles section of the Event Configuration application Venue|Basic page.
|
AVD-15095 AVD-15180 |
IMPROVEMENT |
Redcard - The Redcard integration now supports URLs with commas in them, as required by some financial institutions. |
AVD-15233 |
IMPROVEMENT |
API - Add parameters to the TSmapBO::Extract. TSmapBO::Extract can now take the following parameters: •screen_id •seat_id •entered_promo_code_id •promocode_access_code •promocode_access_code_url •clearPromoCodes The behaviour of the promo code parameters is consistent with other calls: •If screen_id or seat_id is specified an event (performance_id) must also be specified. •If screen_id is specified the extracted data is limited to that screen. •If seat_id is specified the extracted data is limited to that seat's screen. •If screen_id and seat_id are both specified, the seat must be on the screen identified by screen_id. •If multiple events are specified (performance_id), data is extracted for all events. Previously, data was only extracted for the first event. |
AVD-15389 |
FIXED |
Pledge Portal - Menu items with absolute URLs do not work/open the link to the URL. |
AVD-15240 |
FIXED |
Updating Price Chart and received Database Unique Key Violation. |
AVD-15255 |
FIXED |
Desktop - On high latency connections, it is possible to submit an order on the Customer Services application Order|Summary page twice, which causes errors. |
AVD-15308 |
FIXED |
Pledge Portal - Article links do not open to articles outside of the pledge portal. |
AVD-15373 |
FIXED |
Online - Deep Linking an event to Pick-a-Seat generates a tampering message. |
AVD-15431 |
FIXED |
Online - Questions are only being displayed once. |
AVD-15492 |
