Jadu XFP: Product Updates

This release:

New Adds form variables for each field in a matrix question.
The Matrix page element provides a structured way to capture responses from your users. You can now access responses entered into a Matrix question in all form actions via the variable picker select and the placeholder modal.

New Adds the ability to book multiple concurrent slots per single event in an Event Booking question.
This is achieved by adding a 'weight'. This weight can be specified by another question, logic, or other form variables.

New Adds a new predefined logic which returns an area for a given postcode based on its prefix.
This logic allows administrators to define groups of prefixes for 'Area 1', 'Area 2', 'Area 3' and 'Area 4'. If the prefix matches one of the prefixes in an area, the name of this area is returned.

New Adds a new predefined logic which checks if an address, identified by its UPRN, exists in the LLPG data.
Some services require the property being served to be within the area served by your organisation. When using third party addressing services such as SinglePoint or ESRI LocatorHub the national property database (NLPG) is searched.
To allow form designers to confirm a property is within the serviced area this logic will lookup the UPRN in the LLPG data imported into the CMS. The result of the logic can be then be used in branching rules.

New Adds a new predefined logic which, given a UPRN or postcode, will return the ward from the LLPG data.
For some services the ward a property resides in is required so the different questions/values for that ward can be set. This predefined logic can use either the property's UPRN or Postcode to find the ward from the LLPG data imported into the CMS.

New Adds a new predefined logic which adds or subtracts days, or weekdays, from a given date.
Use the predefined logic to manipulate a date. Date manipulation is a common requirement when building forms, the service may require an SLA date to be calculated, using this logic the SLA date can be calculated by adding X number of days to the submission date.
Service design may necessitate the need to send out a notification prior to a date chosen by the customer. For example, allowing a customer to choose a collection day, using the logic to subtract X number of days from the collection day will give the date where a notification can be sent to the customer using Jadu CXM.

New Adds a new predefined logic which returns a specified part of the provided date.
Use this predefined logic when you want to get part of a date, choose from day, month, year, day of week and week of year.
Service designers often need to automate the sending of notifications which are initiated from Jadu CXM rules. In order for the rules to send the correct notifications at the right time, using parts of the date for example the month or the week of the year helps drive this automation.
Sometimes a form needs to respond to the time of year by using the month part of the date the form can behave differently for each month. For example a pro-rata amount can be calculated for each month and used when making a payment via PayBridge

New Adds a new predefined logic which returns a specified address field from SinglePoint for the provided UPRN.
In addition to the UPRN and Label of a property you may need to capture some other detail on the property such PAON, SAON, Street, Town, Postcode, County or USRN. This logic will allow you to capture that information from SinglePoint in the form for use within integrations such as Jadu CXM, Northgate M3PP/Assure and Bartec Collective.

New Adds a new predefined logic which returns a textual, comma-separated, version of a specified row in a repeatable section.
The repeatable sections on a form page provide a way to repeatedly ask the same questions and capture responses from a customer. This predefined logic allows you to access a single row of responses in a repeatable section question to all form actions and then use the value in form actions such as Jadu CXM.
Please note, in order to use this logic you must not use a text area within the repeatable section.

New Adds a new predefined logic which compares two values.
Sometimes in a form you need to make a decision based on an answer or on data retrieved from an external system such as Jadu CXM or Bartec Collective. The result of the decision can then be used in branching rules to determine the form flow.
This returns a specified value if true or another specified value if false.

New Adds a new predefined logic which splits the input based on a separator and returns either the start or end.
A form may need to contain a question with multiple options that will affect branching between pages as well as recording the response selected by the customer. In these cases setting up the required branching rules may not be possible or may become very complicated. The introduction of this substring predefined logic will allow a single value to contain multiple parts for example:

• Route1_Option1
• Route1_Option2
• Route2_Option3

Then using this new substring predefined logic the routing information can be extracted by splitting the option value on the underscore and saving the forward section.

Fix Fixes an issue where, when sending an email, using the default CSV email attachment structure contained the incorrect set of answers.

Fix Fixes an issue where, when setting up a PayBridge action on a form, the default mappings for the corresponding PayBridge service were not displayed.

Fix Fixes an issue where, when interacting with an ESRI map as part of a Location question, moving the pin prevented any further panning of the map.

Fix Fixes an issue where, when setting up form-level branching based on a newly created logic formula, the branching rule would not save.

Fix Fixes various HTML markup errors.

Fix Fixes an issue where, when setting up in-page branching on a checkbox question, the branching rule would not save if it used the 'selection does not include' operator.

Fix Fixes an issue where, when creating an email alert, underlined text was not underlined in the received email.

Fix Fixes an issue where, when submitting a form on behalf of a user, any created CXM cases were not assigned to that user.

Fix Fixes an issue where, when exporting and importing a form, placeholders in instructions text did not import correctly.

Fix Fixes an issue where, when creating a CXM case from a form, any unmapped date fields incorrectly defaulted to the current date.

Fix Fixes an issue where, after patching to Continuum XFP #75 or above, it was not possible to rollback to a version prior to this version.

Fix Fixes a usability problem where there was no obvious way to add more items to a payment basket in PayBridge.

Fix Fixes an issue where, when using Northgate M3PP predefined logic formulae, returned values contained additional whitespace.

Fix Fixes an issue where an additional character was printed at the top of any pages of an embedded form.

Compatibility

This release contains both Continuum #96 (5.10.1) and the corresponding Continuum CMS #99 (18.6.5) 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: 5.10.1

Download

Download this Continuum package from Jadu Supportal now