Bank Account Details Validation Section
New functionality has been added from this release to enable bank account validation to be added to eDesigner forms. This uses the Loqate third party bank details validation service so the feature is licensed separately. Please contact your Account Manager or the IEG4 Support team for further details.
When the feature is enabled there is a new item when adding a Section called 'Bank account details section'
There are 4 new global resources for this to control validation error messages in the form
- ValidationUnavailableErrorMessage
- InvalidAccountNumberErrorMessage
- InvalidSortCodeErrorMessage
- InvalidBankAccountNumberorSortCodeErrorMessage
The functionality requires 4 global settings which need to be set up by IEG4
BavaCode
BavaValidationProvider : pcapredict
BavaUrl : url of IEG4 bank validation API
Pre-populated Text and Date fields
This functionality is disabled by default so a Support ticket should be raised if you intend to make use of it.
From this release you are now able to add fields to a page that are prepopulated with data that has been added to text fields on a previous page or with today’s date. This could be used to add confirmation details to a Declaration page or to construct your own Direct Debit Mandate page for example but there will be many more use cases for this functionality.
Text fields: addition of the following options to the Text field type:
- Pre-populated value XPath
- Read-only
For a standard text field the format of the XPath is
//page[@id='page id']/field id (note this is case sensitive)
For Section fields the format of the XPath is slightly different as the field values are hardcoded and the Field ID is what you assigned to your Section when it was created. For example for the bank account validation fields the following is used:
Account number is : //page[@id='page id']/field id/AccountNumber
Sort code is : //page[@id='page id']/field id/SortCode
Example:
Date fields: addition of the following options to the Date field type:
- Pre populate with today’s date. This will be the date that the page on which the field is placed is loaded. Not the form submitted date.
- Read-only
Add a Smart Field and the Date Text field option now has the options to Pre-populate with today’s date and set whether the field is read only
A new Resource has been added for Read Only fields to enable you to configure the indicator displayed for them. This will default to read-only but can be changed to blank if required.
Capita Pay360 Service View Pan Entry Method
For Capita payments customers a new global setting can be added called CapitaPaymentServiceViewPanEntryMethod
Valid values for this are CNP or ECOM and typically you would set it to CNP. If it has a valid value and a form is started from Service View then we will use this value in the PanEntryMethod when redirecting to Capita.
eDesigner Page Logic Rules Processing
There are two new settings which cause new code to be used to process rules. When deploying this version of the framework the new logic will be applied.
PageLogicClientMode will be set to client
PageLogicServerMode will be set to native
Placeholders
The following placeholders are now supported for post submission emails in new version of the eDesigner framework.
[Firstname]
[Surname]
[AddressLine1]
[AddressLine2]
[Postcode]
[DateOfBirth]
[FormUrl]
[FormTypeName]
[Reference]