--- Legend Release Notes ---

Date prepared: Prepared by: Release No: Application Name:

29/10/2012 Ben Mathers 10.9.9 Service Pack 13 Legend Suite

10.9.9 Service Pack 13

Online Services
1. Ref #1680 Enquiry form template design tool Requirement: The ability to custom design enquiry forms for a selection of applications including swimming lessons, courses, and surveys. Proposal: To build a new enquiry form builder in the Legend CMS which can build and then insert enquiry forms into all forms of content. These enquiry forms will include layout design, colour design, free text boxes, drop down selections (including database driven Gender, Goals, Title, Ethnicity, Facility and Interests), radio buttons, checkboxes, mandatory fields, voluntary fields, definable recipients based on selections from the form and a customizable message once the form has been submitted. Implementation: The enquiry form builder can be accessed via the Site Content drop down on the CMS landing page, the option named Enquiry Forms is located at the bottom of the drop down. The enquiry form landing page will show any existing forms and a text filter to search through existing forms. Clicking on the Add new form button at the bottom of the page will load the form builder. The form builder used the same editor as the content with the addition of some new tools, shown in fig 1.1 below.

Fig 1.1 From left to right; Insert checkbox (Requires a name and value) Insert radio button (Requires name and value, to insert as a list give all the radio buttons the same name) Insert text field (Requires name, value, character width, maximum characters and type) Insert text area (Requires name, cumber of columns and number of rows) Insert button (Requires name, text (value) and type) Insert image button (Requires an image) Insert database driven drop down (Requires the data set to be used as the drop down, a pop up will show with the available data and options to preview)

Selecting any of the above elements from the toolbar will insert them directly into the content window; the elements can then be arranged and modified just as normal content. Once the form is built in the editor it now must have rules associated to it, these rules are divided into 3 sections; Recipient rules, confirmation message rules and validation rules. All of these rules are not required as there is are a default set which needs to be added for the forms but these override rules add greater flexibility when building a form. Recipient Rules This allows control over where the form will be sent once submitted by a user. A rule requires a recipient email address and then a field and value for the rule to be met. An example of the rule in use would be; Rule 1: Email address: facility1@company.com Field Name: Facility Value: Facility 1 Rule 2: Email address: facility2@company.com Field Name: Facility Value: Facility 2 This rule would send the enquiry form upon submission to either facility 1 or facility 2 depending on which facility the user selects in the facility drop down. Confirmation Message Rules The rule allows control on where the user is sent upon the form being submitted, the rule requires the content name, selected from a drop down of existing content, a field name and a field value. An example of this rule in use would be; Rule 1: Content Name: MaleConfirmationContent Field Name: Gender Value: Male Rule 2: Content Name: FemaleConfirmationContent Field Name: Gender Value: Female This rule would split the submission of the form into male and female replies and send each gender to a different confirmation message; this enables each page to be themed in a particular way. Validation Rules - This rule allows each element on the form to be assigned validation if required. The rule requires a field name, validation type and error message. An example of this rule in action could be; Field Name: Input Email Validation Type: Email Error Message: Email is not a recognized email address; please enter a valid email address. Field Name: Input Name Validation type Required Field Error Message: Please enter a name

The first of these rules uses a text input field named email address to check if the text entered into the input field is actually an email, if it is not a valid email the error message will be shown, if it is a valid email then the form will continue to check any more validation rules or submit. The second of these rules checks to see if the user has entered some text in the input text field with a value of name. If nothing has been entered the user will be shown an error message, if the input field has something in it then the form will continue onto any additional validation and then submit. Rules can be edited at any point, to refresh any of the drop down to include the relevant content click the small arrow next to the required rule. To remove a rule click the red arrow next to the rule or the rule criteria. Before saving the form it requires a name, a default recipient email address (email address used if the recipient rules arent met), default confirmation content (content shown to the user upon submission if the confirmation rules arent met) and a subject for the form which will be shown in the email subject when receiving any submissions. Once the form is saved it can now be add to any piece of content by using the insert enquiry form option from the toolbar in the editor. Upon clicking the button a pop will show with a list of all available enquiry forms, the enquiry form will be inserted in a similar way to a macro where the form content is locked unless you are editing the form itself. 2. Ref #2310 Membership filtering Issue: Shibboleth roles did not filter renewals and add ons like it did the online sign up process. Solution: The roles for Shibboleth add ons and renewals now only show the relevant agreements for the user to select. 3. Ref #2465 Lapsed members cant renew Issue: If a member moved into a lapsed state the member could not renew their agreement. Solution: The standard renewal options are now allowed for a lapsed member. 4. Ref #2422 Class timetable view Issue: The kiosk timetable view opened by showing the first time of the day, for a member using the kiosk this made it difficult to find the activity that was later on in the day as they had to scroll through all the time slots. Solution: The time table view now defaults to an hour before the current time. 5. Ref #2524 Profile fields Issue: When the lock profile setting is enabled it was still possible to tick and un-tick the marketing preference fields even though nothing happened when doing so. Solution: These tick boxes are now disabled and cant be altered if the lock profile setting is enabled. 6. Ref #2523 Add On agreements online Issue: When adding Add On agreements online the website took no notice of the limit the head agreement sets for the number of add ons that are allowed. Solution: The website now checks how many add ons should be allowed against a head agreement and does not allow any more than that to be added.

