Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed images layout

...

The easiest way to see how the CheckBoxes works are to use the existing built-in App Expenses Claims. Here are the steps:

...

  1. Start Joget Server and open the App Center.

  2. Log in as admin and click on the pencil icon on the Expenses Claim to open the Design App. (see Figure 1)

    Image Added
    Figure 1

  3. Click on Expense Claim New and you will be directed to the Form Builder.

  4. Drag and drop a CheckBox element on to the canvas.

  5. Hover the mouse over the CheckBox element on the canvas and click on Edit to open up the Edit CheckBox properties.

  6. Fill up the 

...

  1. Edit CheckBox properties as follows and click on OK (see Figure 2):
    1. ID: type
    2. Label: Type
    3. Options Hardcoded: 

      ValueLabel
      LocalLocal
      InternationalInternational

    Image Added
    Figure 2

  2. Click on Preview to see that it works.

...

Image Removed

Figure 1

Image Removed

Figure 2

CheckBox Properties

Edit CheckBox

NameDescriptionScreen (Click to view)
ID

Element ID (By declaring as "type", a corresponding database table column "c_type" will be created)

Please see Form Element for more information about defining the ID and list of reserved IDs.

Image Removed

LabelElement Label to be displayed to end-user.
Options (Hardcoded)

Select Box options

Info

Options defined here will not be put into use if Options Binder is defined below.

Or Choose Options BinderOptions to be populated dynamically using Options Binder plugin.

Image Added

Advanced Options

Data

Image Removed
NameDescriptionScreens (Click to view)
Default Value

Default Value when there's no existing value found/selected.

A Hash Variable is accepted here. For example, you may key the following

Code Block
#currentUser.firstName# #currentUser.lastName#

to pre-populate the field with currently logged in user's name.

You may define multiple default options by separating them using semicolons.

Code Block
titleSample
option1;option2;option3
Validator

Attach a Validator plugin to validate the input value.

Info
titleWhen will validation takes place?

Validation will take place whenever a form is submitted except when it is submitted as "Save as Draft".

Image Added

Dependency

Screens (Click to view)
NameDescription
Field ID to control available options based on Grouping

Dynamically change the available options based on the "grouping" attribute defined in the options by matching the current value of the element ID defined.

Image Removed

Image Added

UI

Image Removed

NameDescriptionScreens (Click to view)
Readonly

Determines if the element is editable.

Display field as Label when readonly?

Displays the value of the element as plain text when element is set to "Readonly".

Image Added

Workflow

Screens (Click to view)Image Removed
NameDescription
Workflow Variable

If the form is part of a workflow process, upon saving of the form (by clicking on "Save as Draft" or "Complete" button). The value in this input field will be saved into the corresponding workflow variable named here.

Info
titleUsing a non-existent Workflow Variable name

You will get the following warning with the name printed out (e.g. status) in the server log if you attempt to map to a non-existent Workflow Variable.

Code Block
context attribute status does not exist in process context - adding new attributes to the process context is not allowed


Image Added