- Knowledge Base
- Technical Area
- Integration
-
Customer Portal
-
Benefit Forms
-
Revenues Forms
-
Editing Forms
-
Customer Engagement Centre (Previously known as CSVu)
-
Blue Badge and Concessionary Travel
-
Built Environment
-
AI Validator
-
BACAS
-
Health (CHC)
-
Events
-
General Form Guidance
-
Release Notes
-
Technical Area
-
Open Process
-
Forms
-
Waste Services
-
'How to...' Sessions
-
Awards and Grants
-
Social Care Financial Assessments
-
eDesigner - Community Forms
-
Tender Responses - General
-
IEG4 Team Updates
-
Internal Process Guides
-
Public Protection
-
Local Land Charges
-
BACAS Nova
How does eDesigner transfer form data?
Each eDesigner form can be configured to produce a PDF and an XML at the point of submission.
The PDF and XML files can be saved to a file system on the customers network. The form accesses the on-premise file system via the integration proxy service.
The XML file can be sent to any on-premise web service that accepts a HTTP POST request where the body of the request is XML. The form accesses the on-premise web service via the integration proxy service.