Audience Development Software Release Notes (Version & 1.1.9)

Transcription

1 Audience Development Software Release Notes (Version & 1.1.9) Abacus e-media Chancery Exchange 10 Furnival Street London EC4A 1YH Tel: +44 (0) Abacus Software Ltd trading as Abacus e-media No Registered office 10 Furnival Street, London SW1Y 4PH

2 ADvance Version Configuration Version Environment Date Released / Planned Test 11 th December Live 22 th December Test 27 th December Live 3 rd January 2014 Document Control & Work Flow Date Author Version Change Reference 6 th January 2014 Jack Middleton V1.0 Initial version 9 th January 2014 Glenn Watts V3.0 Final version

3 Table of Contents 1. Summary of Changes Forms/Form Builder... 6 New features/improvements... 6 Abacus Product Development... 6 Fixes... 6 Abacus Product Development Product Offer/Orders... 7 New features/improvements... 7 Abacus Product Development... 7 Fixes... 7 Abacus Product Development General Backend... 7 New features/improvements... 7 Abacus Product Development... 7 Raised by Client General Frontend... 9 New features/improvements... 9 Abacus Product Development BI... 9 New features/improvements... 9 Abacus Product Development... 9 New features/improvements... 10

4 Raised by Client Appendix A AAD-4628 Improved the form builder usability and design Page 1 Form set-up page Page 2 Select question popup Page 3 Question Add/Edit page AAD-4154 Added configuration setting to control whether form questions are pre-populated CHTAD-70 Added the ability to cancel one subscription within an order Cancellation reason and Comment fields Cancel Options radio buttons Order details table - Cancelling Individual Entitlements Order details table - Cancelling Entire Orders Refunding Cancelled Entitlements AAD-4762 & AAD-4763 Added corporate offers to the front-end and back-end Creating a corporate offer Placing a corporate order Frontend Placing a corporate order Backend Renewing corporate orders Frontend Renewing corporate orders Backend AAD-4807 Added the ability to concatenate values output in BI Appendix B - Summary of changes for AAD Fully responsive UI to a max width of 1280px Improvements to validation Help text re-positioned... 26

5 Section heading enhancement Text size enlargement Question labels aligned right Two column layout enhanced Improve layout of password question Right column fixed width Masthead width change... 30

6 1. Summary of Changes These code drops occurred over the holiday period and contain a multitude of improvements to the design and functionality of the ADvance forms (both back end and front end changes), please see the Appendix 2 for more details. Other highlights include the ability to cancel & refund one subscription within an order, allow customers to place corporate orders via front end and continued improvements to both ETL and BI tools. 2. Forms/Form Builder New features/improvements Abacus Product Development Jira reference AAD-4509 (including AAD-4773 & AAD- 4774) Description Redesigned front-end forms to improve usability (See Appendix B) AAD-4628 Improved and redesigned the form builder flow (See Appendix A) AAD-4154 AAD-4377 Added option to configure whether questions are pre populated based on existing party demographics (See Appendix A) Added the ability to order countries that appear in the Address Component question This can only be done upon request to Abacus. There is currently no way to do this via the back end. This setting is set per capture form. So, if requested, it is possible to have different countries/ordering on different forms. It is only possible to order countries that appear on the Address component question type that can be added to capture forms. It is not possible to order the countries dropdown that appears within the checkout process (I.e. Billing address and Delivery address) It is also possible to specify which countries appear in the dropdown as well as the order in which they appear (I.e. Just EU countries with UK at the top) Fixes Abacus Product Development Jira reference AAD-4813 AAD-4724 Description Fixed issue preventing users from going back to the previous page using the browsers back button Fixed issue with date questions not allowing you to enter a date in a year beyond the current year

