Custom code token is the ability to execute a segment of custom code within a token.  This functionality provide form developers with the full flexibility to execute and process form data to any specific needs.  This functionality requires that the form developer have knowledge of the .NET C# language.

The format of a custom code token is as follows

[[CODE:custom code]]

where custom code is the segment of C# code.

the custom code must return a string in order for the token to properly evaluated.  Line break can be included in the custom code.

Note: Opening and closing curly brackets { and } must be escaped with double curly brackets such as {{ and }}

Examples:

1.  The simplest Hello World custom code is

[[CODE:

       return "Hello World"

]] 

when evaluated the above custom code token returns the string "Hello World"

 

2.  Custom code with embedded standard tokens

[[CODE:

       if ([FORM:field1] > [FORM:field2])

...

Read More »

Advanced dynamic tokens is a new feature in Enterprise Forms 3.7.  This feature extends dynamic tokens capability by providing the additional ability to perform complex expression evaluation using built-in function or custom .NET code.

A typical advanced token is contained within double opening ([[) and closing (]]) square brackets.  Similar to the standard tokens, advanced tokens also use name space to distinguish between token types.

Advanced tokens currently support two type of namespaces, FUNCTION and CODE.

The FUNCTION Namespace

The FUNCTION namespace is used for describing the built-in functions available.

An example function token has the following format

[[FUNCTION:functionname(param1, param2, paramN)]]

functionname: name of the function

paramX: list of parameters required for the function

when evaluation is performed and if successful the full token will be replaced by the returned value of the function.

...

Read More »

Steps to add a tooltip to a form field

• Go to the ClientActoins tab of the Edit Field Element popup window
• Provide text in the following format to the OnMouseOverAction field
  • return escape('[TOOLTIP]');
  • where [TOOLTIP] is the tooltip text required to display.
  • an example to display the Hello Worlf message tooltip
  • return escape('Hello World');

From version 03.06.05 we have added support for dynamic tokens to the Workflow From email field.

Enabling this support provides further flexibilty in using the a form value as the From email address in workflow email notification.  Once of the advatanges of this feature is that it could be used in a Feedback / Contact Us type forms to allow the form submitter to use his/her email address for direct email correspondence between the users.  An example of this is the Contact Us page where we are using to allow customers to contact us directly without having to use the Enterprise Forms workflow engine.

DotNetNuke(DNN) has a built-in storage area where list and list entries could be created from Host  Lists menu.  Lists are used to store lookup information such as Countries and its associated Regions.  DotNetNuke provides a facility to create your own list but it does not provide a way to access and use it within its core functionalities or modules.

This article discusses the technique of using a DNN List and bind to a form field (Select List form element) in Enterprise Forms. 

To achieve this we will be using the Databind feature in Enterprise Forms to call a Stored Procedure (SP) that retrieve the required list entries based on a set of parameters. The stored procedure concerned is

GetListEntries @ListName, @ParentKey

Where

@ListName is the name of the list – in our case it is called Country @ParentKey is the key associated to the parent of the list – in our case Country is the top parent list thus we use ‘’ (empty string) as the...

Read More »