AudienceView Connect

AV Community 1.8.0 New Features and Enhancements

AV Community Enhancements

Feature Description ID
Event Widget for Affiliated Websites This has been implemented in AV Community 1.8.
An event widget has been added to the event dashboard in the left-hand pane
under the Promote section. The event widget can be configured in two ways, in various sizes, to allow event owners to embed event widgets into their websites so that customers can purchase tickets directly:
  • Embedded Widget: Adds all of the event’s information directly into your site.
  • Modal Widget: Adds a 'Buy Tickets' button. When customers click the button, the event information will be displayed in a pop-up.
Shibboleth This has been implemented in AV Community 1.8.
For organizations using our Shibboleth integration, AV Community 1.8 includes the ability to use an attribute set on a user’s Shibboleth account to control that user’s access within AudienceView. Any attribute which is passed from Shibboleth to AudienceView can be mapped to a security group on the AudienceView side. For example, access to creating an event owner profile in AudienceView can be controlled by setting an attribute in Shibboleth and configuring AudienceView to read the attribute and set the appropriate security groups when the user account is created. Users without the attribute will not be able to create a profile.
Customers can now belong to multiple groups (the Registry application Registry::EN::Business Objects::TScustomerBO::User::Group node's 'Value' field is multi-select).
RSS Event Feed
This has been implemented in AV Community 1.8.
RSS feeds are a common way for one website to syndicate content from another website. AudieceView's new RSS event feed feature enables you to customize the AudienceView Online event content listings for affiliated websites. For example, a university department with its own website can use this feature to fetch department-relevant event listings from the central university event calendar (AV Community) and display them on the department website, formatting and styling the listing accordingly.
The base URL for absolute URLs is taken from the Content Management application Sites|Basic page's 'Payment Return URL' field (which will be renamed in a future release).
RSS feed includes:
  • The RSS URL builder page makes creating and testing tailored content feeds simple (with on page instructions, plus full help page)
  • Select the feed content by date, search terms, and filter options by:
    • Event owner
    • Result type (event, event Owner, article)
    • Venue
    • Campus
    • Department
    • Genre/sport
    • Any and all of the new event filter options added in this release (AVD-5993)
  • Compliant and extended RSS data output:
    • All standard RSS elements (produces great listings from even a basic RSS reader)
    • Extended AudienceView specific RSS elements (provides affiliate websites everything they need to generate content rich listings in their own format)
  • High performance, template based, event listing service provided for low volume periodic querying of currently active listings (forward compatible with node.JS).
Event Filters This has been implemented in AV Community 1.8.
New filter fields have been added to events to increase an event owner's ability to categorize events. The new fields include:
  • Four single string fields to track attributes like Campus, Faculty and Department
  • Two multi-select fields to track attributes like Event Type or Intended Audience
  • Two two-level hierarchical fields to track Genres and Sub-Genres.
Once event owners have set the values on their events, online users can filter their event search results using any combination of filters.
These configurable fields are available in the event owner portal as well as the Desktop via the Venue Configuration application Performance|Basic page.
A new Filters node has been created in the Registry application Registry::EN::Business Objects::TSperformanceBO node.
When you bind a list to a filter field, the list's 'Key' is displayed and not the list 'Label'. Ensure that you configure the filter-related lists so that the 'Key' values are readable/user-friendly.
Increase default 'Maximum Number of Values' for search filters. This has been implemented in AV Community 1.8.
The default value of the Registry application
Registry::EN::Business Objects::TSarticleBO::Search::Search Filters node's 'Maximum Number of Values' field has been increased from 8 to 16 because the addition of the new event filters exceed the previoius value.

Access Control Enhancements

Feature Description ID
(at-the-door app)
This has been implemented in AV Community 1.8.
Sesame is an application for mobile devices that allows users to manage and service events at the door. Sesame provides the means for event organizers and planners to check-in, scan and manage attendees.
The following preloads have been added for Sesame:
  • New Sesame site (Content Management)
  • New Anonymous Sesame group with basic permissions set in TScontentBO to allow the site and help articles to load (Application Security)
  • New Sesame group (Application Security)
  • New Sesame user which will be set as default the default user for the Sesame site (Application Security)
  • Uses the existing Scanning User role (Application Security)
A Sesame Dashboard report has also been created, and can be accessed viat he Business Intelligence and Reports application.
A BETA version of the Sesame app can be downloaded from:

Security Enhancements

Feature Description ID
PA-DSS requires that user passwords are stored using strong encryption (MD5 is not strong) This has been implemented in AV Community 1.8.
The user password encryption method has been upgraded from MD5 to PBKDF2 (PBKDF2/HMAC/SHA-256). This greatly increases the level of encryption available for stored passwords. For upgrading clients, existing passwords are maintained as-is in MD5, usable for log-in until updated or reset. New, updated and reset passwords will use the stronger PBKDF2 encryption.
All HTML fields containing card numbers, swipe values and expiration dates must have the autocomplete="off" attribute. This has been implemented in AV Community 1.8.
Fields used for credit card swipe data have had an additional HTML directive to not auto-complete. This directs compliant browsers to never store or recall values entered into these fields. This is an extra measure on top of AudienceView's already PCI compliant set of payment security features.

Analytics Enhancements

Feature Description ID

Implement the 'User ID' as the 'Customer Number' in Google Tag Manager.

This has been implemented in AV Community 1.8.
A new field was added to the Google Tag Manager data layer. av.session.user_id. If the user is logged in, the value is the 'Customer Number'; otherwise, if the user is not logged in, the value is undefined.

This change adds support for Universal Analytics cross device tracking.

Payment Enhancements

Feature Description ID

Implement the PayPal Native payment gateway.

This has been implemented in AV Community 1.8.
The preliminary work that was done to implement the PayPal Native gateway has been completed.

Before implementing a PayPal payment method, contact your AudienceView Relationship Manager.

Data Monkey Enhancements

Feature Description ID
Enhance the manageDonations method on the TSorderBO to use names instead of GUIDs. This has been implemented in AV Community 1.8.
The manageDonations method has been modified to accept the appealName and fundName parameters.

Enhance the manageGiftCertificates method on the TSorderBO to use the stored value item's 'Name' instead of its GUID

This has been implemented in AV Community 1.8.
The manageGiftCertificates supports the passing of stored value items by name using the addStoredValueName parameter.