Release notes
From OpenQuote
Contents |
Release Notes - OpenQuote - Version 1.2RC3
Bug
- OQ-187 - Alfresco major/minor check-in labels reversed
- OQ-189 - Link to sample policy wordings does not work
Sample wording link on quotations page corrected to use an externally accessible URL. If the wording is held within Alfresco, the document's permissions must allow for external access (i.e. the Guest user has Consumer rights).
Improvement
- OQ-186 - Add google analytics to portal layouts
Added google analytics to the footer of portal page layouts.
Task
- OQ-185 - Add LifePlus to the home page
Added link to new TermLife product quote page to the home page.
Release Notes - OpenQuote - Version 1.2RC2
Bug
- OQ-182 - OpenQuote hangs when the Sandpit tab is opened
RC1 issues with the deployment of product content during installation process fixed. Under RC1 product content was not being correctly setup when the server was first started.
Release Notes - OpenQuote - Version 1.2RC1
Improvements
- OQ-181 - Document apparent problems with window's zip tool in installation notes
Release Notes - OpenQuote - Version 1.2EA2
Bugs
- OQ-132 - In a PageFlow RowScrollers cannot be embedded in QuestionSections
PageSections within PageFlows now correctly pass renderHeader requests down to their sub-elements. Among other things, this now means that RowScrollers embedded with a PageSection correctly render drop downs based of attributes of type choice. In the past an empty drop down would have been rendered. - OQ-145 - Question validation ignores question condition rules.
PageFlow validations (and request/model value binding) now respects the element's "condition" property. Prior to this release a PageFlow element's "condition" property could be user to prevent it from being rendered, now it also prevents binding and validation form taking place for that element. - OQ-167 - RowScroller add and remove buttons can't be used from selenium tests
The RowScroller add and remove buttons used to be assigned randomly generated IDs in the form '#xxxxxx". Being random, tools like Selenium could not reliably drive the screens during testing. As of 1.2 all elements are given unique IDs in the form OQX-X-X-X.... based on their page positing and nesting in the PageFlow. - OQ-169 - The 'required' option doesn't work on yesorno questions
- OQ-170 - Choice attribute format only supports '?' as a default value.
It is now possible to "translate" the values in a choice attribute's option list into language or product specific strings for use on the user interface. Internally, within the product's model, the representation remains unchanged from previous releases. For example: <attribute ... format="choice,options=-1#?|1#Male|2#Female"/>. However, during the rendering process the values ("?", "Male", "Female" in this case) are passed through OpenQuote's I18N process allowing them to be overriden by a product specific translation. If, for example, you wanted to use '-' rather than '?' to represent the undefined value on the UI, and show "Male" as "Man" and "Female" as "Woman" you would add the following Translations.xml file to your product:<translations defaultLanguage="en" xsi:type="java:com.ail.core.language.Translations" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <translation language="en"> <element key="i18n_?">-</element> <element key="i18n_Male">Man</element> <element key="i18n_Female">Woman</element> </translation> </translations>
You also need to have the following in your product's Registry.xml to allow your product's Translations to extend those in the Base product:
<configuration ...> ... <type name="Translations" builder="CastorXMLBuilder" singleInstance="true" key="com.ail.core.language.Translations"> <parameter name="Extends">super.Translations</parameter> <parameter name="Url">./Translations.xml</parameter> </type> ... </configuration>
- OQ-171 - Switching the browser locale does not affect the rendering of locale specific fields
Fix to ensure that the browser's locale is correctly passed into the page rendering process such that both UI widgets and other services can see it. - OQ-174 - QuestionWithSubSection doesn't enable the subsection on refresh for radio buttons
QuestionWithSubsection fixed so that it opens correctly when the question is rendered as radio buttons. - OQ-175 - Choice AttributeFields based on a Type do not validate correctly
Validation fixed so that an undefined selection ("?" by default) is caught during validation even if the "?" symbol has been overriden by I18N settings. I18N can be used to replace the default "?" symbol, which choice lists generally use to indicate that a selection is needed, with another symbol. Prior to this fix, do that would result in validation assuming that a selection had been made. - OQ-178 - questionWithDetails sub details bug if renderHint="radio"
QuestionWithDetails with renderHint="radio" will now correctly disable all of the detail question's radio buttons. - OQ-179 - Question validation ignores parent question/page section condition rules.
When a PageContainer (e.g. PageSection, QuestionSection, etc, etc) defines a condition to control whether it is or is not rendered, that condition is now taken to apply to the contents of the container too and prevents the contents from being validated. If the user cannot see the content, validation is not performed.
Improvements
- OQ-172 - Remove errors logged during startup and normal operation if they are not significant
In a number of areas suprious or unnecessary logging has been removed. Most notably, the exceptions thrown by Alfresco in response to requests for content that does not exist are now turned off as this represents normal activitiy. The server now simply returns a 404 instead. Warning messages related to type merging/cloning are also avoided now. - OQ-173 - Add automatic reformatting of numbers to locale specific formats on field exit
The AttributeField widget now uses NumberFormat (http://www.mredkj.com/javascript/numberFormatPage2.html) to reformat number in a locale sympathetic way on field exit.
Release Notes - OpenQuote - Version 1.2EA1
Bugs
- OQ-149 - Exception thrown during broker email render
- OQ-160 - PageScript does not inject JavaScript into generated pages
- OQ-163 - QuestionWithDetails and QuestionWithSubsection ignore the detailsEnabledFor setting
Improvements
- OQ-155 - Generic portlet that can be used to access any product
- OQ-162 - html and xforms forms need to refect questions mandatory status
- OQ-164 - Allow QuestionWithSubSection to contain many sub-element, not just one
New Features
- OQ-159 - Improved eclipse support for product development
