Difference between revisions of "Features/Advanced input forms"

From TempusServa wiki
Jump to navigation Jump to search
Line 4: Line 4:
In case you need step-by-step questionaires or wizards, we recommend looking at [[Features/Questionaires|Questionaires]]
In case you need step-by-step questionaires or wizards, we recommend looking at [[Features/Questionaires|Questionaires]]


== Validation rules ==  
== Validation rules ==
Validation of field values can follow one of the following
* The value is required
* Can be validated by a Regex expression
* Have a value within a minimum and/or maximum
 
Value ranges will differ according to data type
* Numbers: The value
* Text: Length of text
* Date: Allowed years
* Filles: Number of files
 
Note that dependencies are resolved before validation, so in case a field is not relevant the validation rule will be ignored.
 
=== Instrcutions ===
# Click on field
#* Check of Validation
#* Remove check in Allow empty values


== Field dependencies ==  
== Field dependencies ==  

Revision as of 14:58, 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

Validation of field values can follow one of the following

  • The value is required
  • Can be validated by a Regex expression
  • Have a value within a minimum and/or maximum

Value ranges will differ according to data type

  • Numbers: The value
  • Text: Length of text
  • Date: Allowed years
  • Filles: Number of files

Note that dependencies are resolved before validation, so in case a field is not relevant the validation rule will be ignored.

Instrcutions

  1. Click on field
    • Check of Validation
    • Remove check in Allow empty values

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

If the status restrictions are not satisfied the field will be removed and validation requirements will be ignored.

Note that 0 signifies that the status level restriction is disabled.

Instructions

Learn to setup Features/Status level dependencies

Lookup fields (DAWA,NACE etc.)

Duplicate prevention

To ensure that the same data are not duplicated by mistake, it is possible to ensure that new records are unique based on values in one or more fields.

Learn to set up Features/Duplicate_prevention

Special content