AudienceView Connect
 Product Guides   Knowledge Base   Discussions   Support   Annual Conference   Developer Guide Login   Developer Guides  
 
AudienceView Documentation

AudienceView 6.5.1 New Features and Enhancements

Table of Contents | Previous | Next

Desktop Enhancements

Feature Description ID
The current placement of the email marketing Google Analytics parameters in the Registry does not allow you to easily configure parameters on a message-by-message basis. This has been implemented in AudienceView 6.5.1.
If Google Analytics is configured for the Correspondence application, when a link being inserted into a message the link builder displays the 'Campaign', 'Content', 'Medium' and 'Source' fields appear.
For more information, refer to Managing AudienceView's Ability to Use Google Analytics - Correspondence in the AudienceView 6.5.1 Addendum.
The Registry application Registry::EN::Application::Online::Analytics::Email Tracking node has been removed.		 MAINT-459

Online Enhancements

Feature Description ID
Improve the usability of the SVG pick-a-seat map. This has been implemented in AudienceView 6.5.1.
Users can now click and drag the map when they are zoomed in, and they cannot zoom-out lower than 100%.		 CORE-241
With the introduction of the SVG pick-a-seat map, customers selections are no longer retained when they change venue screens. A warning message should be displayed to customers. This has been implemented in AudienceView 6.5.1.
When customers select seats in one venue screen and then attempt to navigate to another screen the following message will be displayed in a pop-up Changing your area or viewing the full map will result in your selections being lost. To retain your selections please add to order. This message is configurable within the Registry application Registry::EN::Application::Online::Pick a Seat node 'Area change warning' field.		 CORE-242

Business Intelligence and Reports Enhancements

Feature Description ID
Make Audit Batch Name available through Business Intelligence. This has been implemented in AudienceView 6.5.1.
The following criteria have been added to the Admissions, Customer and Orders BIs:
  • Create Action
  • Create Application
  • Create Audit ID
  • Create Audit Create Time
  • Create Business Object
  • Create Business Object ID
  • Create Client Address
  • Create Context
  • Create Description
  • Create Override ID
  • Create Result
  • Create Sequence
  • Create Server Address
  • Create Transaction ID
  • Create Session ID
  • Create ID
  • Create Audit Correspondence Detail Link Name
  • Create Batch Name
  • Update Action
  • Update Application
  • Update Audit ID
  • Update Audit Create Time
  • Update Business Object
  • Update Business Object ID
  • Update Client Address
  • Update Context
  • Update Description
  • Update Override ID
  • Update Result
  • Update Sequence
  • Update Server Address
  • Update Transaction ID
  • Update Session ID
  • Update ID
  • Update Audit Correspondence Detail Link Name
  • Update Batch Name
 MAINT-515
MAINT-538

Dataloader Enhancements

Feature Description ID
Conditionally create orders using the Dataloader. This has been implemented in AudienceView 6.5.1.
Logic has been implemented so that if an order does not currently exist in the database, one will be created. If the order does exists, it will be updated		 MAINT-440

AVScheduler Enhancements

Feature Description ID
Revert the AVScheduler improvements that were implemented in AudienceView 6.5.0 (CORE-120) This has been implemented in AudienceView 6.5.1.
The AVScheduler improvements that were implemented in AudienceView 6.5.0 (CORE-120 - Scheduling missed AVScheduler Jobs)) have been removed from AudienceView 6.5.1.		 CORE-240

WebAPI Improvements

Feature Description ID
The WebAPI needs a doWork method to release orders. This has been implemented in AudienceView 6.5.1.
The cancelOrderItem action has been added to the TSorderBO doWork method.		 MAINT-423