By EThuongmai Support on 7/18/2007 3:29 AM
Enterprise Forms v3.6 will no longer support DNN 3.x earlier than DNN 03.03.07 due to a new feature that we will be introducing in Enterprise Forms v3.6.
|
By EThuongmai Support on 7/16/2007 5:40 AM
If you are using Enterprise Forms 3.3+ with DotNetNuke 4.5.3 with Compression turned on, ensure that the follollwing value is added to the Excluded Paths field located in Host Menu --> Adveanced Settings --> Compression Settings anthem_callback
|
By EThuongmai Support on 7/15/2007 6:20 PM
Enterprise Forms version 3.6 now support the following additional tokens
Token Name
Description
[USER:UID]
UserID of the current logged on user
[USER:USERNAME]
Username of the current logged on user
[USER:FULLNAME]
Fullname of the current logged on user
[USER:DISPLAYNAMe]
Display name of the current logged on user
[USER:FIRSTNAME]
First name of the current logged on user
[USER:LASTNAME]
Last name of the current logged on user
[USER:EMAIL]
Email of the current logged on user
[USER:CREATEDDATE]
Date of when current logged on user was created
[USER:LASTLOGINDATE]... Read More » |
By EThuongmai Support on 6/21/2007 10:19 PM
Enterprise Forms 3.5 release contain a number of significant enhancements all of which come from requests from valued customers.
Conditional Workflow
Workflow Processing
Conditional Workflow
Conditional workflow is the ability to selectively decide the workflow path of a form instance based on value of form fields. Conditional workflow is a logical enhancements following the successes of conditional page/field visibility and conditional binding make available in the 3.3 release.
An example is the best way to describe the applications of conditional workflow feature.
You may have a job application form that is required to be rejected or accepted depending on the age of the applicant. Previously the application form is required to be reviewed by a staff member, whereby he/she needs to manually check for the age entered then reject or appove the job application based on the value entered via the available Reject or Approve buttons.
In version 3.5 we have taken the workflow engine one step further by having the workflow engine automatically reject or approve the job application form based on the age entered. The need for an additional review process is no longer required thus making your business process streamlined and automated.
... Read More » |
By EThuongmai Support on 4/21/2007 9:00 PM
As users are becoming more familiar with Enterprise Forms more and more complex forms are being created. From Enterprise Forms v3.0 we have included a number of Javascipt API to allow easy access of form objects for advanced field validation and calculations etc. Thus it is vitial that EF provide a set of API functions to allow advanced users to obtain the object reference to the field elements for data manipulation and processing.
The following list some of the most commonly used API functions available for used within the form.
__EFGetElementByEFFieldName(fieldname) : this function takes in a parameter which is the name of the field and returns an object reference to the field. If the field name does not exists a null value is returned. Example var obj = __EFGetElementByEFFieldName('myTextbox');
__EFGetElementByID(id) : Similar to the above function, this function takes in a paramter which is the 34 characters IS of the form element and returns the object... Read More » |