docs: improve formula examples, fix roadmap structure, add trailing newline
- dcc-validations: add MATCH() example showing why spaces matter around column names; document that new rows are 'A' from creation - roadmap: move delivered Frontend Formulae and Regex Rules to Delivered Features section; reword 'necessary' heading - deploy-viya: add trailing newline
This commit is contained in:
@@ -60,7 +60,7 @@ Formulas use column names, not cell references, so there is no need to know the
|
|||||||
Each row calculates its own result - the PRICE in row 1 is multiplied by the VOLUME in row 1, the PRICE in row 2 by the VOLUME in row 2, and so on.
|
Each row calculates its own result - the PRICE in row 1 is multiplied by the VOLUME in row 1, the PRICE in row 2 by the VOLUME in row 2, and so on.
|
||||||
|
|
||||||
!!! note
|
!!! note
|
||||||
Each column name in the formula must be surrounded by spaces (eg ` PRICE ` not `PRICE`) so it is recognised as a column reference rather than part of a function name. Text inside quotes is left as-is.
|
Each column name in the formula must be surrounded by spaces (eg ` PRICE ` not `PRICE`) so it is recognised as a column reference rather than part of a function name. For example, `=MATCH( PRICE )` resolves the column reference, but `=MATCH(PRICE)` does not - PRICE is left unrecognised and the formula will error rather than using the column's value. Text inside quotes is left as-is.
|
||||||
|
|
||||||
### HARDFORMULA vs SOFTFORMULA
|
### HARDFORMULA vs SOFTFORMULA
|
||||||
|
|
||||||
@@ -77,7 +77,7 @@ Each row calculates its own result - the PRICE in row 1 is multiplied by the VOL
|
|||||||
|
|
||||||
Formulas can reference three special values that are resolved at runtime:
|
Formulas can reference three special values that are resolved at runtime:
|
||||||
|
|
||||||
* `DC.ROW_STATUS` - the current state of the row: `M` (Modified), `A` (Added), `D` (Deleted), or `U` (Unchanged).
|
* `DC.ROW_STATUS` - the current state of the row: `M` (Modified), `A` (Added), `D` (Deleted), or `U` (Unchanged). A newly-added row is `A` from the moment it is created - there is no transient state before that.
|
||||||
* `DC.USER_NAME` - the logged-in user id.
|
* `DC.USER_NAME` - the logged-in user id.
|
||||||
* `DC.ORIG_VALUE` - the original cell value before the current edit.
|
* `DC.ORIG_VALUE` - the original cell value before the current edit.
|
||||||
|
|
||||||
|
|||||||
+9
-6
@@ -26,12 +26,7 @@ The following features are currently requested:
|
|||||||
|
|
||||||
### Additional Validations
|
### Additional Validations
|
||||||
|
|
||||||
The following additional features are necessary:
|
The following additional features are under consideration:
|
||||||
|
|
||||||
* ~~Frontend Formulae~~ - **Delivered** in v7.13.0. See [Formula Rules](/dcc-validations/#formula-rules).
|
|
||||||
* Regex Rules - **Delivered**. See [Regex Rules](/dcc-validations/#regex-rules).
|
|
||||||
|
|
||||||
The above rules will apply only at frontend, and will be configurable in the MPE_VALIDATIONS table. The values will appear as part of the [editors/getdata](https://code.datacontroller.io/getdata_8sas_source.html) service response in the `dqrules` object.
|
|
||||||
|
|
||||||
**Frontend Formulae**
|
**Frontend Formulae**
|
||||||
|
|
||||||
@@ -237,3 +232,11 @@ It is now possible to restore any change by heading to the particular staged dat
|
|||||||
This will submit a NEW change (which must first be approved) that will revert the table to state it was in just prior to the selected upload.
|
This will submit a NEW change (which must first be approved) that will revert the table to state it was in just prior to the selected upload.
|
||||||
|
|
||||||
Note that Data Controller can only track (and revert) changes that are made using the Data Controller tool itself! It does not / cannot track changes made externally to a table, by other tools.
|
Note that Data Controller can only track (and revert) changes that are made using the Data Controller tool itself! It does not / cannot track changes made externally to a table, by other tools.
|
||||||
|
|
||||||
|
### Frontend Formulae
|
||||||
|
|
||||||
|
Delivered in v7.13.0. Formula columns (HARDFORMULA / SOFTFORMULA) are computed live in the editor using HyperFormula, with variable-name references resolved to row-relative cell references. See [Formula Rules](/dcc-validations/#formula-rules).
|
||||||
|
|
||||||
|
### Regex Rules
|
||||||
|
|
||||||
|
Delivered. HARDREGEX (blocking) and SOFTREGEX (warning) rules validate cell values against a Perl-style regular expression. See [Regex Rules](/dcc-validations/#regex-rules).
|
||||||
Reference in New Issue
Block a user