Deploying eaForms

Top  Previous  Next

Feature only available with the Corporate or Enterprise versions

 

The designer will produce a set of eaForms which they want to provide to eaForms users.

The deployment of Form Definitions is a straightforward process consisting of 3 steps:

 

1.Export the desired set of Form Definitions
2.Generate a password for the Form Definitions file

3. Deliver the eaForm definitions to users

 

 

Exporting a set of Form Definitions

 

To export a set of Form Definitions go to the Manage eaForms and

ensure that the active status for each required form is set "True" - note that there can only be a single form for a specific Element / Stereotype - plus a default that will cover all elements of a specific type if required
Press the Export button and this will prompt the designer for a filename - it is suggested that this is a filename that will be meaningful to both the designer and user
Press Save - remembering where the file has been saved!

 

Generating a run-time user password

 

Each designer will produce a password for their forms - see Generating Run Time passwords

 

Both the file and password will be provided to the user - or configured on their behalf.

 

The Form Definitions file that has been exported by the designer for the user(s) should be stored on their computer (or accessible file share) and referenced in the User Settings filename (and autoload enabled - so that the user does not have to manually load).

 

Also the password must be set to enable the load of the Form Definitions - see Setting Licence Information

 

Deliver the eaForm definitions to users

 

eaForms definitions are stored in a file which can either

be sent to users who can store the file in a location of their choice, and set the filename in their settings

or

specified in configuration file, which can be located in on an accessible server or file share, which can be referenced in the user settings so that on EA startup the relevant form definition file (plus other optional information) can be loaded.  Note: This method also simplifies updating users as they don't need to do anything to benefit from updates the designer may have made and stored in the relevant server location.