...
Rules are the best way to add dynamics to your forms, make validation rules conditional or customise form UI behaviour
Available rules
...
...
...
...
| Applies CSS styles on a given field, based on the condition set | |
|
...
...
...
...
| You can apply specific filters on "select"-type fields. This is especially powerful, when your fields are backed by smart fields, web-service or database fields. Your filter is applied ON THE DATASET this field relies on. Which means, the filter is applied on the source dataset Few examples: |
|
...
...
| Conditionally hides the field and the "wrapping" container (if given) | |
|
...
| Allows you to hide by CSS selector | |
|
...
...
...
...
| Helps you to have a lookup against the query you create from your database | |
|
...
...
...
...
| Allows you to make a request to a webservice and set the received values back to the form's fields | |
|
...
...
...
...
...
| Allows you to request issue details from your Jira (by issue key) and set the received values back to the | |
|
...
...
...
...
...
| Same as with Jira issue data, but allows you to query Insight data storage | |
|
...
...
...
| This rule allows you to lookup the data from another ConfiForms form and set received data back to the form's fields | |
|
...
...
| ConfiForms can execute a custom JavaScript function via ConfiForms Field Definition Rules, and your function can expect the following variables to be present - formName - is the "form" with HTML field elements. This allows you to access fields very easily via AJS.$(formName).find('#i_FIELD_NAME')
- formId - is the "div" element in HTML holding the whole form and fields. This allows you to access fields very easily via AJS.$('#' + formId).find('#i_FIELD_NAME')
which means your function can have a signature like: | Code Block |
|---|
function myfunction(formName, formId) {
} |
See demo: Using ConfiForms Field Definition rules with JavaScript action to get and set field values | |
|
...
| Same as set value, but you can set expression (Supported math operators, formulas and functions), which will be calculated for you | | Sets field as readonly, setting reverse condition will do the opposite. Please note that you will need 2 rules to set/unset the readonly status - you cannot have one (as with hide/show, for example) Please also note that not all the fields can be set as readonly - dropdowns are ALREADY readonly, and setting the as readonly makes no sense and no impact. Also, not all the fields are supported (work in progress). | |
|
...
...
| Rule to help you to changes form's title | | Sets label text for the field | |
|
...
| Set's value to the fields. Please be aware, that internal value for the field is expected. See ConfiForms Field Types | |
|
...
...
...
| Same as above, but has additional check applied to ensure the value is set ONLY when the field has not value set | |
|
...
...
...
| Changes label on submit form button | |
|
...
| Conditionally shows the field and the "wrapping" container (if given) | | The opposite what "Hide container" does, and allows you to show elements matching the CSS selector you put | |
|
...
...
...
...
...
...
| Useful action type to check if the record matching configured condition / filter exists in the other form | |
|
...
| On form submit, the action checks if the record is unique within a dataset. Uniqueness criteria is calculated based on the fields given | |
|
...
...
| This action is executed on "record delete", and could prevent the record being deleted based on the condition you set | |
|
...
| Validates record(conditionally) | |
|
...
...
| Validates current record against the rows in the dataset, For example, when you want to ensure the max number of records stored in the dataset |
|