Issue |
Solution |
ID |
|
Add Canonical Link URL and Redirect (301) URL attributes to Content Management |
This has been implemented in AudienceView 7.7.0. Two new attributes have been added to the Content Management application Articles|Application page are to help manage visitors from Google and other search engines:
•Canonical Link URL: Used to set another page on the same domain that will be considered by search engines to be the authoritative go-to page for searches that also match the subject of the article. •Redirect (301) URL: Used to create a redirection for any request for the article to a different URL. This type of redirect (301 response) also provides search-engine crawlers with a hint that the new URL should be considered the new location for the articles content. Articles must be active for the redirection to happen -- an IIS webserver rule would be necessary for redirections from URLs that no longer have an active Article. |
AVD-8453 |
|
Improve the speed of saving copies of events. |
This has been implemented in AudienceView 7.7.0. The speed of the 'Save Copy' function on events was improved. The time it takes to complete save copies of events was reduced from 7-8 seconds to 1 second. |
AVD-12198 |
|
Move the fiscal year node. |
This has been implemented in AudienceView 7.7.0. The fiscal year node has been moved from the Registry application Registry::System::Configuration::Fiscal Year to Registry::System::Application::Fiscal Year to improve accessibility for reports and business intelligence. Reports and BI could no longer access the previous location, rendering the fiscal year inoperable in donation reports. |
AVD-12528 |
|
Improve the layout of the Event Configuration application Event|Pricing page, consolidating it with the Event|GA Seats page. |
This has been implemented in AudienceView 7.7.0. The layout of the Event Configuration application Event|Pricing page has been improved. The information previously configured on the Event Configuration application Event|GA Seats page has been added to the Event|Pricing page, and it has been removed. |
AVD-12636 |
|
Update the Customer Services search result styles. |
This has been implemented in AudienceView 7.7.0. An improvement has been implemented to greatly enhance the look and feel of search results within Customer Services. Functions such as 'Add To Order' now appear in the action menu displayed directly in the search result row to eliminate the need for page scrolling. |
AVD-12871 |
|
Remove warning Message 4243: This Event is about to be put off-sale before it happens. Continue? |
This has been implemented in AudienceView 7.7.0. It is a common business practice to have an event go off-sale prior to the event start date, so the message was redundant and has been removed. |
AVD-12876 |
|
Add 'Create Date/Time' criteria to the preloaded search on the Utilities application Data Management|Search page. |
This has been implemented in AudienceView 7.7.0. The 'Create Date/Time' criteria was added to the preloaded search on the Utilities application Data Management|Search page to help distinguish between jobs with similar names. Jobs are now sorted by create date/time in descending order (most recent jobs are displayed at the top). |
AVD-13035 |
|
Add a grouping section to the General Configruation application Script Definitions|Edit page. |
This has been implemented in AudienceView 7.7.0. The fields grouping section to the General Configruation application Script Definitions|Edit page, allowing users to add groups separately from the field configuration. Execution fields will be separated on the Utilities application Data Management|Schedule page appropriately. |
|
|
Improve the messages that are displayed during the creation of multiple events. |
This has been implemented in AudienceView 7.7.0. When a user clicks 'Create Events', a warning message is now displayed, showing the number of events which will be created based on the values set by the user. |
AVD-13182 |
Issue |
Solution |
ID |
Improve the preloaded Refund Protection article. |
This has been implemented in AudienceView 7.7.0. The text of the preloaded Refund Protection article (used with Booking Protect) has been updated to improve offer conversion. |
AVD-12597 |
Issue |
Solution |
ID |
Expose the event's 'Category' field. |
This has been implemented in AudienceView 7.7.0. When the event 'Category' field is readable, it is also displayed on the Create Event and Edit Event pages. |
AVD-11055 |
Issue |
Solution |
ID |
Convert the Call Over report from XSL to JavaScript. |
This has been implemented in AudienceView 7.7.0. The Call Over report has been converted to JavaScript. The labels can be configured in the Registry application Registry::EN::Application::Business Intelligence and Reports::Report Labels::Call Over node. The report does not display customer/order data filters as criteria at the top of the HTML and AVDOC output when selected. Face Value will exclude any charges not selected for output. |
AVD-11810 |
Remove the Security by User report (and update the Security by Group report) and the Order Marketing Data report. |
This has been implemented in AudienceView 7.7.0. The Security by User report has been removed. User criteria has been added option to the Security by Group report. This was done to simplify the code and improve the quality of the report.
The Order Marketing Dta report has also been removed. This was done because it can be replicated more easily in BI and with greater flexibility. |
AVD-11835 |
Issue |
Solution |
ID |
Support swiped cards in scheduled payments |
This has been implemented in AudienceView 7.7.0. To further support the encrypted ID Tech devices, the ability to swipe a card number through a simple card swipe, or use the ID Tech encrypted device whether keyed or swiped has been added. EMV is not supported in scheduled payments because the card number is not passed to the application, and scheduled payments require the presence of a persisted card number. |
AVD-13044 |
Feature |
Description |
ID |
Provide the ability to load customer data from external .CSV source files |
This has been implemented in AudienceView 7.7.0. •One preloaded script called Customer Load and an accompanying include script called Customer Load Include have been added to the General Configuration application Scripts section. •Six preloaded script definitions, each of which uses the same Customer Load script but handle a different combination of source files, have been added to the General Configuration application Script Definitions section: 1.Customer Load: Using customer, contact and address files 2.Customer Load: Using customer, contact, address and customer marketing files 3.Customer Load: Using customer, contact, address and membership files 4.Customer Load: Using customer, contact, address and user files 5.Customer Load: Using customer, contact, address, customer marketing, user and membership files 6.Customer Load: Using single source file •Sample source files can be found in the \Setup\Examples\DataMonkey\Sample Source Files folder.
Users can create source files based on the samples provided. Users can then create a Data Management job using whichever script definition fits the available source files. If no appropriate script definition exists, users may create their own, following the same conventions as the existing script definition.
It is strongly recommended you test any customer load in a staging environment before executing it in a production environment. |
AVD-6342 |
Implement payment processor script as a Data Monkey script |
This has been implemented in AudienceView 7.7.0. The pre-existing payment processor script has been converted for use with the Data Monkey. The Scheduled Payments to Process Business Intelligence query (which generates a list of scheduled credit card payments that have not been processed) and the Process Scheduled Payments script and script definition allow scheduled payments to be processed via Data Monkey. |
AVD-13079 |