7 3. Product Offer/Orders New features/improvements Abacus Product Development Jira reference Description CHTAD-70 Added the ability to cancel one subscription within an order (See Appendix A) AAD-4762 Added corporate offers on the front-end (See Appendix A) AAD-4763 Added corporate offers on the back-end (See Appendix A) Fixes Abacus Product Development Jira reference AAD-4766 Description Fixed an issue where editing a variant removes the renewal default flag set on quick product offers 4. General Backend New features/improvements Abacus Product Development Jira reference AAD-4795 Description Changed the image text that appears on Configuration >> Brands >> [Brand] >> Branding (Figure 1)

8 Figure 1 AAD-4734 Improved the IFR Galley file to show correct addresses column shows the latest that is saved against a physical address on the party record Secondary column shows the latest that is not saved against a physical address If a party only has an address that is not saved against a physical address, this will only appear in the Secondary field and not field AAD-4757 AAD-4746 Allow records from different pages to be selected at the same time on DD Reconciliation page Added the status of a matched party on the matching screen

9 Raised by Client Jira reference AAD-4691 Description Fixed diary entry not being created when cancelling/registering newsletters 5. General Frontend New features/improvements Abacus Product Development Jira reference Description AAD-4796 Added support for logging in with Legacy ID (See Appendix A) 6. BI New features/improvements Abacus Product Development Jira reference AAD-4791 Description Various improvements and fixes to BI Fixed order status picking up wrong value (Used subscription rather than order) The field Order >> Order Details >> Channel has been added back in

10 Fix Today relative filters Added date format for date value options: YYY-MM-DD (NB: This is the only format that is current operational) AAD-4807 Various improvements and fixes to BI (Continued) Changed Order >> Subscriptions folder to contain fields from the main Subscriptions folder Added the ability to concatenate values output by BI (See Appendix A) New features/improvements Raised by Client Jira reference CTAD-520 Description Added newsletter fields to BI: Subscriptions >> Newsletter >> Newsletter Name Subscriptions >> Newsletter >> Newsletter Brand Subscriptions >> Newsletter >> Newsletter Code

11 7. Appendix A AAD-4628 Improved the form builder usability and design The workflow for adding/editing questions that appear on a form has been updated to improve the usability of the form builder. Page 1 Form set-up page There has been no visible change to the layout or design of this page The Add questions link in the left hand column now opens a new popup (Figure 7) o Adding a question automatically adds the question to the last section on the last page of the form The Add questions link at the end of each form section now links to the new popup as well The Edit links open the add/edit page (Figure 8) Page 2 Select question popup Figure 7 This pop-up displays the list of demographics split by demographic categories. Selecting the arrows opens all demographic questions within that demographic category o This list is the same list that appeared in the left hand column of the previous implementation All questions are selected by radio buttons which means only one can be selected at a time Once a question has been selected, the continue button becomes active and selecting continue will open the add/edit page (Figure 8) Selecting cancel closes the popup

12 Page 3 Question Add/Edit page Figure 8 This page is very similar to the previous form builder page o There is no longer a left hand column listing all demographics available This has been replaced with the form edit furniture o There is no longer a right hand column listing all demographics currently used on the form No functionality to the demographics themselves have been changes as part of this improvement o There are still two tabs on look-up questions; Question Settings and Manage Answers At the bottom of the page, the Done and Cancel buttons are available o Done saves the question and returns to the form set up page o Cancel removes any changes and returns to the form set up page AAD-4154 Added configuration setting to control whether form questions are pre-populated There is now an additional tick box that appears on the form builder labelled as Pre-populate with existing details (Figure 9). NB: Pre-population means pre-filling the field with information that we already hold about the user completing the form after they have been identified. This is different to pre-selecting default values for certain questions on a form (AAD from sprint v1.1.6).

