Business Rules have several quirky behaviors that will be addressed in a future release. Please read and understand these points before writing your first business rule.
...
The code above makes logical sense but it just won't work. In a nutshell this particularity of the implementation can be resumed explained this way:
The right hand side of an assignment expression resolves to the value of a a control passed to a rule when it is invoked. The left hand side uses a reference to the control'.
Lets work with a concrete example to understand the concept. Assume that there are two subtotals in the form, 12 and 14 and the total is correctly set to 26. Now, you add 50 as a third subtotal and the rule fires as a consequence. The values of the controls involved in the rule are passed as parameters to the rule: the subtotals 12,14 and 50 and the current total (value of T), 26. The core of the matter is in the expression:
...
| Code Block |
|---|
if (form.load)
{
PO.value = 'A-234';
// FN.value = 'Nancy';
/* LN.value = 'Doe'; */
} |
What causes an "Invalid signature detected. Data may have been tampered with" error?
This error message usually displays in multi-step workflows when there is a rule on a subsequent step that executes at form load and updates values inside a signed section in a previous step. Check your rules if you encounter this error.