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

AudienceView 6.8.0 New Features and Enhancements

Table of Contents | Previous | Next

Point-of-Sale (POS) Interface

Feature Description ID
Implement a point-of-sale (POS) interface This has been implemented in AudienceView 6.8.0.
A POS system has been implemented allowing users to sell concessions and merchandise quickly and easily though a touchscreen-friendly interface. Cash or credit card payments can be accepted using existing AudienceView payment systems. The POS system can be deployed on a wide range of tablets, laptops and dedicated POS terminals.		 AVD-1071
AVD-1083

DataMonkey

Feature Description ID
Add 'Export' buttons to configurable items. This has been implemented in AudienceView 6.8.0.
'Export' buttons have been added to all configurable items within the system, allowing you to extract configurations from an older version of AudienceView and then import them to upgraded versions.		 AVD-2677
Improve the dataloader and XSL templates. This has been implemented in AudienceView 6.8.0.
The DataMonkey has been introduced to provide a high-performance import and export interface powered by a JavaScript engine.
The XSL Template pages in the General Configuration application has been renamed/updated to Script, allowing you to create any number of scripts that can be used to manipulate data.
The Script Definitions page has also been added to the General Configuration application, allowing you to define sources that will be used with the scripts.
The dataloader available in the Utilities application has been replaced with the Data Management pages.		 AVD-2059
AVD-2726
AVD-2917

Desktop Enhancements

