AudienceView Unlimited 7 Release Notes

NEW

Desktop - Update the inputs and icons (e.g. pickers)

Inputs have undergone some visual improvement. Icons next to inputs are now cleaner SVG images and it is now possible to tab correctly with the keyboard through each input and associated icon.

AVD-15631

NEW

Provide the ability to create multiple events using a .CSV source files

One preloaded script called Create Multiple Events Using CSV Source has been added to the General Configuration application Scripts section.

One preloaded script definition called Create Multiple Events Using CSV Source has been added to the General Configuration application Script Definitions section:

Users can then create a Data Management job using the Create Multiple Events Using CSV Source script definition.

The script creates multiple events based on the data provided in the .CSV source file, and data provided in execution fields on the script job. The script will automatically create admissions for reserved seat sections. It does not currently create admissions for GA sections – this is being considered for a future enhancement.

Details for the Source Data:

•The CSV source file can contain any single-value fields from the Event Configuration application Event|Basic page

•Multi-value fields on the Event|Basic page can be set using execution fields on the script job

•The calendar for the events can be set using a collection-type execution field on the script job

•Price, hold and fill values for the events’ reserved seat admissions can be set using three more execution fields on the script job

There is an assumption that, initially, all events in the set have the same values for the multi-value fields and for the calendar, and that all admissions for the events in the set have the same price, hold and fill values.

In cases where the multi-values or the calendar differ across the set of events, there are two options – either split the source data into separate pieces, where in each piece the values are the same, or use the Event Configuration application Events|Batch Update pages to update the events after they’ve been created.

In cases where the price, hold and fill values differ across the set of events, they can be updated after the events have been created, using the Admissions Management UI.

Performance:

•During performance testing, it was discovered that the script performed reasonably well for up to 1,000 events in a 792 seat venue (10 minutes) and 1,000 events in a 10,000 seat venue (2-3 hours); however, with 10,000 events in a 792 seat venue, the script took over 12 hours, and for 10,000 events in a 10,000 seat venue, the script failed. Until we can resolve those performance issues, we recommend limiting each execution of the script to a maximum of 2,000 events.

Limitations:

•Due to a defect (AVD-13967), the execution fields displayed on the Utilities application Data Management|Schedule page are not sorted correctly.

•Do not exceed 2,000 events in each script execution.

•The script creates admissions for reserved seat sections (sections with seats defined), but not for GA sections (sections with a GA capacity). Admissions for GA sections can be added after the events have been created using the Events|Batch Update|General Admissions page.

AVD-16033

NEW

Provide the ability to add correspondence codes to existing customers throught a script

The new Correspondence Load script adds correspondence codes to a set of existing customers, based on data provided in two .CSV source files, and data provided in execution fields on the script job.

Details for the Source Data:

•The parent .CSV source file contains the correspondence codes and their descriptions

•The child .CSV source file contains a customer identifier and the correspondence code to add to that customer

•An execution field on the script job is used to define which value is used to search for the customer (either 'Customer Number' or one of the three 'Legacy Account Number' fields)

•Two more execution fields are used to set the 'Default Correspondence Type' and the 'Correspondence Status'

•Sample source files are provided as part of the release.

Limitations:

•If a customer in the customer source file can't be found, or if a correspondence code in the customer source file is not defined in the correspondence source file, the record will fail silently (i.e. no error will be logged).

AVD-16110

NEW

Provide the ability to update values in customer marketing data fields based on data provided in a CSV source file.

The new Update Customer Marketing Data script and script definition updates customer marketing data field.

The source file should contain one row per customer. It includes a customer identifier column with the header customer, which is expected to contain the 'Customer Number', 'Legacy Account Number 1', 'Legacy Account Number 2' or 'Legacy Account Number 3'.

The 'Customer Identifier' execution field in the script definition determines which of the four fields will be used to look up the customer. The default value for the field is 'Customer Number'.

The source file can also include columns for any single-value customer marketing data fields (i.e. any of 'Marketing Data [1-50]', 'Currency [1-10]', 'Date [1-10]' and 'Fixed Integer [1-10]'). Multidata fields are not supported by this script.

