Hidden form control

A form control that the form user cannot see.

Configure the Hidden form control

To configure the Hidden Hidden icon control, do the procedure in this topic.

Video: Common Configuration Settings in eForm Controls

Examples

How to Start

  1. Open eForm Builder.

    For information about how to open this screen, refer to eForm Builder screen.


    Eform Builder screen
  2. On the eForm Builder screen, in the Toolbox, open the Commmon Controls tab.

    Common Controls tab
  3. On the Common Controls tab, drag a Hidden Hidden icon form control onto your eForm.

    Hidden Form Control

Procedure

  1. Complete the settings on the configuration screens.

    You can use the App Data screen to specify a variable.

General

Specifies the basic configuration for the Hidden form control.

Figure: General tab

General tab

Fields

Field Name Definition

Internal Name

Function:
Specifies a unique, technical name for your control.
Accepted Values:
One line of text with no spaces.
Default Value:
Different for different controls.
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Default Value

Function:
Specifies the default value in the field.
Accepted Values:
More than one line of text that can have letters, numbers, spaces, and special characters.
Default Value:
None
Example:
Refer to:

Advanced

Specifies advanced settings for your form control.

Figure: Advanced tab

Advanced tab

Fields

Field Name Definition

Field ID

Function:
Shows an ID of the control.
Accepted Values:
Read only.
Default Value:
Different for different controls.
Example:
Refer to:

Data Security Settings

Function:
Specifies whether to store information from the field in the process schema, so the app can use it again, or to simply pass on the information after the form is submitted without storing the information. This option helps to protect sensitive user information.
Accepted Values:
  • Persist - Stores the data from the field in the process schema, so the app can use it again.
  • Do Not Persist - Does not store the data from the field in the process schema. This option provides greater security for sensitive user information.
Default Value:
Persist
Example:
Refer to: