Continuum XFP #123 (8.2.0)

This release:

Update Improves compatibility with photon forms.

Photon sites use the twig templating engine. One of the advantages of this approach is the reuse of common components across the site. Photon defines a form.html.twig template that forms the basis of all forms across the site. User registration, new event submission, new directory entry submission and XFP forms are all examples where form.html.twig is used.

Occasionally the forms.html.twig file may be edited to support functionality such as uploading files on non XFP forms. This can cause issues with compatibility with XFP. We have changed the way XFP uses the form.html.twig template so that it can be edited for non-XFP forms on the site without affecting XFP forms. This change doesn't affect the way XFP forms function instead it allows future customisations on a per site basis.

Impacts: Progression and submission of forms with and without payments via the web and internal channels. No change in behaviour is expected.

 

Update Updates Blue Badge Integration to add support for changed person details (on badge replacement application) and "Assessed as a 3 year old" to the Blue Badge integration.

Releases #87 and #88 of the Blue Badge Service introduced some new fields which our “Blue Badge - Application” logic has been updated to support.

Three new options have been added to the "Application Detail" option in the "Blue Badge - Application" logic. These are:

• Person - Assessed as a 3 year old?
• Have personal details changed?
• Changed personal details

Impacts: "Blue Badge - Application" logic "Application Detail" list options.

 

Update Improves the performance of the Data Export control centre interfaces.

We have improved the loading times of the Data Export pages in the control centre by removing unused code.

Impacts: Load times for Data Export control centre interfaces.

 

Fix Fixes issues with character encoding on WISP systems.

Jadu supports installation on both LAMP (Linux, Apache, MySQL, PHP) and WISP (Windows, IIS, SQL Server, PHP) environments.

Entering non-ASCII characters into the form/page instructions content would result in character encoding errors after saving. For example, entering a £ sign into form instructions would result in output of Å£. Similar output would result for other non-ASCII characters such as the copyright symbol ©.

Impacts: System wide, input fields for settings and WYSIWYG editor content in the control centre and on the website.

 

Fix Fixes the validation message displayed when a repeatable question has 1 required row.

A repeatable section can have a minimum number of responses set. This is set using the "Minimum required" setting. If this is set to 1 and the user filling in the form doesn't answer the repeatable question a validation error will be triggered and the validation message "This table should contain at least 1 rows" would be displayed.

We have updated the validation message so the singular "row" is displayed instead of the plural "rows" when the minimum required setting is 1.

Impacts: Repeatable question minimum required rows validation message.

 

Fix Fixes an issue where Google Maps Street View was available in the location component.

We have disabled the ability to switch into street view when using the location component with Google Maps.

Impacts: Location component with Google Maps as the mapping type.

 

Fix Renames "Logic Definitions" and "Conditional Logic Definitions" to "Definitions".

Definitions allow a constant or date value to be defined and used in your forms, for example the renewal date of the service can be defined as a definition and used across the forms related to the service. When definitions were first introduced they could only be used in conditional logics, however over time we have enabled definitions in more areas such as mappings, placeholders and prefills.

The terminology used to reference definitions was inconsistent, "Logic Definitions" was used in the XForms Pro menu, "Conditional Logic Definitions" was used as the page title for the control centre page to manage definitions and "Definitions" was used everywhere else.

We have standardised the naming of "Definitions" throughout the control centre. There are no changes in how definitions function as a result of this change.

Impacts: Naming convention of "Definitions" throughout the control centre.

 

Fix Fixes an issue where it was possible to create a Definition with the same name as an existing Definition.

Definitions are identified in the variable picker and the insert placeholder modal by the name of the defintion. Using the same name for more than one Definition makes it difficult to identify which definition is being referenced. We have updated the save routine when creating and editing a defintion to enforce a unique name.

If you already have definitions that share a name the definition name will be updated to append the ID of the database record to the name on deployment of this version.

Impacts: Validation applied when creating a new or updating an existing Definition.

 

Fix Removes "New Definition" option from the "Actions" menu on the "Definitions" page.

We have removed the "New Definition" option from the "Actions" menu in keeping with our UI design guidelines. The primary action "New Definition" appears above and to the right of the list of items.

Impacts: "Actions" menu options on the "Definitions" control centre page.

 

Fix Fixes a number of issues relating to invalid HTML markup on the "Logics" pages when managing form logics.

We have resolved a number of HTML validation errors on the Logic pages in the form designer. No change in behaviour is expected as a result of this change.

Impacts: HTML markup of the Logics page in the control centre.

 

Fix Fixes an issue where it was possible to save a Literal Logic without a formula.

Literal logics allow form designers to create a literal string for use within the form. The string can be made up of a combination of variable and text blocks. This update ensures the literal logic formula contains at least one variable or text block.

Impacts: Literal logic formulas.

 

Fix Fixes an issue where it was possible to add multiple validation messages in the same language.

Under the Validation Routines module, validation messages can be defined that are displayed when a response entered into a question fails validation. Messages can be set in either English, Welsh or Polish languages. An issue allowed a validation message to be set multiple times for the same language. We now prevent being able to set a validation message in a language that already has a validation message.

Impacts: Editing of validation messages.

 

Fix Fixes showing of the "Forms unavailable" message when forms are offline in classic templates.

Whilst patching a site forms are taken offline whilst the patch runs. During this time if a user tries to access a form they are redirected to the forms list view and shown a message stating that forms are currently unavailable. This message wasn't shown on sites that use the classic templates (non photon). We have resolved the issue that prevented the "Forms unavailable" message from being displayed.

