Difference between revisions of "Features/Advanced input forms"
Jump to navigation
Jump to search
(Created page with "== Usage == In TS it is possbile to configure very advanced and dynamic input form behavior. The goal is to minimize the effort required to enter data, and at the same time maximize data quality. == Validation rules == == Field dependencies == == Workflow dependencies == == Lookup fields (DAWA,NACE etc.) ==") |
|||
| Line 1: | Line 1: | ||
== Usage == | == Usage == | ||
In TS it is possbile to configure very advanced and dynamic input form behavior. The goal is to minimize the effort required to enter data, and at the same time maximize data quality. | In TS it is possbile to configure very advanced and dynamic input form behavior. The goal is to minimize the effort required to enter data, and at the same time maximize data quality. | ||
In case you need step-by-step questionaires or wizards, we recommend looking at [[Features/Questionaires|Questionaires]] | |||
== Validation rules == | == Validation rules == | ||
== Field dependencies == | == Field dependencies == | ||
Fields can be dependent on values in other fields. Specific values, value ranges or list of values. | |||
== Workflow dependencies == | == Workflow dependencies == | ||
Fields can be dependent on the records location in the workflow governing that entity. Each status is assigned a status level. | |||
Fields can then refer to the workflow model with restrictions | |||
* Status level FROM | |||
* Status level TO | |||
Note that 0 signifies that the status level restriction is disabled, | |||
== Lookup fields (DAWA,NACE etc.) == | == Lookup fields (DAWA,NACE etc.) == | ||
Revision as of 12:04, 9 November 2024
Usage
In TS it is possbile to configure very advanced and dynamic input form behavior. The goal is to minimize the effort required to enter data, and at the same time maximize data quality.
In case you need step-by-step questionaires or wizards, we recommend looking at Questionaires
Validation rules
Field dependencies
Fields can be dependent on values in other fields. Specific values, value ranges or list of values.
Workflow dependencies
Fields can be dependent on the records location in the workflow governing that entity. Each status is assigned a status level.
Fields can then refer to the workflow model with restrictions
- Status level FROM
- Status level TO
Note that 0 signifies that the status level restriction is disabled,