eDesigner

Similar to how you can map a date field in the required format to your XML (e.g. dd/mm/yyyy can be mapped to XML as YYYY-MM-DD), we need a way to map reference numbers correctly to XML. Many back office systems include a check digit on the end of the customers account reference number. So to a customer, we ask for their full reference number (inc check digit) on the form, however the API call only requires the actual account reference number to update the back office system. We need a way to format the refence number entered on the form to the appropriate length in the XML (same as eMapper options for dates). Example. Council tax account reference entered by customer 152006463866 (12 digits inclusive of check digit). I want to map the first 11 digits / trim the last digit so that the actual account number 15200646386 populate the XML payload and update our back office system.

As a Form Builder I would like to Be able to pass the form reference So that I can Use it in an XML post to a back office application

Be able to include [First name] and [Surname] placeholders for SendApplicantEmail.

We would like to add the e-form Start Date and Time, and the Completion\Submitted date and time to the xml export in eDesigner. These fields should be selectable for the xml export so we can report when e-forms are being completed and how long the customer takes to complete them.

Hi, the new developer in edesigner 2.13 for placeholders is great but it only works on the applicant email (SendApplicantEmailBody and SendApplicantEmailSubject resources). Please enable the same placeholders to work on the DefaultEmailBody and DefaultEmailSubject resources too: [Firstname] [Surname] [AddressLine1] [AddressLine2] [Postcode] [DateOfBirth] [FormUrl] [FormTypeName] [Reference] Thanks, Esther

Give the ability to enable or disable logic statements.

It would be good if we could split the pdfs on the ToAddress email after submission of a certain form, i.e. 1st pdf would be page 1 2nd pdf would be pages 2 - 16 3rd pdf would be page 17

Ability to map form data into an OpenProcess 'Account' so that if a step has an action to send a notification to the citizen this can be done using solely this data and not need a OneVu account. WHY: As a Process Builder I want to Enable citizens to report incidents that kick off processes and which send citizen centric emails So that I can send context sensitive notifications to people WITHOUT needing a OneVu account.

EITHER a) make payment items mappable to XML entries in the same way other fields are. OR b) create standard items that can be mapped to XML for the total payment taken on a form. SO THAT we know how much money has been collected on a form for further processing without having to re-do any logic.

Currently we can't provide a high quality VAT receipt to users who complete forms that take payments as we can't display they amount of VAT on a line item or total basis which is needed for a VAT receipt. We would like the payment basket summary component to optionally display VAT on a line by line basis (based on the details within each payment item) and as a set of totals excluding VAT, total VAT amount and total including VAT.