Current Filter: Document>>>>>>

   

BACKGROUND
eForms are essentially structured data entry screens used for collecting data which can be used to feed any number of front and back-end systems used in business processes, for example, HR and ERP applications, reporting tools, letter generation, etc. But these forms must not be seen as simply tools for data collection - this is just the start. The essential functionality must include:

= Ability to use a form that interactively changes according to the needs of each individual user's session. The user simply fills out drop down lists, and depending on one answer, different choices are given for the next questions - intelligent navigation.
= Users are led through the process of filling a form from beginning to end with a point and click interface. As a user answers questions, a form is built electronically.
= Forms link to supporting documents of all types
= Form design should not require programming although it is understood that more complex forms will require some IT input - users who understand the business process are ideally placed to design forms
= The eForms system is independent of any back-end business system, although it can be integrated; consequently, it can be used to collect data for any back-end system, including centralised information repository systems
= Upon completion, the form is automatically saved and integrated into a back-end repository, which allows users to access and search for the form based on data populated in the form. Receipt of the completed forms may trigger back end workflow processes.

Crucially, eForms must be detached from any front-end application, to avoid counting eForm users as concurrent users, eliminating any licensing implications. The system should support un-limited access by internal and external users.

Equally, eForms must not be seen in isolation from a planned information strategy. An eForms Framework helps to define a business strategy - simply deploying an eForm will not deliver that strategy.

WHERE ARE WE NOW?
Advances in eForms and mobile devices open up new options for collecting and analysing data. The boring chore of form filling - paper or electronic - is in the past. With a tablet, the user is essentially left with the fingers of one hand to carry out data entry tasks. Rich user-interface controls such as sliders are replacing click based controls such as drop-down lists and calendars.

But simply replacing established data entry controls with new gesture based controls is not sufficient in itself. eForms are being designed to be device agnostic and provide instant feedback during data collection to help the time-pressed user who needs to easily collect and analyse data. As a minimum, eForms must:

• Be usable on any mobile device, without having to manage versions for each device type
• Allow the user to rapidly collect data using rich user interface controls
• Validate data collected and save it for reuse
• Perform simple and complex calculations using the data collected
• Display and feedback to the user selected results to support analyses and reporting, including dashboard-style charting

The device-agnostic requirement is key: eForms should not be designed to work on a specific platform. Installing an app on an iPad may be terrific as it provides access to the rich user experience on this specific device - but what about an Android or a Windows tablet? Will suppliers develop and maintain eForms for each platform? This will become cost-prohibitive very quickly. It makes sense to design and develop the eForms once, install it on a secure server and provide access to the electronic forms using any device. Furthermore, the success of the mobile platform stems from the fact that it's a device which connects a mobile user with the office - i.e. it is a connector and need not hold any data locally. This is a welcome message for IT and Compliance people in organisations which worry about mobile devices becoming mobile - losing such a device is an acceptable risk; losing corporate data is not!

Page   1  2