13 Figure 9 Selecting this option will pre-populate questions that appear on the current form based on the following rules: Pre-populate will take the latest demographics for the user that is currently logged in o If there is no user logged in, the fields will remain blank E.g. Registration o If the logged in user has no demographics, the fields will remain blank The tick box will be disabled on Edit User Details forms as this functionality is already automatically in place for this form type The pre-populate tick box will be enabled on the registration forms, but this will not have an effect on the front-end display as there is no data to pre-populate the form with If the question has both pre-selected values and has the pre-populate option selected, the latter will take priority o E.g. Question 1 by default selects answers A, B and C. The current user has previously answer this question with just A. When opening a form with both settings enabled, the question will be prepopulated with A and not A, B and C. This occurs even if the user has never answered the demographic before. So, in the previous scenario, the question would be blank If a party has answered a look-up question with a value that is not set to display on the current form, the lookup question will remain blank. For address component questions, the Options section has now been added to cater for this new option (Figure 10).

14 Figure 10 CHTAD-70 Added the ability to cancel one subscription within an order Prior to sprint v1.1.8 it was only possible to cancel a whole order. This change introduces the functionality to cancel part of an order (i.e. 1 subscription from an order that includes 3 subscriptions). Both cancelling a subscription and cancelling and order are controlled by the Cancel order option in the actions dropdown that appears at the bottom of each order (as per previous behaviour). When this option is selected a new cancellation page (Figure 2) is opened instead of the popup that previously appeared. This new page also incorporates the refunding functionality that was previously accessed via a tick box in the popup.

15 Figure 2 Cancellation reason and Comment fields These fields have been carried over from the previous functionality. The functionality has not changed; both values will be used in the customer diary entry that is created when cancelling/refunding an order. Cancel Options radio buttons Cancel options specifies whether the cancellation is for individual entitlements or for the entire order. The selection here changes what is possible in the Order Details table that appears below this option. Order details table - Cancelling Individual Entitlements Checkbox o The checkbox is active when the entitlement is Active or Cancelled This is active when cancelled so it is possible to refund after cancelling an entitlement o The checkbox is inactive for Expired and Suspended entitlements The tick box is also inactive when the calculated value is 0 which prevents refunding more than the value of the order Title o The title shows the name of the entitlement o If the Quantity > 1 the number of entitlements will be added in brackets. E.g. Jack Magazine (2) Status o Total o The status displays the status for each entitlement in the order (Active, Expired, Cancelled and Suspended) This value shows the total value of the individual entitlement

16 o Hovering over this value shows a breakdown of the cost (Figure 3) Figure 3 Calculated o The value shown here is a system generated refund amount that is owed on the entitlement. E.g. If a 10 entitlement has been refunded 2 already, this value will be 8 Refund o o This is a text box where the value to be refunded is specified. The textbox is only active if the checkbox for the current entitlement has been selected. This value can either be blank (no refund) or a value that is less than the total value for that entitlement. NB: Refunding an order does not put money back into the customer s account. This marks the entitlement as cancelled and the actual refund process is handled by the accounts team. At the bottom of the page there are two buttons; Submit Cancellation and Cancel. Submit cancellation will submit both the cancellation and the refund (if one has been specified). Cancel will abort the process and not save any changes. When single entitlements have been cancelled the status of the whole order is not changed, only the status of that entitlement. A customer diary entry is also created highlighting what has been cancelled and whether a refund has been made. Order details table - Cancelling Entire Orders When cancelling an entire order, the display is mostly the same except that the checkboxes are all disabled and an additional Total row is added to the bottom of the table (Figure 4). Figure 4

17 The total row has 3 values Total This shows the sum of all entitlement totals o Hovering over this value shows a breakdown of the cost for the whole order Calculated This shows the sum of all the entitlement calculated values Refund this text box is used to specify the refund amount for the whole order. The value that is entered here must be less that the total value for the whole order When an entire order is cancelled, both the entitlements and the orders status are changes to Cancelled. At this point, a diary entry is also created for the cancellation and any refunds made. Refunding Cancelled Entitlements As part of this change, the Pay Invoice/Refund option that appeared in the actions dropdown has been split into two options; Refund order and Pay invoice. The Refund Order option only appears when one or more of the entitlements have been cancelled but the order itself is still active. When this option is selected the new refund page is opened (Figure 5) Figure 5

