Feature |
Description |
ID |
The navigation arrows on the Customer Services application Seats|Calendar page do not appear. |
This has been corrected in AudienceView 7.0.0 LA. The navigation arrow now appear on either side of the month/year in the calendar's header, allowing you to cycle through months. |
AVD-5023 |
The price type symbol for promotional seats are being displayed as Xs on the Customer Services application Seats|Map page. |
This has been corrected in AudienceView 7.0.0 LA. When a promotional seat is selected the Customer Services application Seats|Map page, the price type symbol the same as it would be without the promotional code activated. |
AVD-8699 |
The General Admission option should be removed from the seat 'Sys Type' field on the Event Configuration application Venue|Seats page when selecting a single seat (it has been removed from the other seat select options). |
This has been corrected in AudienceView 7.0.0 LA. General Admission has been removed as an option from the seat 'Sys Type' field on the Event Configuration application Venue|Seats page. |
AVD-9062 |
The 'Miscellaneous Item' and 'Name' columns in the search results section of the Customer Services application Miscellaneous Items|Search page contain the same information. |
This has been corrected in AudienceView 7.0.0 LA. The 'Miscellaneous Item' column has been removed from the Customer Services application Miscellaneous Items|Search page's search results section. |
AVD-9110 |
The broswer title for the Event Configuration application (formerly Venue Configuration) appears as Venue::label. |
This has been corrected in AudienceView 7.0.0 LA. The browser title fo the Event Configuration application now appears as Venue. |
AVD-9119 |
The button is not displayed next to the 'Image' field on the Event Configuration application Venue|Seats page when a group of seats has been selected. |
This has been corrected in AudienceView 7.0.0 LA. The button is now displayed. |
AVD-9506 |
The performance record includes a settlement amount which is the sum of all the settlements associated to the event. When 'Save Copy' is used to make a copy of an existing event, the settlement amount is also being copied, even though there were no settlements associated to the new event. |
This has been corrected in AudienceView 7.0.0 LA. The settlement amount is no longer copied when using 'Save Copy' to create a copy of an event. |
AVD-9586 |
Change label/field name of the 'URL' field that appears on the Event Configuration application Venue|Seats page. |
This has been corrected in AudienceView 7.0.0 LA. The 'URL' field that appears on the Event Configuration application Venue|Seats page has been renamed 'Image' to better reflect the field's purpose: storing an image or a URL to an image and not just any URL. The following changes were also made: 1.The 'section_url' database column has also been changed to 'section_image' 2.The Registry::EN::TSvenueBO::Sections::URL node has been changed to Registry::EN::TSvenueBO::Sections::Image. 3.The pop-up label (that appears when the section or seat image is displayed) has been changed from Section URL to Section/Seat Image. |
AVD-9693 |
When a merchant description on a performance or payment method exceeds 128 characters, causes the buffer to overflow and the user to be kicked out of the order. |
This has been corrected in AudienceView 7.0.0 LA.
The value of the merchant description field should not exceed 25 characters. |
AVD-10191 |
Issue |
Solution |
ID |
Event, Section and Seat messages are being displayed on the shoppingCart_admissions.inc.asp page despite being surpressed for the Internet role. |
This has been corrected in AudienceView 7.0.0 LA. The pop-up no longer appears when it is suppressed for the role. |
AVD-9609 |
Unicode characters in the event description (copied and pasted in from another text source) cause search results to fail. |
This has been corrected in AudienceView 7.0.0 LA. Fixed issue where unprintable characters in Event description could break search result listings Online. |
AVD-9863 |
Feature |
Description |
ID |
If users logged into the Event Owner Portal and attempt to access a page that they do not have content permission for, they get stuck in a redirect loop. |
This has been corrected in AudienceView 7.0.0 LA. If users are logged into the Event Owner Portal and do not have content permissions for the page that they are trying to access, they are redirected to a new "Unauthorized" page. If the user is not logged in and does not have content enabled for the page they are trying to access, they are redirected to the login page.
To expedite this release, the message and button labels are hardcoded. These will be added to the Registry in a future release. |
AVD-7713 |
An issue was found in environments where: 1.The Shibboleth integration is in use; 2.A Shibboleth attribute is used to set a group for new users; and, 3.There are multiple default groups configured for the user
When the Shibboleth-driven group is added, it replaces one of the default groups instead of adding to the set. |
This has been corrected in AudienceView 7.0.0 LA. The Shibboleth-driven group is now added to the default set of groups, even when there are multiple default groups. |
AVD-9432 |
All of the profiles created by the same customer share the same settlement payment method. |
This has been corrected in AudienceView 7.0.0 LA. Each profile creted by a single user/customer account can now have an independent settlement payment method. |
AVD-9805 |
Using the temporary password generated by the Forgot Password functionality causes an error |
This has been corrected in AudienceView 7.0.0 LA. Users can sign in using the temporary password. |
AVD-9699 |
The Forgot Password functionality is not sending the temporary password emails. |
This has been corrected in AudienceView 7.0.0 LA. The emails are now being sent as expected. |
AVD-9727 |
Events and profiles are intermittenly being assigned the wrong GUID in the 'URL for Published Event / Profile' field. |
This has been corrected in AudienceView 7.0.0 LA. The way that GUIDs are set has been modified to prevent this issue from reoccuring. |
AVD-10075 |
Changing the label on the 'Save as Published' button (Registry application Registry::EN::Application::Online::MarketView::Create Event node's 'Save as Published' field) prevents users from eventually publishing an event. |
This has been corrected in AudienceView 7.0.0 LA. Changing the label no longer effects event creation. |
AVD-10173 |
Issue |
Solution |
ID |
PayPal's soft descriptor is not available on credit card bank statements. |
This has been corrected in AudienceView 7.0.0 LA. The merchant descriptor field on the event or on the payment method can be used to dynamically create a descriptor that displays on the card holder's credit card statement.
The formula for both PayPal gateways is as follows:
SOFTDESCRIPTOR (Optional) Per transaction description of the payment that is passed to the buyer's credit card statement. If you provide a value in this field, the full descriptor displayed on the buyer's statement has the following format:
<PP * | PAYPAL *><Merchant descriptor as set in the Payment Receiving Preferences><1 space><soft descriptor>
Character length and limitations: The soft descriptor can contain only the following characters: •Alphanumeric characters •- (dash) •* (asterisk) •. (period) •(spaces) If you pass any other characters, PayPal will return an error code.
The soft descriptor does not include the phone number, which can be toggled between your customer service number and PayPal's Customer Service number. The maximum length of the soft descriptor is 22 characters. Of this, the PayPal prefix uses either four or eight characters of the data format. Thus, the maximum length of the soft descriptor information that you can pass in this field is:
22 - len(<PP * | PAYPAL *>) - len(<Descriptor set in Payment Receiving Preferences> + 1) For example, assume the following conditions: •The PayPal prefix toggle is set to PAYPAL * in PayPal's administration tools. •The merchant descriptor set in the 'Payment Receiving Preferences' is set to EBAY. •The soft descriptor is passed in as JanesFlowerGifts LLC. The resulting descriptor string on the credit card is:
PAYPAL *EBAY JanesFlow |
AVD-9023 |
Issue |
Solution |
ID |
Rollback the changes made to the primitive serialization introduced in AVD-9031. |
This has been corrected in AudienceView 7.0.0 LA. The JSON output now consists of object with "standard", "input" and "display" values for all primitives as it was before the change in AVD-9031. |
AVD-9726 |