AudienceView field names must be used as column headers (e.g. data1, currency1, date1, fixed1). For each column in the source, the supplied value will overwrite the existing value in that field. This includes blank values, so if there is a data3 column in the source and the source value is blank, the existing value in data3 will be overwritten with the blank value.

The customer is expected to exist in the database; if it does not then that row will be skipped and an error will be logged.

Date values should be provided in 2016-01-31 format. If the date field has been configured to store date and time, standard format (2016-01-31T13:45:50.987) can be used.

Limitations:

•The marketing data fields that are being updated are expected to be configured as writeable. If fields are not configured as writeable, the update will fail silently with no error logged. This limitation is being tracked as AVD-13585.

AVD-16248

IMPROVEMENT

Email Marketing/Online - Add Mailchimp parameters to analytics_allowedElements.inc.asp to allow MailChimp tracking

The following MailChimp tracking parameters have been added:

•mc_cid

•mc_eid

•mi_u

AVD-10960

IMPROVEMENT

Convert the Performance Popularity report from XSL to JavaScript, and renamed Event Popularity.

The Event Popularity report (formerly the Performance Popularity report) has been converted to JavaScript. The labels can be configured in the Registry application Registry::EN::Application::Business Intelligence and Reports::Report Labels::Event Popularity node.

AVD-11831

IMPROVEMENT

Convert the Wrap report from XSL to JavaScript.

The Wrap report has been converted to JavaScript. The labels can be configured in the Registry application Registry::EN::Application::Business Intelligence and Reports::Report Labels::Wrap node.

As part of this work, the following issues are deemed resolved:

•AVD-1984: Wrap report issues

•AVD-4902: Wrap report on performance short description gets idispatch error Major - Major loss of function.

•AVD-5094: Wrap report displays iDispatch errors with when running with a date range Major - Major loss of function.

•AVD-8287: Wrap report - the 2 hold options do not work at all Major - Major loss of function.

•AVD-11031: Wrap report - Performance column is blank when it includes a performance where all seats have been returned Major - Major loss of function.

•AVD-14875: Wrap report - Comp count and Charge amount calculations are incorrect Major - Major loss of function.

•AVD-16695: Wrap Report pdf overlapping issue

•AVD-16696: CLONE for 7.0 - Wrap report producing different results in 6.3 vs 5.1

•AVD-16697: BI Report-Wrap Report-An Error Message could be shown when using the filter of Report On: Series

•AVD-16699: Wrap Report (all reports with charges output) should have selectable charges as other reports​

•AVD-16700: Incorporate exchange record and transaction state into Wrap report SQL

AVD-11834

IMPROVEMENT

Desktop - Add 'Sort By' and 'Sort Order' fields to the 'Article Type' Template with Search.

The 'Sort By' and 'Sort Order' fields have been added to the Content Management application Articles|Basic page when Template with Search is selected from the 'Article Type' dropdown. This allows users to sort Template with Search articles the same way that Articles with Search can be sorted.

AVD-13347

IMPROVEMENT

Consolidate the multiple script definitions available for the Order Load and Customer Load scripts into single script definition for each script.

The script definitions have now been consolidated into one script definition for each script. Each script definition can handle any combination of source files.

There is an outstanding defect when using all of the available source files at the same time - AVD-16861. This defect existed prior to the consolidation.

AVD-13573

IMPROVEMENT

API - Added the new addBundleGifts doWork method to the TSOrderBO

The new parameters are:

•bundleName - The name of the bundle

•bundleID - Bundle Unique Identifier (GUID)

•giftName - The name of the gift

•quantity - The number of gifts to add to bundle

•appealName - Appeal Name to use

•fundName - Fund name to use

•Donation::* - Group of Gift fields to be set on the newly added gifts

•Fund::* - Group of Funds fields to be set on the associated funds for the newly added gifts

The error codes that can be thrown from this doWork method are:

•4004

•4336 - This is a new error code that is thrown when the supplied gift is not configured for the bundle, stating, The Gift is not available in the bundle.

•5579 - The description has been updated to You are attempting to load a Gift that does not exist.

•5594

AVD-15555

IMPROVEMENT

API - Added new addBundleItems doWork to TSOrderBO

