By EThuongmai Support on 1/29/2006 6:50 PM
With the introduction of a rich text editor for editing HTML fields,
Enterprise Forms users now can freely create and edit rich content
without requiring any knowledge of HTML. This article describes how to
use Enterprise Forms to create and publish content via a designated
approval process.
Enterprise Forms form template designer
has an mini approval process whereby designated form creators can
create content, whether it is a web form or just an article, the form
template goes through a mini approval process before it can be publish
for public viewing. The workflow for publishing form template is a 6
step approval process. Once a form template is
created by a designated form creator, it is assigned a "Development"
state. This state is solely for designing the form template layout
and content. In addition other meta data information about the form
template such as security access controls and roles are defined.Â
During the "Development" state, the form template... Read More » |
By EThuongmai Support on 1/13/2006 4:41 PM
Enterprise Forms 2.2 (Final Beta) has been uploaded to the demo website and currently is being tested vigorously by a number of selected users. New features of Enterprise Forms 2.2 include: - Enhanced user interface to make it more user friendly
- Provided the ability to edit HTML fields using DotNetNuke’s native HTML editor
- Separated module suites into separate module component so that a single module instance can be easily added to a page
- Better localization support for lookup values
- Added paging for all history related data
Note that existing Enterprise Forms 2.x customers will be able to obtain the upgrade for free and will be notified when the final release version is available
|
By EThuongmai Support on 12/4/2005 4:03 PM
We have been inundated with emails with questions regarding our licencing policy for Enterprise Forms.
Here is a short version of the licencing policy
A single purchase of Enterprise Forms entitles you to use Enterprise Forms in a single production parent portal only. However you are entitled to use Enterpise Forms in unliminted number of child portals within a licenced parent portal.
In other words, if you have a licence to use Enterprise Forms for
http://www.mydomain.com
then you are also entitled to use the product for your child portals without requiring further licence.
http://www.mydomain.com/child1
http://www.mydomain.com/child2
 etc..
However, if you also intend to use Enterprise Forms for another domain/parent portal, say http://www.myotherdomain.com, then you will need to purchase... Read More » |
By EThuongmai Support on 11/8/2005 5:34 AM
DotNetNuke (DNN) 3.2 and 4.0 have recently been released to support the new .NET Framework 2.0. Enterprise Forms 2.0 has only been tested with DNN 3.1.0 and DNN 3.1.1 thus it is not advisable to install Enterprise Forms to these two recently released versions particularly DNN 4.0 Once tests have been completed we will officially announce whether Enterprise Forms is fully compatible with DotNetNuke 3.2 and DotNetNuke 4.0
|
By EThuongmai Support on 11/2/2005 11:39 PM
With the recent introduction of the Report Manager in Enterprise Forms 2, portal administrators and users a like are able to create reports on form templates.Â
Â
When a form template has been published and is ready to be used to collected data, report templates can also be created for the form template. One of the features of the Report Manager module is its ability to create a dynamic SQL view of fields that can be individually selected from the list of available fields in the form. This means that an advanced user can use this SQL view to integrate with an external system for data integration or more advanced reporting.
Â
Each instance of the Report Manager module can display a report template. When configuring, the user can select and assign which fields are available as search criteria. In addition reports can be customized to display data immediately or only when the user trigger a search action. Report data can then be used to export to an Excel®... Read More » |