18 This design of this page is consistent with the cancellations page. The cancellation specific fields (Cancellation reason and Comment) have been removed. The key differences are as follows: Refund Options o Individual Entitlements This option is always active. Selecting this allows refunding of selected entitlements o Entire Order Entire order will only be active when all the entitlements have the status Cancelled Order details table o Checkbox The checkboxes are only active when Individual Entitlements has been selected and the status of the entitlement is set to cancelled. Refunding an order is the same as cancelling an order. You must select an entitlement and then enter the value in the refund box. Submitting the refund does not update the order or entitlement status, it just adds a refund value which is displayed in the order payment tab (Figure 6). This process also created a customer diary entry detailing the refunded amount. Figure 6 AAD-4762 & AAD-4763 Added corporate offers to the front-end and back-end This change was to allow corporate orders to be sold using the front-end checkout flow as well as making a few changes on the back end. Creating a corporate offer There has been no change to the way a corporate offer is set up as part of this JIRA. The only difference is that the corporate offer can now be displayed on the frontend by using either the preferred offer status or by using a source code which can be entered as a promo code on the front-end. These rules are the same as those for standard order types

19 Placing a corporate order Frontend The front-end flow for corporate orders is very similar to the flow used on standard order types. The key difference is that the Company Name field on the billing address is mandatory. This means that the order must be placed by a company even though a person creates the order: Select a corporate variant Log in or register o The party that places the order will automatically be added to the company that is created/assigned to the order Enter or select a billing address o The billing address now has a mandatory Company field. This is the company the party will automatically be assigned to Enter a delivery address o The delivery address is for the person placing the order and 1 copy of the product will be sent to this address. The company field is not mandatory here. Select a payment method and proceed to pay and complete the order o The order confirmation is sent to the person who placed the order The key point to take note of here is that you cannot assign people to companies using the front-end. This JIRA was only to allow the corporate order to be placed on the front-end. The only way to add a person to an order is to use the backend flow already in place. Placing a corporate order Backend The flow for placing a corporate order using the back-end has not changed as part of this sprint. The main change to corporate orders on the back end is that you can associate the company itself to an order. This means that you can send products to the company itself instead of just people within the company: 1. Open the company that has a corporate order

20 2. Select Orders >> Add to corporate order which opens a Select Company popup (Figure 11) Figure Within the Select company popup, select the company name and the Select corporate order window will be opened (Figure 12) Figure Now select the corporate order to associate the company to open the Select Product popup Figure 13

21 5. Within this popup it is possible to select the products and quantity to be sent to the company. Once finished, select Finish and the company will be added as a recipient to the order (Figure 14) Figure 14 NB: It is not possible to associate company A to Company B s corporate order, only company B can be associated to Company B s orders In addition to being able to add the company to a corporate order, there are a few points about backend corporate orders that differ to frontend orders: Creating a corporate order on the backend does not automatically assign any parties to the order (including the company) Order confirmation s can be sent to either an address or physical address using the last step of the order process (as with standard orders) The value of the orders entitlements is split between the number of recipients o E.g. A company has a corporate order that cost 100 for 10 subscriptions. If there is one recipient, the value of the recipients entitlements will be 100. If there are 4 recipients, the value of each recipients entitlements will be 25. Renewing corporate orders Frontend If any recipient of the order places another order for the same product, the new order will be a renewal and all parties that are part of the order will automatically be added to the renewal. NB: You will not be able to purchase a variant that has fewer products than there are recipients on the original order as the system will try to renew using this variant but there won t be enough products for each recipient. Renewing corporate orders Backend There is only one way to renew a corporate order using the backend and this is by using the actions dropdown that appears at the bottom of an order (Figure 15).

