RAP Side Effects — Triggering Field Permissions

Imagine a scenario where the behavior of a field (like readonly, mandatory, etc.) needs to change based on another field’s value. For example, if the OverallStatus is Rejected, the Description field may need to be set to readonly (using feature control).

So usually, we define side effects like this:

field ( features : instance ) Description;
side effects { field OverallStatus affects field Description; }

But the catch is — this does not trigger the feature instance. It only refreshes the field value, not its behavior.

To trigger the feature instance, define it like this:

side effects { field OverallStatus affects permissions ( field Description ); }

Here, it refreshes the field permissions, which triggers the feature instance and updates the behavior (readonly, mandatory, etc.).

📄 View PDF