E-Forms can be used from outside resources by calling into the system to fill out forms. This is typically used for sending someone from outside the system into DocMgt to fill out a form. The form can then send the user back to whatever page you wish in order to provide the user will a full-circle experience.


Prerequisites

  1. Your server must be available to the "outside" users. For hosted users this is already provided. For in-house or on premise systems you must be sure the server can be accessed by the users who need access.
  2. The forms to which you send "outside" users must be marked as Public in the Form / Advanced Settings section of the form designer.


From your web page you would include a link or a redirect to the URL of the form you wish to have the users fill out. This is just a URL on you DocMgt server that has a variable value on the end that is the ID of your form. For instance, if your main URL to DocMgt is https://myserver/dm and the public form ID is 10 then your public form URL would be https://myserver/dm/eforms/10. When users are directed there from redirect, link, JavaScript or whatever means, they will see the form and can fill it out as necessary.


Sending Information to Form

Another added feature with this is the ability to supply field values via the query string. If the name of the query string variable must match the name of the field in the form then the value of the query string variable will be populated into the form. This is an easy way to send information into a form


One other feature is the ability to send in search data to the form so a Record can be found and the form can be filled from that Record.To do this you must send in the field name / value pairs in the query string. The form must also be configured to look for those variables to do a search by adding the field names to the "Record Lookup Fields" field in the form.


Directing the User When Finished

In order to have the users "bounce" back to the correct page on your site when they are done with the form there are 2 fields you will need to fill out in the Form; Save/Cancel Events settings - Public Save URL and Public Cancel URL. 


There is more detail on the Save/Cancel Events page but basically the Public Save URL is where the users will be directed once they save the form. The Public Cancel URL is where the users will be directed if they click the Cancel button from your form.


Sending Information Back to Calling System

You can also include variables on the return URL so you can get information from DocMgt that you can log or use for more interaction with the system. Here is a list of the variables you can code into the Public Save URL.

  • [RECORDID] - This will be replaced with the ID of the Record that the form was saved into.
  • [DOCUMENTID] - This will be replaced with the ID of the Document that the form created.
  • [EFORMID] - This will be replaced with the ID of the E-Form that was used. This should be the same ID as you sent in on the URL to begin with.


For instance, if your return URL is http:/myserver/return and you wanted to know the Record where the form was saved you could enter http:/myserver/return?RecordID=[RECORDID] in the Public Save URL and on your server you would check for the RecordID parameter on the Query String to see what that value is. You could either log it or save it or even use the DocMgt REST API to make a call directly back into the system to get the data that was saved into that Record.




With this set up you can have forms filled out and saved into DocMgt and can leverage that data in any other system you wish by direct communication or by using one of the other Integration Options available.