Impacts: Displaying of "Forms unavailable" message when forms are offline on sites built using classic templates.

 

Fix Fixes an issue where an unanswered "Verified Address - Business Name Search" question is shown on the form review page.

The form review page allows users to review their responses before submitting the form. Only questions that have been answered are shown on this page. Questions using the "Verified Address - Business Name Search" integrated component would appear on the review page even if they were unanswered. We now prevent these questions from showing if they are unanswered.

Impacts: "Verified Address - Business Name Search" questions displayed on the form review page.

 

Fix Fixes an issue where importing a page template would append "(-1)" to the title.

Page templates can be exported and imported separately from forms. When importing a page template into a system that already has a page template with the same title the title of the imported page template will be appended with the ID of the page template e.g. "(123)". If the system the page template is being imported into doesn't already have a page template with the same title the page template title should not be changed.

We have resolved an issue where "(-1)" was being appended the page template titles after importing the page template into a system that didn't have an existing page template with the same title.

Impacts: Importing page templates.

 

Fix Fixes an issue where category stylesheet wasn't applied to modern forms.

Jadu sites allow you to change the look and feel of specific sections of your website, this is managed under Utilities > Stylesheets and applying a different stylesheet to different categories and content types. When applying a stylesheet to a category and the form content type, all forms under this category should be displayed on the website using the applied stylesheet.

We have resolved an issue where forms created in the modern form builder would not have the correct stylesheet applied to them.

Impacts: Look and feel of forms on the website that are categorised under a category that has a stylesheet applied to the forms content type in Utilities > Stylesheets.

 

Fix Fixes an issue where "jump to error" link didn't work.

When completing a form page and proceeding to the next page of the form, the responses provided are validated and any errors found with the supplied responses are displayed above the question for review. Users can jump to the error question using the link provided. When a form is embedded into a site on a different domain to the site that is hosting XFP the links to jump to the question didn't take the user to the question. This issue only affected embedded forms embedded into a page on a different domain.

Impacts: Embedded forms embedded into a page on a different domain to the domain hosting XFP.

 

Fix Fixes an issue where extra whitespace was prepended to a textarea response when the page question page failed validation.

When a user answers a textarea question on a form page and continues through the form, if their responses fail validation on the textarea question or any other question on the page (e.g. a required question hasn't been answered), the form page will reload allowing the user to correct the validation error(s).

When the form page reloaded the response in a textarea question would have whitespace appended to it. We have removed this whitespace.

Impacts: Responses to textarea questions.

 

Fix Fixes an issue where it was not possible to set mappings in the "Create PDF of Submission" template.

The "Create PDF of Submission" template allows PDF form fields to be mapped to form variables such as questions, logics and form metadata.

We have resolved an issue where it was not possible to activate the mapping select field in order to set or update a mapping.

Impacts: Setting and updating mappings on the "Create PDF of Submission" template.

 

Fix Fixes an issue where it was possible to move a page element with duplicate Question Text into a section.

Question Text has to be unique within the section it is contained within, for example on a page template with no sub sections only one question can have the Question Text of "Jadu". If a page template has subsection, a question with the Question Test "Jadu" can exist in the main page template body and the subsection.

Using the arrows to move a page element within the page template designer, it was possible to move a question into a section that has the same Question Text as an existing question within the section. We have added extra validation when a question is moved into and out of a section to prevent this.

Impacts: Page template designer.

 

Fix Fixes an issue where an existing Connector doesn't update with new settings when saved.

A Connector is a set of connection details to a target system. These can be SFTP, FTP or SCP credentials, or just a folder on the current system. Connectors are set up within the control centre under XForms Pro > Connectors.

We have fixed an issue where if you edit an existing Connector and change the type of connection the Connector details are not updated.

Impacts: Editing existing Connectors by changing the type of connection used.

 

Fix Fixes an issue where hourly data exports may not run every hour in non UTC timezones.

When a data export is run via a schedule the next run date is set so the export will be picked up again in a future run. When calculating the next run date the correct timezone wasn't being used and this resulted in the next run date being calculated incorrectly.

We now take into account the timezone when setting the next run date.

Impacts: Scheduled data exports in non UTC timezones.

 

Fix Fixes an issue where metadata details were not created when importing a form or using Save As

All forms must have metadata assigned when setting up the form. When importing a form or using Save As to create a copy of the form this metadata wasn't being set on the new form.

Impacts: Metadata details when importing a form or using Save As to create a copy of the form.

 

Fix Fixes an issue where PDFs generated by the "Create PDF to Sign" template action were not included in Data Export.

The AssureSign integration allows PDFs to be created that are then signed at AssureSign. These PDFs were not included in the "Generated PDFs" output from Data Export. We have updated Data Export to include these PDFs in the ZIP file.

Impacts: Exporting PDF files using Data Export when AssureSign integration is enabled.

 

Fix Fixes a potential security issue within the Data Export API interfaces in the control centre.

Jadu doesn't disclose details of security issues publically. If you require details of this issue please contact Jadu Support.

Fix Fixes a potential security issue within the connector setup interfaces in the control centre.

Jadu doesn't disclose details of security issues publically. If you require details of this issue please contact Jadu Support.

Fix Fixes WCAG 2.1 compliance issue within embedded forms.

 

Compatibility

This release contains both XFP 8.2.0 and the corresponding Continuum CMS 21.3.2 in a single package. There is no need to apply the Continuum CMS package separately.

If you are unsure of compatibility please speak to Jadu Support who can advise.

Semantic version number: 8.2.0