Go to start of banner

# Why do I need a local variable for certain cases ?

There are rules scenarios where you can't use a frevvo control directly in a rule expression and you are forced to define a local variable, perform the computation using the local variable and assign the value to the control at the conclusion of the computation.

For instance, assume a form that calculates a total from a list of subtotals. The total is a control T and subtotals are represented as a repeat of controls S. In other words, T holds the total of adding all values in S. You could write the rules as:

```T.value = 0;
for (var i = 0; i < S.value.length; i++) {
T.value = T.value + S[i].value;
} ```

The code above makes logical sense but it just won't work. In a nutshell this particularity of the frevvo implementation can be explained this way:

The right hand side of an assignment expression resolves to the value of a frevvo 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:

`T.value = T.value + S[i].value; `

The expression will be evaluated three times (since there are three subtotals) but for every iteration, the T.value operand on the right hand side will always evaluate to 26 which is not the desired behavior and will lead to an incorrect result. Again, this happens because the right hand side of that expression is resolved based on the values initially passed to the rule as parameters.

frevvo explicitly imposes this restriction for the sake of efficiency and there would be a significant impact in performance if the restriction was not in place. Lets rewrite the rule using a local variable:

```var tot = 0;
for (var i = 0; i < S.value.length; i++) {
tot = tot + S[i].value;
}
T.value = tot; ```

This rule will produce the expected result.

# Why does a commented out code line still execute?

A rule with a code line inside a comment block may still execute. For example this rule uses two different Javascript comment styles. The commented out lines in both cases will execute even though you would expect them to be ignored. Do not use comments for this purpose.

```if (form.load)
{
PO.value = 'A-234';
// FN.value = 'Nancy';
/* LN.value = 'Doe'; */
}```

# Why do my rules show unexpected results in a flow using Linked activities?

This question is best answered with an example. Let's say you have a two step flow that contains the following rules; When step 1 of the flow is execute, the form loads and the Sales Planner Status control displays "Not Ready for Review".

```Sales Planner Status:
SalesPlannerStatus.value = "Not Ready for Review";
}```

```CP Status:
if (CP.value == "Yes") {
} else if (CP.value == "No") {
SalesPlannerStatus.value = "Not Ready for Review";
}	```

If the user clicks Yes in the CP field, the Sales Planner Status control displays "Ready for Review"

When you click Continue to advance to the next step of the flow, the value of the Sales Planner Status is set to "Not Ready for Review" even though value of CP is still Yes.

This is as designed. The logic purposely ignores setting value properties that happen in a flow during form state initialization. This is what happens in the second step of this flow using linked activities. Note that changes to other attributes other than value are not ignored during initialization. The designer will see a message in the log and debug console output that says the set of the property value is ignored.

Adding if (_data.getParameter('flow.activity.name') == "Step 1") to the Sales Planner Status rule, gives the expected results:

# 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.

• No labels