Feature Description ID
Convert the Confirmation Order Invoice template to JavaScript. This has been implemented in AudienceView 6.8.0.
The Confirmation Order Invoice template has been converted from XSL to JavasScript.		 AVD-36
Localized number, currency and date formatting. This has been implemented in AudienceView 6.8.0.
You can now define the language, country and any special variant preferences that you want to see in your user interface.
The Offer Confirmation Email, Order Confirmation Email and Order Failure Email templates have been converted into JavasScript. These invoices render localized values where possible. When a calculation is being done, a standard formatting is used ($#,###.00).
The Registry::EN::Primitives::Subtypes node has been added. The 'Format' dropdown has also been removed from the various calendar references in the Registry an has been replaced with a 'Subtype' dropdown.
The currency code for Canadian dollars has been changed from CDN to CAD to align with the ISO 4217 Currency Codes.

For more information, refer to Localization in AudienceView and Defining Date and Time Display Formats.		 AVD-26
AVD-27
AVD-34
AVD-37
AVD-38
AVD-39
AVD-56
AVD-433
AVD-435
AVD-437
AVD-438
AVD-439
AVD-440
AVD-443
AVD-445
AVD-446
AVD-451
AVD-454
AVD-455
AVD-456
AVD-457
AVD-459
AVD-460
AVD-463
AVD-464
AVD-465
AVD-466
AVD-467
AVT-9533
Add 'Category' fields to performances and bundles and make the 'Category' field from all other searchable/sellable products multi-select. This has been implemented in AudienceView 6.8.0.
  • A multi-select 'Category' field has been added to the following pages:
    • Venue Configuration application Performances|Basic
    • Product Configuration application Bundles|Details

      Selecing the Category option from the Content Management application Articles|Criteria page when defining online search criteria will now use the new 'Category' fields instead of the 'Performance Group' and 'Bundle Group Name' fields respectively.
  • The 'Category' field on the following pages is now a multi-select field:
    • Product Configuration application Stored Value Items|Details
    • Funds Management application Gifts|Details
 AVD-395
Gate Management
  • The Venue Configuration application Venue|Gate page has been updated to allow you to specify which seats, rows, sections and price types can access a particular gate, and the time frame in which they will be granted access.
  • The Venue Configuration application Seat Management|Gate page has also been added so that performance specific gate access rules can be configured.

    For more information, refer to Working with Gates and Managing Performance Specific Gates and Access Rules.
 AVD-413
Open AudienceView applications to fit the full screen. This has been implemented in AudienceView 6.8.0.
When an application is opened from the AudienceView Desktop, the window opens to fit the full screen.		 AVD-504
Implement new web widgets in Content Management and allow users to set widget parameter a corresponding 'Context Type' dropdown. This has been implemented in AudienceView 6.8.0.
The following widgets have been added to the Content Management application: 		AVD-506
AVD-2864
Determine the page that loads when the 'Next Customer' button is clicked in the Customer Services application. This has been implemented in AudienceView 6.8.0.
The 'Next Customer Landing Page' field has been added to the Application Security application User|Preferences and Roles|Preferences pages and the Registry application System::Configuration::Preferences node. This field allows you to define the page that users will be redirected to when the 'Next Customer' button is clicked. While this field can be set to any page within the Customer Services application, it is recommended that you only set it to one of the following:
  • bundleSelect.asp
  • customerSearch.asp
  • giftsSearch.asp
  • miscItemsSearch.asp
  • offerSearch.asp
  • orderSearch.asp
  • seatSearch.asp

    The 'Next Customer Landing Page' field is case sensitive.
 AVD-507
Add the Customer|Activities page and improve the Customer|Calendar page in the Customer Services application. This has been implemented in AudienceView 6.8.0.
A new Customer|Activities page has been added to the Customer Services application. This page allows you to see the following interactions that have taken place with the customer in a single view:
  • Activites: All of the interactions that have taken place with the customer.
  • Notes: The notes associated with the customer.
  • Correspondence: All of the correspondence that has taken place with the customer. Calls can also be logged using this section of the page.
  • Offers: All of the offers available to the customer.
  • Opportunities: All of the opportunites associated with the customer.

    It is also possible to set the Customer|Activities as the default page that will open when a customer is loaded via the Application Security application User|Preferences and Role|Preferences pages (and globally via the Registry).

    The Customer Services application Customer|Calendar page has also been improved to show the above interactions.

    For more information, refer to Customer Services - Customer|Activities Page and Customer Services - Customer|Calendar Page.
 AVD-510
AVD-801
Optomize the column widths/spacing of the Venue Configuration application Price Charts|Pricing page. This has been implemented in AudienceView 6.8.0.
The columnn widths Venue Configuration application Price Charts|Pricing and the field sizes have been improved to make the page easier to read when there are multiple price zones and price rows		 AVD-583
Add a way to navigate through the Venue Configuration application Price Charts|History|Details page without returning to the Price Charts|History|Search page. This has been implemented in AudienceView 6.8.0.
Previous and Next arrow buttons have been added to the Venue Configuration application Price Charts|History|Details page.		 AVD-584
AVD-819
Add a way to navigate through single performances in Venue Configuration application Performance Management pages without returning to the Performance Management|Search page. This has been implemented in AudienceView 6.8.0.
When a single performance has been selected, Previous and Next arrow buttons have been added to the following pages:
  • Performance Management|Seats
  • Performance Management|Price
  • Performance Management|Hold
  • Performance Management|Best Available
  • Performance Management|Model
 AVD-585
Make the 'Type' field on a saved ticket template editable. This has been implemented in AudienceView 6.8.0.
The 'Type' field a saved ticket template (General Configuration application Tickets|Basic page) is now editable, allowing you to modify the ticket template 'Type' and then save a copy ('Save Copy' button) of the ticket template.		 AVD-586
Display the payment authorization code and the payment terminal in payment summary bar. This has been implemented in AudienceView 6.8.0.
Once a payment has been processed on the Customer Services application Order|Summary page, the payment's 'Authorization Code' and 'Payment Terminal' are displayed in the payment summary bar. This prevents you from having to expand the payment section to see this information.		 AVD-605
Highlight loaded performances This has been implemented in AudienceView 6.8.0.
When a performance has been loaded in the Customer Services application, when you return to the Seat|Search page the currently loaded performance is highlighted in red.		 AVD-607
When series changes are pushed down to performances, unchanged data is updated. There needs to be a way to specify the information that is pushed down to avoid performances issues. This has been implemented in AudienceView 6.8.0.
Check boxes have been added to the Select Performances dialog box that appears when the 'Update Performances' button is clicked on the Venue Configuration application Series pages.
The following categories can be selected and pushed down to the selected performance(s):
  • Associations: Information defined in the Series|Basic page's 'Association' dropdown.
  • Calendar: Information defined on the Series|Calendar page.
  • Delivery Methods: Information defined in the Series|Basic page's 'Allowed Delivery Methods' field.
  • Limits: Information defined in the limits section of the Series|Limits page.
  • Eligible Passes: Information defined in the Series|Basic page's 'Passes' field.
  • Payment Methods: Information defined in the Series|Basic page's 'Accepted Payment Methods' field.
  • Performance Details: Information defined in the following areas of the Series|Basic page:
    • details section: 'Merchant Description' and 'Sales Type' fields and 'Producer' and 'Ticket Template' dropdowns.
    • performance data section: 'Options' field.
    • series URLs section: 'Additional Info', 'Logo 1', 'Logo 2', 'Upsell Article' and 'Add-on Article' fields.
 AVD-1545
AVD-1798
Meta Tags by Site/Article The Sites|Applications and Articles|Applications pages have been added to the Content Management application. You can configure a Google Analytics account for each site/article so that analytics reporting data can be easily segmented. Each AudienceView site can have its own analytics account and its own analytics reporting dashboard so that specific site usage statistics and conversion rates can be gathered.
The new pages also allow you to configure metadata globally at the site level and more granularly at the article level. These meta tags can be general purpose (e.g. keywords) or specific to a third party integration (e.g. Facebook).
The META Tags list has also been added to the General Configuration application, allowing you to add additional meta tag types.
For more information, refer to the following sections: 		AVD-1598
AVT-6536
Add ability to send blind carbon copies (BCC) of order confirmation emails. This has been implemented in AudienceView 6.8.0.
You can configure an email address to receive blind carbon copies (BCC) of order confirmation emails using the Registry application Registry::EN::Business Objects::TSorderBO node's 'confirmationBCC' field. This can be used to help easily handle customer services issues by allowing you easily verify what was sent to customers. Only order confirmation emails will be sent to the defined email address.		 AVD-3355
AudienceView Desktop dashboards This has been implemented in AudienceView 6.8.0.
The AudienceView Desktop has been redesigned, and can display graphs, gauges and lists to give users an overall view of various aspects of their business. Four dashboards have been implemeted: Performance Sales, Overall Sales, Fundraising and Notes. Dashboards are configured through the Business Intelligence and Reports application. The dashboards are mobile responsive.		 AVD-1987
Creating renewal orders via the Utilities application is causing the system to timeout. The 'AutoCommitFrequency' field in the Registry application System::Application node has been modified to also control the creation of renewal orders in addition to controlling the sending of email messages. During large batches of renewal order creations, the original large transaction will be auto-committed as specified by the 'AutoCommitFrequency' setting into smaller transactions to prevent the loss of renewal order records in the event of rollbacks. The default setting is 10. A 0 indicates that the Auto-Commit functionality has been disabled.
For more information, refer to Setting the Auto-Commit Frequency.		 AVT-6848
QAS Pro On Demand Integration As an additional billable service, QAS Pro On Demand has been integrated with AudienceView 6.8.0.
For more information regarding the QAS configuration, refer to Configuring AudienceView to use QAS Pro On Demand.		 AVT-7291
Goals and Opportunities This has been implemented in AudienceView 6.8.0.
It is now possible to set donation opportunity forecasts against customer accounts, and set fundraising goals against programs, campaigns, appeals and funds.
For more information, refer to Setting and Managing Fundraising Goals and Setting and Managing Customer Donation Opportunity Forecasts.
The notes section of the Funds|Details page has been removed and a new Funds|Notes page has been created.
Funds and Programs and have been added to the BI 'Object List' to allow you to pull information.
It is no longer possible to create a campaign or an appeal without having a parent program or campaign respectively.		 AVT-9471
AVT-9472
AVT-9519
AVT-9521
AVT-9526
AVT-9527
AVT-9528
AVT-9543
AVT-9544
AVT-9570
AVT-9573
If two or more customer accounts share the same email address, email marketing messages are being sent to the address more than once. This has been implemented in AudienceView 6.8.0.
By selecting Remove duplicate addresses from the 'Message Delivery Options' field on the Correspondence application Message|Basic page when an email message is sent, email addresses that are associated with more than one customer account will only receive the email once.		 CORE-1
'Legacy Account Number 2' and 'Legacy Account Number 3' fields and BI options have been added. This has been implemented in AudienceView 6.8.0.
'Legacy Account Number 2' and 'Legacy Account Number 3' fields have been added to the Customer Services application Customer|Basic page. They have also been added to both the Customer and Order business intelligence objects used via the Business Intelligence and Reports application Business Intelligence pages.		 CORE-4
TScurrency should allow negative values. Currently, TScurrency assumes that the minimum value for any currency primitive is zero if not specified. This has been implemented in AudienceView 6.8.0.
TScurrency does not enforce minimum value of 0 if a minimum value is not specified.		 CORE-7
CORE-44
Promotions on gifts. This has been implemented in AudienceView 6.8.0.
Promotions can now be associated with gifts via the Funds Management application Gifts|Calendar page's 'Promotion' field; however, you cannot currently report on promotions on gifts.		 CORE-67
Add 'Payment Methods' to gifts This has been implemented in AudienceView 6.8.0.
The 'Payment Method' field has been added to the Funds Management application Gifts|Details page, allowing you to determine the payment method(s) that can be used to purchase the gift.
If an order contains multiple items with different payment methods, only the payment methods that all order items have in common will be available. For example, if an admission has three payment methods available to it (i.e. Cash, Visa and MasterCard) and a gift has one payment method available to it (i.e. Visa), then only the common payment method(s) (i.e. Visa) will be available on the order.		 CORE-69
Enhancements to the Find Performance dialog box This has been implemented in AudienceView 6.8.0.
The following search fields have been added to the Find Performance dialog box, enabling you to further filter performance searches:
  • Day of Week: Enables you to filter the search based on the day of the week on which the performance falls.
  • Performance Type: Enables you to filter the search based on the performance type.
  • Price Chart: Enables you to filter the search based on the price charts that are assigned to the performance.

    The search performances section can also be collapsed so that more of the seach results can be viewed.
 CORE-91
Add 'Category' fields to performances and bundles and make the 'Category' field from all other searchable/sellable products multi-select. This has been implemented in AudienceView 6.8.0.
  • A multi-select 'Category' field has been added to the following pages:
    • Venue Configuration application Performances|Basic
    • Product Configuration application Bundles|Details

      Selecing the Category option from the Content Management application Articles|Criteria page when defining online search criteria will now use the new 'Category' fields instead of the 'Performance Group' and 'Bundle Group Name' fields respectively.
  • The 'Category' field on the following pages is now a multi-select field:
    • Product Configuration application Stored Value Items|Details
    • Funds Management application Gifts|Details
 CORE-329
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.8.0.
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.
The Registry application Registry::EN::Application::Online::Analytics::Email Tracking node has been removed.		 MAINT-459

Online Enhancements

Feature Description ID
Decline partially accepted offers. This has been implemented in AudienceView 6.8.0.
If an offer is configured with a 'Redemption Type' of Partial (Customer Services application Offer|Summary page), and the offer is partially accepted a Decline Remaining link will appear in the next to the offer in My Account. If the offer has not been partially accepted a Decline Offer hyperlink will appear.
When the remaining seats on an offer have been declined, the 'Status' is set to Partially Accepted and Declined and the declined seats are released from the offer.
The new 'State' is available in Business Intelligence.		 AVD-1
AVD-667
Spotlight internal messages. This has been implemented in AudienceView 6.8.0.
Internal messages are displayed in customers' Message Centres within My Account. You can call attention to a particular message so that customers become aware of it as soon as they log into AudienceView Online. For example, if your organization's customer account requirements have changed, you can prompt customers to update their accounts with the new information.
For more information, refer to Spotlighting an Internal Message.		 AVD-390
AVD-392
Add support for Google Adwords' gclid (Google Click ID) parameter. This has been implemented in AudienceView 6.8.0.
Google Adwords' gclid (Google Click ID) parameter is now supported when Google Analytics is enabled. For more information, refer to the Google help article Tag your AdWords Destination URLs.		 AVD-508
Re-implement the 'Continue Shopping' button. This has been implemented in AudienceView 6.8.0.
The 'Continue Shopping' button now appears in the upper left-hand corner of the shopping cart. When it is clicked, users are taken to the default.asp page where they can search for and add additional items to the shopping cart.		 AVD-520
Google Tag Manager integration This has been implemented in AudienceView 6.8.0.
Google Tag Manager allows you to add marketing tracking to your websites, making it even easier to do very advanced tracking without advanced scripting.		 AVD-642
Update the Flash Map to SVG This has been implemented in AudienceView 6.8.0.
The existing Flash Map and related .ASP pages have been replaced/updated with an SVG version of the pick-a-seat functionality.		 AVD-651
MAINT-322
Improve the Best Available (seatSelect.asp) page and incorporate an alternative Best Available (seatSelect.asp) page. This has been implemented in AudienceView 6.8.0.
  • Improvements to Best Available: The following improvements have been made to the Best Available page:
    • The ticket price displays next to the price type.
    • If the customer changes the price zone the ticket price is updated. If the price zone and the price type are not available then a message displays next to the price type indicating that it is unavailable.
    • The 'Best Available' radio button has been moved outside of the Seat Price Zone section to make it clearer that the price zone/price has yet to be determined, and a label displays indicating that the pricing cannot be confirmed.
    • The 'Promotion' field now appears to the top of the page.
    • The 'Continue' button is larger and fits the width of the column.
  • Alternative Online Best Available: By selecting the Enable Alternative Online Best Available 'Option' from the Venue Configuration application Performance|Basic page, an alternative Best Available (seatSelect.asp) page will be enabled for the performance. The alternative page consists of the following enhanced features:
    • Customers select the price, then the section and then the price type.
    • The Price Zone section only allows customers to select the available price zones, sold out price zones will be greyed-out.
    • The Section section displays the largest number of contiguous seats.
    • The price types displayed in the Seat Quantity section are dependent on the selected price zone. Unavailable price types will not be displayed.
    • Price zones that are sold out are disabled and labelled as such.
    • The 'Quantity' dropdown will only allow customers to select the maximum number of contiguous seats within the section.
 AVD-651
MAINT-345
ASA Compliancy - display the ticket price and the per ticket charges. This has been implemented in AudienceView 6.8.0.
By enabling the Include Ticket Charges in Ticket Prices 'Option' for the applicable role(s), you can display the ticket charges along with the ticket price in AudienceView Online, AVTiki and the Kiosk.
For more information, refer to Displaying Ticket Charges with Ticket Prices, Displaying Ticket Charges with Ticket Prices in AVTiki and Displaying Ticket Charges with Ticket Prices in the Kiosk.		 AVD-651
MAINT-349
User Friendly Limit Validation This has been implemented in AudienceView 6.8.0.
The limit validation process has been improved so that the dropdown lists are limited and the validation happens earlier in the process. For more information, refer to User-Friendly Limit Validation.		 AVD-721
Upgrade Fusion Charts used with AudienceView charting This has been implemented in AudienceView 6.8.0.
Fusion Charts (used with AudienceView charting) has bee upgraded to version the 3.3.1 Service Release.		 AVD-2256
Performance Availability This has been implemented in AudienceView 6.8.0.
The performance availability is now automatically displayed when a customer searches for a performance.
The duration in which inactive performances information remains in the cache is set to seven days, by default.
To alter the duration, refer to Configuring the Performance Availability Cache Timeout.
As a result of this work, you can no longer manually cache performance information. The 'Cache Selected' button has been removed from the Venue Configuration application Performances|Search page.		 AVT-6638
AVT-6659
My Account Recommendations This has been implemented in AudienceView 6.8.0.
Recommendations can now be displayed in the My Account pages.
For more information, refer to Configuring Recommendations.		 AVT-6417
AVT-6501
AVT-6502
Separation of AudienceView Online SSL This has been implemented in AudienceView 6.8.0.
You can separate encrypted/secure pages and entry points to pages (e.g. via the navigation bar or through the purchse flow) from non-encrypted/secure pages (i.e. https versus http) so that you can integrate third-party advertisements within your AudienceView Online sites
For more information, refer to Enabling Encrypted or Secure Pages.		 AVT-7672
CORE-68
Bypass the loginDelivery.asp page when items in the shopping cart do not require a delivery method (i.e. gifts). This has been implemented in AudienceView 6.8.0.
When items in the shopping cart do not require a delivery method, the loginDelivery.asp page is bypassed.		 CORE-63
CORE-64
Improve the usability of the SVG pick-a-seat map. This has been implemented in AudienceView 6.8.0.
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.8.0.
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

Mobile Enhancements

Feature Description ID
Remove the AudienceView Mobile application and make AudienceView Online mobile responsive. This has been implemented in AudienceView 6.8.0.
AudienceView Mobile as a separately configurable entity has been removed. Instead, when customers access AudienceView Online via a mobile device, the pages will adapt to their screen sizes allowing them to easily complete transactions in the same matter they would from a desktop/laptop computer. The responsive design uses Bootstrap 3.11. For more information, refer to http://getbootstrap.com/.		 AVD-563
AVD-3277

Business Intelligence and Reports Enhancements

Feature Description ID
Venue Proof report improvements This has been implemented in AudienceView 6.8.0.
The Venue Proof report has been updated to allow you to filter the report based on seat rows.
For more information, refer to Venue Proof Report.		 AVD-51
Holds per Performance report This has been implemented in AudienceView 6.8.0.
The new Holds per Performance report outputs the number of holds by type, the number of holds sold and the number of holds available for a specific performance.
For more information, refer to Holds for Performance Report.		 AVD-397
Improve the downloadReport.asp to support Business Intelligence queries. This has been implemented in AudienceView 6.8.0.
The downloadReport.asp now supported Business Intelligence queries, allowing you to run queries without logging into AudienceView.
For more information, refer to Download Report Portal.		 AVD-523
Add a Email Marketing Report This has been implemented in AudienceView 6.8.0.
A new Email Marketing Report has been added to the Business Intelligence and Reports application Generated Reports|Reports page under Marketing Reports. The Email Marketing report displays the metrics for an email marketing campaign either defined by appeal or message.
For more information, refer to Email Marketing Report.		 AVD-652
All BI queries to be run against the reports database (if one exists). This has been implemented in AudienceView 6.8.0.
The 'Default Reporting Database' field has been added to the Registry application System::Application node to allow BI queries to be run against the reports database.
The value entered in this field should match the 'Node Name' of the database configured in the Registry application System::Databases section.
When this value is set, all BI queries will be created with the configured value by default.
Hint
This field only defines the database for BI queries. If you want to run reports against the same database, you must define it in the Registry application Registry::Business Objects::TSreportBO::Reports::Database node's 'Default Value' field.
AVD-1556
Upgrade Fusion Charts used with AudienceView charting This has been implemented in AudienceView 6.8.0.
Fusion Charts (used with AudienceView charting) has bee upgraded to version the 3.3.1 Service Release.		 AVD-2256
Add Renewable Payment Method to the Customer object to Business Intelligence. This has been implemented in AudienceView 6.8.0.
The Renewable Payment Method criteria has been added to the Customer object in Business Intelligence as a result member and criteria.		 AVD-2561
Update the 'Include Non-producer Performances' criteria on the Performance Settlement, Ticket Sales by Performance, Ticket Sales and Wrap reports so that its purpose is clearer. This has been implemented in AudienceView 6.8.0.
The 'Include Non-producer Performances' dropdown name has been changed to 'Only Show Performances Without a Producer'. The available options have also been changed from Always and Never to Yes, making the criteria selection clearer.		 AVD-3534
Call Over Report Sorting The Section Row Seat option has been added to the 'Report Output By' dropdown of the Call Over report so that the report can be output by sections, rows and seats. AVT-6583
Cannot decrypt encrypted card numbers when extracting the information from a BI query. To decrypt encrypted card numbers via Business Intelligence, select the decrypt option from the Application Security application Group|Permissions page for applicable group's TSorderCO and TSorderPaymentCO properties. AVT-6819
Opportunities and Goals report This has been implemented in AudienceView 6.8.0.
The new Opportunities and Goals report displays pledge amounts and counts; goal amounts, counts, and expenses; and opportunity amounts and counts, for a specified date range for the selected funds, and appeals. Results are grouped by month and can be output in a cumulative (running total) or non-cumulative format. The report is “Association aware” and will filter fund, appeal and pledge results by the association on the user.
For more information, refer to Opportunities and Goals Report.		 AVT-9608
Direct Debit related 'Customer Payment' fields need to be added to the Customers BI. This has been implemented in AudienceView 6.8.0.
Several Direct Debit related 'Customer Payment' fields have been added to the Customers BI.		 CORE-70
Exclude hold types from reports This has been implemented in AudienceView 6.8.0.
The following reports can be configured to specify whether they should include only Open Seats, Seats on Hold, or both. The specified holds that are selected can also be specified to either be included in the results or excluded. 		CORE-93
Improvements to the AV Transaction report The following improvements have been made to the AV Transaction report:
  1. The detailed break-out of the output tables for admissions have been removed in favour of summary information.
  2. A gross sales column has been added when there is a count for both the 'Transaction Date Range' and the 'Year-to-Date Range'.
  3. Miscellaneous items have been added to the report's output, including both miscellaneous items sale counts and gross sales for the 'Transaction Date Range' and the 'Year-to-Date Range'.
  4. All of the fields except the 'Transaction Date Format', 'Transaction From', 'Transaction To', 'Contract Start Date' and the 'Display Values' criteria have been moved to the advanced section.
  5. The 'Transaction Date Range' column heading has been replaced with the applicable date range criteria.
  6. The 'Series', 'Price Types', 'User Roles' and 'User Role Groups' criteria have been altered so that they are exclusive instead of inclusive.
  7. The output identifies which criteria have been excluded from the report.
  8. An AVTiki Admissions row representing purchases from referrals from the AVTiki application has been added to the output.
  9. A 'Correspondence' section has been added to the output, displaying the total number of correspondences, the number of successful deliveries and the number of delivery failures.

    For more information, refer to AV Transaction Report.
 CORE-226
Add 'Customer State' filtering to the Donor Biography report. This has been implemented in AudienceView 6.8.0.
The 'Customer State' field has been added to the criteria of the Donor Biography report, enabling you to filter the report based on the state of the customer account (i.e. Active, Suspended, Closed).		 MAINT-150
Make Audit Batch Name available through Business Intelligence. This has been implemented in AudienceView 6.8.0.
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

Payment Enhancements

Feature Description ID
PayPal Express Checkout, PayPal Bill Me Later and Payment Method Logos This has been implemented in AudienceView 6.8.0.
PayPal Express Checkout and PayPal Bill Me Later can be configured as payment methods in the General Configuration application.
For more information, refer to Creating a PayPal Payment Method.
A 'Logo' field has also been added to the General Configuration application Payment Method|Basic page, allowing you to display the logos for the applicable payment methods. The images are located in the Online/Images folder. To display the Visa logo online, for example, enter images/payment_method_visa.png in the 'Logo' field.		 AVD-101
AVD-608
AVD-918
AVD-925
AVD-1519
AVD-1523
RedCard Prompted Signature This has been implemented in AudienceView 6.8.0.
RedCard's Prompted Signature feature for card-present payments has been introduced. An on-screen message prompts sales staff to have customers sign for the purchase.		 AVD-547
Add TouchNet as a core payment gateway. This has been implemented in AudienceView 6.8.0.
TouchNet has been added as a core payment gateway.
For more information refer to TouchNet.		 AVD-643
Enterprise clients need a way to manually purge cardholder data according to their organizations' retention period. This has been implemented in AudienceView 6.8.0.
The Encryption page has been added to the Registry application, allowing clients to define retention periods for encrypted cardholder data in the database.
For more information, refer to Using the Encryption Page to Purge Cardholder Data.		 AVD-644
Payment gateway configuration improvements The following changes to the payment gateway configuration have been implemented in AudienceView 6.8.0:
  1. A Payment Gateway user list has been created in the General Configuration application.
  2. Each entry in the list contains a readable name for the gateway followed by the optional gateway configuration (i.e PaymentGateway::PaymentType). For example, the 'Key' for a ProtoBase credit card gateway is ProtoBase::Credit.
  3. Payment gateway keys that were used for multiple configurations before (e.g. ProtoBase - Credit and ProtoBase - Gift Card) have been collapsed into a single entry (e.g. ProtoBase) in the Registry.
 AVT-9199

Printing Enhancements

Feature Description ID
Local Printer Support This has been implemented in AudienceView 6.8.0.
AudienceView offers local printer support, allowing locally connected or networked printers to be used without requiring WAN network considerations. Supported printer protocols include BOCA (FGL2, FGL4) and PDF. Works on all modern browsers by way of a small Java Applet that automatically installs the first time it is used. This funtionality replaces the Auto-Print funtionality.		 AVD-1990

Access Control Enhancements

Feature Solution ID
Introduce Mobile Device based scanning. This has been implemented in AudienceView 6.8.0.
The AudienceView Scan app is now available in the Google Play Store (Android) and the Apple Store (iOS). This app allows you to scan tickets using a mobile device. The interface operates in the same manner that the current access control works. The URL used for the app will be https://www.your_base_URL/mobilescan.		 AVD-1893

Performance Enhancements

Feature Description ID
Coordinated Universal Time from Database (UTC) This has been implemented in AudienceView 6.8.0.
Dates and times are now stored in UTC format. This allows database instances from different time-zones to run off of the same database server cluster.		 AVD-1991

Database Enhancements

Feature Description ID
Change default logging level in global.asa to 4 from 3. This has been implemented in AudienceView 6.8.0.
The default logging level in global.asa has been changed from to 4 from 3.		 AVD- 2

WebAPI Enhancements

Feature Description ID
Eliminate calls to Refresh. This has been implemented in AudienceView 6.8.0.
  1. All calls to Refresh have been removed.
  2. fixIt is now called instead of Refresh.
  3. fixIt is private to the order (with the exception of renewals, fixIt is a friend)
 AVD-1448
The ability to add customer account balances using the TScustomerBO has been added. This has been implemented in AudienceView 6.8.0.
The ability to add customer account balances using the TScustomerBO has been added.		 CORE-2
CORE-43
The WebAPI needs a doWork method to release orders. This has been implemented in AudienceView 6.8.0.
The cancelOrderItem action has been added to the TSorderBO doWork method.		 MAINT-58
MAINT-423

Installation Enhancements

Feature Description ID
The installer should not be required to be installed on the database server. This has been implemented in AudienceView 6.8.0.
The installer no longer creates any temporary files when loading the initial Registry configuration. There is no restrictions to install AudienceView by specifying a remote database in the 'Host' value in the configuration file (i.e. Installer.xml).
The referred database user must have enough privileges to create a database, and the bcpdir directive if such a file has been deprecated.		 AVD-1493
Create a commandline to initialize the AVScheduler. This has been implemented in AudienceView 6.8.0.
The AVScheduler can be initialized with the required encryption keys, without requiring to provide them through the AVScheduler Tray. This can only occur when starting the service via the SC windows command in the following way:
sc start <service name> -k1 "key1" -k2 "key2"
If the keys are empty, an empty string "" must be referenced. If the keys provided do not match the keys required to decrypt the connection string, the service will stop running eventually.		 AVD-1494
Create a command line to create an encrypted connect string with and without keys. This has been implemented in AudienceView 6.8.0.
The following command line can be used to mimic the features of the Master Keys tab of the AudienceView EncryptGui tool to create an encrypted database connect string:
Libs\Encrypt.exe /DC "<Database Connection String>" /DK1 "<Encryption Key 1>" /DK2 "<Encryption Key 2>" /E or /D
The DC, DK1 and DK2 parameters are required, and either /E (encrypted) or /D (decrypted) must also be provided.
Exit codes:
  • 0: with encryption/dencryption
  • 1: otherwise
 AVD-1495