The following table outlines the changes made in AudienceView 7.12.0:
NEW FEATURE |
Provide the ability to load notes from external .CSV source files One preloaded script called Note Load has been added to the General Configuration application Scripts section. One preloaded script definition called Note Load has been added to the General Configuration application Script Definitions section: Users can then create a Data Management job using the Note Load script definition.
The script creates notes based on a .CSV source file, with support for customer, order, performance, fund and user notes. All values on the notes can be set using the script.
The 'parent_type', 'parent_name' and 'parent_value' columns in the source file are used together to assign a parent item to the note. For example you can set a parent customer using a customer number, customer ID or customer legacy number; a parent order using an order number or order ID; a parent event using a performance code or performance ID; or a parent fund using a fund name or fund ID.
One limitation for this first iteration of the script: A key (rather than a label) is required for the parent type and context type, so for reference: •Customer: 12 •Order: 25 •Performance: 13 •Fund: 100 •User: 14 |
AVD-5700 |
|
NEW FEATURE |
Desktop - Batch Event Update Limits The Event Configuration application Events|Batch Update|Calendar page (introduced in AudienceView 7.10.0 under AVD-12831) has been extended to include limits The Event Configuration application Events|Batch Update|Limits page allows you to add, remove and update limits for any set of events, including events from multiple series and multiple venues. To access the tool, Events Batch Update Limits must be enabled for the Application Security application Group|Content page's Event Configuration property. |
AVD-13987 AVD-13988 |
|
NEW FEATURE |
Event Configuration Application Events|Sales Status Page The Event Configuration application Events|Sales Status page has been added. It provides a quick view of the sales counts for the currently loaded event. Unlike the core reports, the page also includes in-progress sales, making it useful for reporting on large on-sales.
The page works best if it is accessed using a role that has the ability to all of the event's holds. If there are admissions with a hold that the role cannot sell, they will be counted in the 'Sold' column. |
AVD-14783 |
|
NEW FEATURE |
Branding Invoices. Invoice brading can be configured in the Registry application and then applied to a particular role using the 'Brand' dropdown on the Application Security application Roles|Basic page. |
AVD-14947 AVD-14949 |
|
IMPROVEMENT |
Online - Pick-a-seat has been significantly improved for usability. •The pan and zoom controls that support pinch to zoom on mobile devices have been improved. Pan and zoom are now available on the overview map. We expect this feature to be more applicable to larger venues with multiple screens; therefore, it is possible to configure on the venue whether pan and zoom is enabled or disabled. By default the option is disabled. •The overview map no longer forces the user to hover over screens to find available screens. Only available screens are now shown and these are displayed without the user needing to hover over them. •The event information is now displayed within a cleaner event information block. This layout has been copied to best available, too. If the event description is long only the first few lines will display and the user will be able to expand the content with the “show more” link. •Because users cannot make selections on the overview page the Your Selections section has been removed from the overview page. •The pricing legend on the overview page is now brought into view via a button. The pricing legend now sits on top of the map, and because price zone colours are not shown on the overview page, the price zone colours no longer appear in the pricing legend. •The pricing legend on the detailed view has been redesigned to show price zones horizontally. The fees message link is no longer displayed underneath each price, instead it is displayed once within the container. The price zone colour is used for the amount display, too. If you do not want to use the same colour for the amount display, use the following:
•Pick-a-seat is now fully responsive and supports desktop computer, tablet and mobile widths. As the width of the view decreases elements on the page will collapse and can be expanded. The map now exists within its own container on the page, panning and zooming on a mobile device within the map only pans and zooms the map and not the entire page. •It is now much clearer when a seat has been selected in the detailed view. The legend that describes the available, selected and unavailable states has been removed. Available seats are filled using the price zone colour, and unavailable seats are now much smaller. If users select a seat, the seat will be highlighted with a white halo. When users select the price type for that seat, the seat fill will flip to white and the halo will be the colour of the price zone. It is now possible to deselect a seat by clicking on a selected seat. The available/unavailable status no longer appears when users hover over a seat to reduce unnecessary information on the page. •The price type selection pop-up position has been improved so that it always appears above the map (users do not have to scroll to find it). The pop-up will appear above, below, to the left or to the right depending on the position of the selected seat. •The dropdown for selecting a different screen on the detailed view has been renamed to 'Jump To…' and this list of screens now only shows the screens that have available seats. In addition The top, bottom, left and right screens are configured on the venue in the detailed view as arrows to allow the user to quickly navigate to nearby screens. When users hover over (not supported on mobile devices) the system indicate how many seats are available in that screen. INearby screens will not display an arrow if the screen is sold out. •Your selections in the detailed view has been moved to the right-hand side of the page. The 'Add to Order' button is positioned at the top of this container, making it much less likely that the button will be pushed off screen. We now maintain a count of selected seats for users. The display of selected seats has been redesigned. To draw the users' eyes to the selected seats on the map, the same selected seat design is used (a circle, filled with white and the price zone colour halo) and the section/row/seat information has been redesigned. The trash can icon used to remove a seat has been replaced with a more obvious cancel button. •General improvements have been made to the layout of the overview and detailed page to make the workflow and page hierarchy clearer to the user. The following is the updated CSS for online pick-a-seat: /* Top Level Container */ |
AVD-14793 |
|
IMPROVEMENT |
Customer - Allow users to set the customer 'Active Date' on the Customer Services application Customer|Basic page. The 'Active Date' field no longer defaults to the current date/time if a specific date/time is entered in the field. If not date/time is provided or if the field is not readable, then the current date/time will be used. |
AVD-13094 |
|
IMPROVEMENT |
Skip Cancelling Tickets When Changing Printed Order Item Customers A new 'Option' Skip Cancelling Tickets When Changing Printed Order Item Customers has been added to the Application Security application Roles|Basic page that allows the role tol not cancel a printed ticket if the only change to the order is the customer assignment. |
AVD-13525 |
|
IMPROVEMENT |
Seat History - Add 'View History' button on the Seat Details pop-up for each event. When multiple events have been "pancaked" on a seat map (events or bundles), the Seat History pop-up now displays a 'Vew History' button for each of the loaded events. |
AVD-14205 |
|
IMPROVEMENT |
Payments - Tokenized refunds and voids through Tender Retail. Refunds and voids are now supported through Tender Retail by using token IDs. This allows you to refund or void card present transactions that were created with a token. Chip and Pin transactions (created with a token) can be refunded or voided without requiring cardholders to insert their cards into the terminals.
This requires a change to the Tender Retail Merchant Connect Multi software so that the 'Card Information Response Format' is set to Token.
For card present transactions: •Payments, refunds and voids all behave as expected with tokenized payments. •Refunds to payments without tokens require the user to have the card present and will prompt the user as such. There is no user impact for card not present (moto or internet) payments. As part of this work, an extra layer in the gateway dll that required the fields to be populated has been removed.
Validation is now done as follows: •Payment Method: The pattern and mod10 can validate that a card number meets rules (no change) •Field Validation: If a field is required in the Registry or Application Security group it will be validated (no change) •Processing Validation: Payment processing validation Is done by the thrid-party payment processor - payments are approved or declined. Since the processor cannot process a payment without card number or expiration date, we are leaving the validation up to them. |
AVD-14267 |
|
IMPROVEMENT |
Payments - Allow Electronic Check payment methods to be saved against a customer account. |
AVD-14384 |
|
IMPROVEMENT |
Bluefin - Populate custom_id field with order number. When processing an order through the Bluefin gateway, the AudienceView order number is now passed to the custom_id field. This field is available on transactions and in reports through the PayConex management portal. |
AVD-14506 |
|
IMPROVEMENT |
Refactor TSorderBO::addSeats TSorderBO::addSeats has been refactored to meet the following objectives: •Support by performanceName and performance_id. •Remove support for bundles and best available options, in favour of new dedicated doWork methods. |
AVD-14587 |
|
IMPROVEMENT |
Bluefin - Support tokenized non-referenced refunds. You can now add a new 'Payment Transaction Type' of Refund (a refund that does not reference the original payment transaction or reference ID) when using the Bluefin payment gateway. Using the 'Refund' and 'Partial Refund' buttons (referenced refunds) are not affected by this change, and work as expected. |
AVD-14637 |
|
IMPROVEMENT |
Order Load Script Updates •The 'Customer Identifier' field has been added to all nine of the script definitions available for the Order Load script. The 'Customer Identifier' field allows the following four options: ocustomer_number ocustomer_reference_code ocustomer_reference_code2 ocustomer_reference_code3
The customer will be added in the order based on what is entered in 'Customer Identifier' field. The .CSV file now accepts the replacement of customer with customer_number. •Support for optional row_end and seat_end CSV columns which, in conjunction with the existing row and seat columns, defines a seat block. The addSeats doWork will default the rowEnd and seatEnd parameters to rowStart and seatStart, respectively, to define a single seat request. •create_date is now supported by the order_source_file, and can add the date that the order was created. •Refunds are now supported. The transaction_amount (.CSV column name in payment_source_file or order_with_payments_source_file) can be set to -ve value, which will add the payment as a refund. •The 'Memo' field was added to the payment_source_file or order_with_payments_source_file .CSV files, which will set 'Memo' field for the payment record. |
AVD-14729 AVD-14802 AVD-14880 AVD-14892 |
|
IMPROVEMENT |
Add doWork parameters (passed by name) to the TSorderBO's getBestAvailable and getBundleBestAvailable doWork methods. The following parameters have been added to the TSorderBO: getBestAvailable •performanceName (array of names) •priceTypeName (single name) •priceValueName (single name) getBundleBestAvailable •priceZoneNames (array of names) •performanceNames::* (array of names) •priceTypeName (single name) |
AVD-14762 |
|
IMPROVEMENT |
WebAPI - Add TSorderBO::addBundleSeats doWork A new doWork, addBundleSeats, has been added to TSorderBO to add seats to a bundle. addSeats no longer supports adding bundles. |
AVD-14791 |
|
IMPROVEMENT |
Payment Gateway - Allow users to add a new payment gateway node through the Registry.
Users can now add payment gateway nodes through the Registry, |
AVD-14844 AVD-14881 |
|
IMPROVEMENT |
Gifts - Customer, address or contact are no longer required on an orders that only contain gifts. |
AVD-14889 |
|
IMPROVEMENT |
Customer Load script updates. •'First Name', 'Last Name' , 'Zip', 'State', 'City' and 'Street' are no longer required fields. •create_date is now supported by the customers_source_file, and can add the date that the customer was created. •Any telephone number and postal/zip codes validations have been removed from the script, and the 'Default Format Country' execution field has been removed from script definition. •The is_default column has been added in the contacts_source_file and address_source_file .CSVs so that the default address (in case of multiple addresses) and the default contact (in case of multiple contacts) can be set. Y, y, YES, yes and Yes are all acceptable values. •Data fields for addresses and contacts are now supported. In a single-source file the name of these columns are prefixed by contact_ and address_, respectively (e.g. contact_data1 and address_data1). This is to prevent ambiguity between same column names but from different nodes. |
AVD-14981 AVD-14982 AVD-15031 AVD-15033 AVD-15035 |
|
IMPROVEMENT |
Limits/Messages - Eliminate Warning Message 6146: The limit's Start Date is before the performance's Start Date. Warning Message 6146 was previously displayed when a limit was added to an event where the limit's 'Start Date' was earlier than the event's 'Start Date'. Since this is almost certain to be true of all limits on events, the message was redundant. |
AVD-15024 |
|
FIXED |
Desktop - The Funds Management application Gifts|Calendar page is not validating unique calendar rows for the same role correctly. |
AVD-5876 |
|
FIXED |
Online - The giftCardListReloads.asp is missing an opening body tag, making it difficult to override element attributes. |
AVD-10895 |
|
FIXED |
Online - The mapSelect.asp page shows price type 'Name' and price zone 'Name' instead of the 'Label'. |
AVD-12643 |
|
FIXED |
Desktop - The 'Duplicate Customer State' field Is not populated when Warning Message 5374: The account being created already exists Is Supressed. |
AVD-13836 |
|
FIXED |
Online - Gift pop-up does not add the 'Gift Amount' to the shopping cart. |
AVD-14158 |
|
FIXED |
Promotion codes allowing customers to purchase tickets in advance are making all events with future on-sale dates available for sale regardless of the promotions assigned to them. |
AVD-14777 |
|
FIXED |
Bundle Admission Customer Displays as GUID |
AVD-14945 |
|
FIXED |
Tickets - Print-at-Home tickets are not being automatically sent |
AVD-14978 |
|
FIXED |
Application Security - Applying a role to a hold causes a database error. |
AVD-15004 |
|
FIXED |
Online/Limits - Online customers and being asked to login after selecting their seats even though the Manage Over Caps 'Option' is selected on the Roles|Basic page. |
AVD-15166 |
