Creating a custom Questionnaire frontend


#1

Hello,


I’m trying to build a custom Questionnaire front end. The workflow is:

* A PDF with a form gets uploaded.
* A process finds the the form fields.
* A custom domain specific frontend in our application displays those fields for user input.
* The user enters the field values.
* Based on that, a PDF with the form filled gets generated.

Now there are two probably approaches to this:

1. Uploading a PDF form document and then adding a datasource with datasource fields based on the user entered values. Code snippet.

The problem with this approach is that Document::Field does not expose information like: field_type (text, multi-choice, boolean), is required, max field length. This is ofcourse needed to capture the user input in our application.

2. Uploading a PDF form document such that it creates a Questionnaire. Then the Question’s text can be auto mapped to the questions name via the API. We don’t care about the Question’s text as its already present in the PDF as a label next to the field. Doing this puts the Questionnaire in an active state. Now perhaps Executions, Datasource, DataSource::Fields can be created for it. The advantage for this approach is that Question exposes the field type information, which we need - although it seems roundabout as compared to the first approach.

I’m using the Ruby SDK. Can also use REST directly if it isn’t in the rubygem yet.


Any thoughts on this would be much appreciated.



#2

Hi Akshay,

Thank you for providing the necessary details.

Our devs have started investigating this.They have already started implementing the required additional data in questionnaire fields. We’ll be updating the API with the mentioned changes soon.

Your latest post (http://groupdocs.com/Community/forums/thread/528/incorrect-questionnaire-pdf-form-field-type-detection.aspx/) depends on this data, so that query too will be resolved ASAP with the same release.

We truly appreciate your cooperation.

Kind Regards,
Vipin Thomas, GroupDocs Support


#3

UPDATE: These requests have been implemented in the latest Ruby SDK version 1.5.7

Please feel free to contact us if you need anything else.