The new parameters are:

•bundleName - The name of the bundle

•bundleID - Bundle Unique Identifier (GUID)

•itemName - Miscellaneous Item name

•quantity - Miscellaneous Item quantity

•option - Miscellaneous Item option

•price - Historical Pricing

•Item::* - Group of Miscellaneous Item fields to be set on the newly added Items

The error codes that can be thrown from this doWork method are:

•4004

•4335 - This is a new error code that is thrown when the miscellaneous item given is not configured for the bundle, stating The miscellaneous item is not available in the bundle.

•4337 - This is a new error code that is thrown when the caller provides both the Bundle ID and the name on the request, stating Both Bundle ID and Bundle Name parameters were provided. Only one is allowed per request.

•5520 - This description have been updated to You are attempting to load a miscellaneous item that does not exist.

•5521

•5522

AVD-15556

IMPROVEMENT

API - Added all of the parameters that are available for manageItems, manageDonations and getBundleBestAvailable doWorks to addBundles.

This allows ASP or webAPI to make calls to all three doWorks as a parameter to the addBundles. Any of the parameters that are required for these doWork calls as parameters to the addBundles call.

AVD-15964

IMPROVEMENT

Update the Order Load Script to use two separate source files.

For both usability and performance improvement reasons, the Order Load script has been updated to use two separate source files for admissions instead of one.

One source file, admission_source_best_available, is used for adding admissions using best available logic. The user supplies a quantity, and optionally a price zone and section.

The second source file, admission_source_by_seat, is used for adding admissions using specific seat locations. The user supplies the section, row and seat.

If necessary, both types of source file can be used within the same script job.

AVD-16309

IMPROVEMENT

API - Added the new setPrimaryEntity doWork method to TSsearchBO

The new parameter:

•primaryEntity - The name of the search Object

The error codes that can be thrown from this doWork method are:

•Warning 4332 TSERR_SEARCH_PRIMARY_ENTITY_CHANGE_NOT_ALLOWED: Once a primary entity has been set, User is no longer allowed to change it.

•Error 4333 TSERR_SEARCH_PRIMARY_ENTITY_INVALID: If the primary entity provided does not exists or is invalid.

•Error 4334 TSERR_SEARCH_PRIMARY_ENTITY_NOT_SET: All of the TSsearchBO doWork methods are now throwing this error, if there is no primary entity set when they are called.

AVD-16399

IMPROVEMENT

Data Management - Prevent scheduled script jobs from being executed on the Utilities application Data Management|Schedule page at the same time.

The 'Execute' button on the Utilities application Data Management|Schedule page is only displayed if the 'Report Schedule Types' is set to 'Unscheduled'.

AVD-16489

IMPROVEMENT

Desktop - Add a user-friendly message to the seat maps when an event is entirely general admission.

When all of the admissions for an event are general admission there is no seat map to display. The message that was previously displayed when users tried to access a map for this type of event (message 6197) has been updated to more accurately reflect the scenario. It now says This event has no reserved seat admissions, so there is no map to display.

AVD-16508

IMPROVEMENT

Desktop - Update the 'Best Section Option' field on the Event Configuration application Venue|Basic page.

The usability of the 'Best Section Option' field on the Event Configuration application Venue|Basic page has been updated in the following ways:

1.The field label has been changed to 'Default Screen' to better reflect the function of the field.

2.The list of values for the field has been updated in the following ways:

oThe All option has been changed to Screen with Best Available Open or Held Seat

oThe None option has been changed to No Default Screen

oThe On Hold option has been changed to Screen with Best Available Held Seat

oThe Open option has been changed to Screen with Best Available Open Seat ​

3.The name of the list used for the field has been changed from best_section_options to Default Screen Options, and has been converted to a system list so that the key values cannot be updated.

4.When creating a new venue, the field now defaults to Screen with Best Available Open or Held Seat (functionally the same as the blank value in earlier versions).

5.The field is now required.

This also fixed an issue where data was not being displayed on the Event Configuration application Events|Ticket Usage page if the venue's 'Best Section Option' was set to None.

AVD-15721

AVD-16513

IMPROVEMENT

