This component allows your code to open blank forms populate them with data, handle user form viewing, filling, validating, data extraction and high quality printing. The component is supplied as an ActiveX component.
When this component is added to your desktop application project, all of the features of eForms and eDocuments can be controlled using simple code. Although simple, the code has masses of power with literally hundreds of programming methods, events and properties at your programmers disposal.
With eForms under the control of your application, programmers can build your own viewer/filler applications to meet exactly your application’s needs. We also supply a ready-made viewer / filler application which can be used as your application.
The core ActiveX component is also used on server applications, for opening and manipulating form files. It can be used for batch printing document sets.
The package component is used in conjunction with a desktop application.
The packager component allows filled forms to be packaged together into a single file. This file can then be sent to remote locations or returned to base by email, ftp or http transfer. Users of your desktop application can therefore send and receive packages of forms and documents, to be stored, viewed, printed, etc. The advantage of the packager adds key benefits:
- Files are encrypted and password protected. Even if sent across the open internet, they remain secure from prying eyes.
- Form packages can contain many different forms and documents, and also additional attachments, such as photos, word documents, etc
- Form packages can be created by a server “on the fly”.
Form templates are opened within an unmodified browser. The browser eForm component presents an API, which you can control using browser scripting.
If you wish you can write your own viewer/filler application to control the form, alternatively, we supply a pre-written viewer/filler, which is also supplied as our internet forms product.
This software presents users with a signing window, when they click into a signature field in an eForm. It captures their signature as they write on a signing pad, encodes it in data, and embeds the encoded image in the document.
Our form data is produced in a simple, open XML format, which can easily be read and manipulated by your own code. However, if your application requires form data to be formatted according to a complex XML schema, writing the code to do this manually is very time-consuming.
Our XML Toolkit is a software add-on which dramatically cuts development time:
- Import a XML schema document into our system – you can use third-party XML editing tool such as XML Spy to view, create and edit these.
- Open the form design file with our design software, and add the XML element tags to data fields – this maps form data to the XML document.
- Where necessary, additional functions can be called to define how form data is handled during the conversion to XML (specifying date format, specifying attributes of an element, etc).
- When your application receives form data, your code can then invoke the XML generation software – it converts it into complex XML format as defined by the imported schema.
Our PDF output converter is an ActiveX object which works as an add-on to the Core eForm component. It converts forms and data in our own format into industry standard PDF; flat and fill-able. It works with desktop applications, and running as an unattended server process.
For internet applications that require PDF document generation that uses the PDF Output Component, we supply a ready-made solution – the PDF Document Server.