2.6 eDesigner Release

This version of eDesigner includes multiple updates.

i) Capita Payment Integration - Prepopulation

enhances the no-code Capita Payment integration functionality so that any of the following can be passed to the Capita payment system:

PersonTitle
Firstname
Surname
Email
AddressFieldsAddressLine1
AddressFieldsAddressLine2
AddressFieldsAddressLine3
AddressFieldsAddressLine4
Postcode

Ultimately ensuring that it is quicker to make / take a payment from a form.

The functionality is accessed using the 'Payment Settings' button on the Designer menu:

Screenshot_2021-01-21_at_10.38.00.png

Once in here one can see there is a new 'Pre-populate customer details in payment system' option:

Screenshot_2021-01-21_at_10.17.51.png

If this is checked/ticked then the following fields (using the standard fieldids) from the 'Standard' or 'Blank' Who Are You page will be used to to pre-populate the Capita payment screen.

PersonTitle
Firstname
Surname
Email
AddressFieldsAddressLine1
AddressFieldsAddressLine2
AddressFieldsAddressLine3
AddressFieldsAddressLine4
Postcode

There is also an option to pre-populate these pieces of data from any page within the form. To do so you need to check the 'Override default 'Who are you' field XPaths' option.

An XPath is a technical term to indicate which field on which page of the form you want to refer to.

So in this case the XPath can be used to override the standard behaviour if:

a) You don't have a WhoAreYou page

b) The details to prepopulate are on a later page.

The UI is illustrated below:

Screenshot_2021-01-21_at_10.22.41.png

To help give an example let's say you have built a page called My Information and you want to use the email address from that page in the pre-population of Capita. If you go to that page you will see its XPath name in the URL.

I.e. this form is PAYMENTTEST, the page it is on is myinfo as that is what is shown in the URL:

Screenshot_2021-01-21_at_10.28.26.png

So in the XPath description we need the page id to be myinfo:

page[@id='myinfo']/....

But this only tells eDesigner which page the field is on. The next thing you need to do is add the field id for the field you want to map. So if the Field ID for the form is myinfoemail, as shown in the screenshot below:

Screenshot_2021-01-21_at_10.33.32.png

The XPath override value would be:

page[@id='myinfo']/myinfoemail

We can see that we have adjusted which field will be used to pre-populate Capita by placing the above into the Email override field:

Screenshot_2021-01-21_at_10.35.12.png

ii) Email Validation

When users provide an email address the maximum number of letters at the end beyond the last full stop e.g. ieg4.com / co.uk was set to 4 in the validation messaging.

However, reflective of new options like .online we have increased the number to 50.

ii) Address look ups inside repeating sections

We have enhanced repeating section functionality so that it is possible to have an address look up within them that is accessing the data via API.

Before spurious results would be presented in repeated sections if this was attempted.

iv) Items resolved

a) The setting 'TreatStartPageAsWhoAreYouPage" mentioned in the location below was not resulting in email receipts being sent on save for later/submit despite this being set to true. This has been resolved.

Email Receipts - Default Page setting – IEG4

b) It was noticed that within the timeline for a form in the Form's portal that page load times were not being updated. This has been resolved.