The names and descriptions of many script definitions have been updated to make them more consistent and informative.​

AVD-16578

IMPROVEMENT

Data Monkey - Add a list of customer identifiers for scripts that look up customers.

A list was added to the 'Customer Identifier' field for the following script jobs to improve usability:

•Order Load

•Correspondence Load (new in this release)

•Update Customer Marketing Data (new in this release)

AVD-16580

IMPROVEMENT

Add the ability to create new languages in the Registry.

An Add Language section was added to the Registry's Utilities tab. It contains a list of source languages that includes the existing languages and a list of target languages.

Upon completion of the command (currently takes 30 minutes to complete) a new language entry with the target name is created in Registry. That entry duplicates the language tree from the source language.

The new language tree is available immediately for browsing.

AVD-16621

IMPROVEMENT

Performance/Desktop - Remove the 'Fill Zone' option from the Utilities application Renewals|Seating page.

As part of our performance improvement program, the 'Fill Zone' option has been removed from the Utilities application Renewals|Seating page. Users who need to target a specific set of seats when using one of the best available 'Seating Options' can still select specific price zones or hold types.

AVD-16723

FIXED

Desktop - Renewing a gift to an offer in the Utilities application when the gift is configured with multiple appeals or multiple funds generates an error.

AVD-10558

FIXED

Payment Methods - Changing the 'Payment Usage' dropdown from Purchase to Settlement on the General Configuration application Payment Method|Basic page disables all of the payment methods from all events.

The 'Payment Usage' dropdown now becomes read-only when the payment method is initiall created.

AVD-10737

FIXED

Online - An error occurs when adding a bundle containing miscellaneous items to the shopping cart was failing with an error.

AVD-14171

FIXED

Online - When hovering over the 'LogIn' button, Log Out displays

AVD-15604

FIXED

Desktop - When an event has multiple general admission allocations, and the quantity of one of the allocations is reduced below the number of tickets sold from that allocation sometimes causes tickets to be deleted from another allocation.

When a user tries to reduce the allocated admissions quantity, the system:

1.checks to see how many admissions in that allocation have been sold; then

2.if the sold count is greater than the new quantity, does not delete any admissions, and presents message 6214 to the user; or

3.if the sold count is less than or equal to the new quantity, deletes admissions from that allocation (and not from any other allocation).

AVD-15952

FIXED

Payments - 'Card Holder Name' is not inheriting the 'Customer Name'.

When creating an order, the 'Card Holder Name' will carry forward for swiped payments and scheduled payments.

For keyed payments, the customer name will carry forward.

AVD-16223

FIXED

Online - Promo code limits and price type limits do not refresh when users clear their shopping carts.

AVD-16348

FIXED

API - Remove the fillValue doWork parameters from TSOrderBO and TSOfferBO methods.

AVD-16392

FIXED

Bluefin - Declines are appearing as Failures in the Payment Gateway Transaction report.

Previously, all AVS, CVV and other failures were set to Failure. Bluefin now distinguishes between transactions that are true Declines versus those that are rejected for AVS or CVV failure.

AVD-16475

FIXED

Bluefin - When saving a payment method to a customer on the Customer Services application Customer|Basic page, the Registry nodes are not behaving as expected.

AVD-16507

FIXED

Printing - Client/Local printing is not working.

AVD-16527

FIXED

Renew the Java code signing certificate used for client/local printing.

AVD-16557

FIXED

Unable to process scheduled ACH payments via the Scheduled Payment job.

The ACH agreement flag was being validated against an already accepted payment. The unnecessary validation has been removed.

AVD-16592

FIXED

Bluefin - The Merchant ID field on payment methods using Bluefin are not transmitted correctly.

You can configure a Group in Bluefin and then apply the same group to the 'Merchant' field on the General Configuration application Payment Methods|Basic page. The value should be a single, alphanumeric term with no spaces.

This allows for reporting on Groups in Bluefin.

The 'Group Name' from Bluefin should be added to the 'Merchant' field on the payment method. Do not use the Bluefin assigned Group ID.

The group will be available on transaction records in Bluefin in the download .CSV, and through the search screen as criteria.

AVD-16619