7. Ref #2510 Non online subtypes showing online Issue: Sub types that were not set to show online were picking up incorrect settings from either resources inside them or associated sub types against the resource. This made the sub type show online. Solution: Only online sub types will now show online. 8. Ref #2509 Online sports hall subtype online description Issue: The sports hall subtypes were showing random descriptions online. Solution: Descriptions have been removed from sports hall subtypes as they are not required. 9. Ref #2376 Online signups not showing in applications Issue: Under certain circumstances members that sign up online are not being pulled through to the core Legend applications, when a member is searched for in Membership Management or FOH they would not be found. Solution: Fixes have been made to various areas of online services to ensure members are correctly passed through when signing up to an agreement online. 10. Ref #2375 Expanding Other membership options for online renewals Issue: When a member cant renew to their existing agreement the other options is not expanded. Solution: The other option will now be automatically expanded so the member can easily see additional choices. 11. Ref #2374 Printing terms and conditions Issue: When printing terms and conditions from firefox or internet explorer the text size was very small making it hard to read. Firefox also only printed the first page. Solution: The text size has been altered to reflect the true font size and Firefox now prints all pages requested in the print. 12. Ref #2661 Booking status not being set to attended on the Kiosk Issue: If a member made a booking in FOH and it somehow was not automatically set to attended by FOH the kiosk would not set the booking to attended even after the user attempts to attend. This enabled members to print multiple tickets from the kiosk for the same booking. Solution: Once the member attends the booking in the kiosk it sets it to attended. 13. Ref #2746 Unable to process add on members with terms and conditions Issue: If a member attempts to add on memberships that have terms and conditions associated with them the application gets stuck in a loop where the user is unable to complete the transaction. Solution: The online sign up add on process now handles the terms and conditions in the same way as a head member, once they have been accepted the user can complete the transaction.

Reports
1. Ref #2058 Additional column for class utilization report Issue: A club name column is required for the location that the class took place. Solution: The club name column has been added as the first column to the class utilization report. This column states the location that the class occurred.

2. Ref #2414 Discrepancies between financial reports Issue: Records were repeating in the transaction detail report. Solution: Transaction are no longer duplicated in the transaction detail report. 3. Ref #2370 Cashing up discrepancy Issue: A problem was identified with the Category Summary report where it splits the total transaction amount and divides by the number of items in the transaction which results in the incorrect transaction amount across a transaction. Solution: The category summary report will now match the cashing up receipts. 4. Ref #1496 Course attendee report doesnt show members paid status of N/A Issue: If a member has a paid status of N/A they would not show in this report. Solution: Members with a paid status of N/A will now be shown in the report as they are to attend.

Bookings
1. Ref #2017 Course import doesnt validate the resource availability Issue: When importing a course the system does not check that the area that will be booked is not already booked out. This can result in double bookings. Solution: The course imports will now error on the grounds that the linked physical/human resource is not available for that date or time. 2. Ref #2011 Rollover attendees does not move all members Issue: In certain cases the rollover attendees does not move all member to the new course. This was generally due to drop ins and selected sessions. Solution: The rollover attendees form now takes into account drop ins and members enrolled onto selected sessions and will roll them over if required. 3. Ref #2470 Booking charges on booking penalties Issue: Within Booking Attendance and configuring the Attendance Configuration - if the Inactive Date is blank, no booking charges are calculated and the member doesn't receive the charge. Solution: The charges are now raised in spite of the missing inactive date. 4. Ref #2464 Patronage values incorrectly reported Issue: In some cases bookings are not picking the correct value from the inventory drop down box when creating the booking. Solution: The inventory override will now always be logged against the booking which will record patronage correctly. 5. Ref #2419 Overridden strikes and bans Issue: Overriding a strike for a member who has two bookings, one of which gets cancelled, the incorrect status will be set against the member, cancelling the booking will then be overlooked. Solution: The correct status and strikes will now be listed against the member, even when some of their bookings are cancelled.

6. Ref #2055 Search bookings error Issue: When searching a child resource without selecting the parent resource in bookings the application shows an error stating that the user is required to select a resource. Solution: The functionality has been altered to include searchable child resources without having to select the parent resource.

FOH
1. Ref #2014 Course registers sorting Issue: The register in FOH course view differed to the register list in Bookings. Solution: The sorting order in the two applications is now the same, by surname. 2. Ref #2012 Moving a member more than once Issue: It is not possible to move a member to a course more than once in FOH. Solution: It is now possible to move a member more than once. 3. Ref #1901 Spelling mistake when issuing a refund Issue: If the basket is in refund mode and the user attempts to add another member to the transaction an error message shows with the word voucher spelt incorrectly. Solution: The spelling has been rectified and is now spelt correctly.

Membership Management
1. Ref #2468 Paying member charges Issue: In certain circumstances members had different balances between FOH and MM. This meant that the balance could not be cleared in MM or paid off by FOH. Solution: Alterations have been made to reduce the risk of members having a different balance between the two applications. 2. Ref #2158 Crash on statement print or view Issue: Attempting to print or view a statement in MM caused the application to crash. Solution: The application will no longer crash upon viewing the statement. 3. Ref #2531 Unable to change add on member agreements Issue: When manually updating an add on members agreement the list of agreements doesnt include add prices, just prices available to head members. Solution: Both head member and add on member prices are now included in the list when manually editing a members agreement. 4. Ref #2522 Add on member wizard not filtering agreements Issue: In the add-on member wizard the member eligibilities are not correctly loaded based on the agreement selected and all options are shown regardless. The filtering was applied correctly in the NMW. Solution: The agreement eligibilities are now loaded correctly based on the selected agreement, going back and changing that agreement also reloads the correct eligibilities.