Enterprise Forms has a mechanism called Conditional evaluation in which a number of powerful features derive from. 

• Conditional Databind: the ability to bind data to form fields based on a condition
• Conditional Visibility: the ability to hide/show as well as enable disable form fields based on a condition
• Conditional Workflow: the ability to move a form to different workflow states based on a certain condition
• Conditional Processing Task: the ability to execute advanced workflow processing task based on a certain condition.

The Form Template Manager module come with two designing modes, Standard and Lite mode.  The Standard mode provides a full set of features for creating a form template.  This of course include the form layout itself and associated workflow meta data (localization, states, access control and workflow).  The Lite mode on the other hand only provide the ability to edit the form layout.  However there are a number of advantages of the Lite mode over the Standard design mode.

Ready made new template - when creatine a new form template in Lite mode, the system automatically creates a simply form with pre-defined workflow meta data giving beginners access to quickly creating the required form and publish for usage.  The pre-defined workflow meta data is a simple 2 states workflow that allow registered users to submit a form from a New to a Submitted state. Quick approval - In Standard mode, publishing a form template requires that the form template go through a series of approval...

Read More »

Enterprise Forms has the ability to access data (read data via data binding and write data via SQL workflow processing task) from a datasource such as a database table or stored procedure.  By default the data source is located within the same database as where the DNN portal resides.  However it is posible to access data sources located outside the DNN database provided the database user (used to access DNN database) also have access to the other databases.  To access data sources from outside of DNN database, fully qualified name must be specified. 

[databasename].[owner].[objectname]

where

databasename: name of the database where the data object resides

owner: name of the owner of the data objects

objectname: name of the database object.  Object can be datatable/view or stored procedure

 

 

...

Read More »

Enterprise Forms 4.0 introduces a new feature where it is now possible to instantly publish a form template without going through the standard 3-step approval proccess. 

Previously when creating a form template before it could be used by the other modules such as Data Collection Manager, Workflow Manager and Report Manager modules, the form template needs to be published by going through a standard approval process.  The process starts with a state called In Development at which form creators could create and modify the form template.  Once the form template design is completed and properly validated, it is moved to the next state of the approval process, Pending Approval.  At Pending Approval, only users with Form Approver access can either move it back to In Development or progress it to the next state Pending Publish.  At Pending Publish, users with access to Form Publisher role can publish the form template and make it Available for use in other Enterprise Forms modules. Feedback...

Read More »

Enterprise Forms demo website has sucessfully been upgraded to DotNetNuke version 4.8.2.