Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Calculation Field allows you to perform a series of arithmetic computations to a set or a series of fields.
The Calculation Field is only available on Professional and Enterprise Edition.
The easiest way to see how the Advanced Grid works is to use the existing built-in App Expenses Claims and look at an existing form in the app. Here are the steps:
In Figure 5, we are summing at a specific column from a Form Grid.
Form Grid ID: spECD
Column in Form Grid: amount
Field ID to be filled in Figure 6: spECD.amount
Name | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Label | Element Label to be displayed to end user. | ||||||||
ID | Element ID (By declaring as "total", a corresponding database table column "c_total" will be created) Please see Form Element for more information about defining the ID and list of reserved IDs. | ||||||||
Variables |
| ||||||||
Equation | Arithmetic operation using the variables declared above. Example
Important Notes
|
Name | Description |
---|---|
Validator | Attach a Form Validator plugin to validate the input value. When will validation takes place? Validation will takes place whenever form is submitted except when it is submitted as "Save as Draft". |
Name | Description |
---|---|
Formatting Style |
|
Number of Decimal | Number of Decimal |
Prefix | The prefix of the calculated value |
Postfix | Postfix of the calculated value |
Use Thousand Separator? | Thousand Separator toggle. |
Store as Numeric Value? | Toggle to store as a numeric value instead of a string |
Name | Description |
---|---|
Hidden? | Shows this element to the end user. |
Display as Label? | Displays the value of the element as plain text. |
Name | Description |
---|---|
Workflow Variable | If the form is part of a workflow process, upon saving the form (by clicking on the "Save as Draft" or "Save" button). The value in this input field will be saved into the corresponding workflow variable named here. Using 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. context attribute status does not exist in process context - adding new attributes to the process context is not allowed |