22 Figure 15 It is not possible to renew an order by placing another order for the same products (as is possible on the frontend) or by using renewal campaigns. AAD-4807 Added the ability to concatenate values output in BI There is now a new Concatenate values setting that appears on all columns selected to be output by BI (Figure 16). Figure 16 This new setting, when enabled, allows columns that have multiple values to be output in one row rather than having each different answer output on a new row. This makes the export more usable.

23 NB: Concatenate Values and Group Type are separate features. The design will be updated to distinguish between these settings in a future sprint Example A simple BI query is set to output Demographics >> Look up 2 for a specific party (Figure 17-18) Figure 17 Figure 18 When Concatenate values is not enabled on Demographics >> Look up 2 the filter gives the following results: Party ID First Name Surname Look up Artyom Kamarov DnB Artyom Kamarov Grunge Artyom Kamarov Hip-hop Artyom Kamarov Metal Artyom Kamarov Pop Artyom Kamarov Punk Artyom Kamarov RnB Artyom Kamarov Rock Artyom Kamarov Ska When Concatenate values is enabled on Demographics >> Look Up 2 the filter gives the following results: First Party ID Name Surname Look up Artyom Kamarov DnB Grunge Hip-hop Metal Pop Punk RnB Rock Ska The values for Look Up 2 are concatenated and the export has 1 row instead of 9.

24 8. Appendix B - Summary of changes for AAD-4509 This release is a major enhancement of all frontend pages to improve usability and the display of content across multiple devices. The improvement was initiated by the ongoing development of the subscription and registration forms but the modifications affect all frontend pages. JIRA reference AAD-4509 Description Usability issues on form Fully responsive UI to a max width of 1280px The new UI framework now will increase to a max with to 1280px and will shrink down minimum width of 300px. This new responsive layout has been designed to capture users across multiple devices ranging from desktop, tablet down to mobile phones. The area in which the forms are now displayed has been increased so there is more room for questions and two column answers to be displayed.

25 Improvements to validation There are many improvements made to the form validation which has a major affect on the usability of the forms. We have removed the live inline error messaging to streamline the completion of forms. We now show these messages after the form button has been submitted. The error messages themselves and been visually enhanced and wrap around the input fields which help focus the users attention on the question. Example of error message wrapping the entire question: Error message at mobile view:

26 Help text re-positioned Help text, if entered into the system, will appear on focus on the input fields automatically. Therefore the help text icon is no longer required making more room for the actual form criteria itself and creates less clutter on the page. The box will expand to the amount of content that has been eneterd. Help text at desktop view: Help text at mobile view: Section heading enhancement It is important to break down a large into relevant sections and make these section breaks clear with the form. Therefore we have enhanced the look of section headings, see below:

27 Text size enlargement We have increased the default text size across entire framework to allow for multi device compatibility. Devices such as the Nexus 7 and Samsung smart phones reduce the text considerably. So although the text may look large on desktop it works well across the device set. Also, we have increased the input field text size on mobile device so avoid the page zoom effect when clicking in and out of form elements. Example of payment details page on a Nexus 7:

28 Question labels aligned right Now the question column is wider we have aligned the question aligned right. This is to associate the question closer to the input fields and allow the users to scan down the options clearly. Example of the questions aligned right: Longer question titles also work well aligned right:

29 Two column layout enhanced The answer column has been made wider to support the two column layout which allows multiple answers to displayed in a smaller amount of space. Now longer names will fit in this layout, see below: Improve layout of password question The wider width allows the password question to display as a complete form component. The option to show password remains and the password strength indicator now appears below the input box. Example of password question at desktop view: Example of user entering a password with the strength indication box:

30 Right column fixed width The right hand column width now if fixed at 300px until the screen size drops below 1024px. This ensures at desktop sizes a level of constancy for content within this column. The form column scales accordingly to account for this fixed dimension. 1280px width: 1024px width: Masthead width change As the UI framework now supports 1280px width branding graphics must be uploaded at this new dimension. The images will scale proportionally to fit the device screen width. Please note that on mobile devices this graphic will scale down to a narrow width.

31