Data accessibility

The execution mode you choose affects the connection between rules and data.

In general:

In sequential mode, preferably use direct data connection with from or in keywords plus ruleset parameters or variables.
In RetePlus and Fastpath modes, favor evaluation in the working memory.

The following table summarizes the effect on data accessibility of changing from one execution mode to another.

Table 1. Changing execution modes
From Mode1 to Mode2	Effect on data accessibility
RetePlus -> Sequential	Sequential mode has limitations compared to RetePlus (see Sequential algorithm). When the rules are connected to the data via working memory, executing traces is different in RetePlus/Fastpath and sequential. RetePlus: `foreach` rule by priority, all the tuples. Sequential: `foreach` tuple, all the rules by static priority. When the rules are connected to the data via `in` and `from` keywords, the data is typically in ruleset parameters and variables. Only the executing trace should differ, as described above.
RetePlus -> Fastpath	Fastpath is a sequential-type algorithm, with static priorities and no support for `update`. However, the change to Fastpath should not affect the executing trace.
Fastpath -> Sequential	Fastpath has fewer rule condition limitations than the sequential mode. The executing trace of Fastpath is the same as RetePlus. When rules are connected to the data via working memory, there is the following difference: Fastpath: `foreach` rule by priority, all the tuples. Sequential: `foreach` tuple, all the rules by static priority.
Fastpath -> RetePlus	No effect.
Sequential -> RetePlus	Only the executing trace differs, as described above for RetePlus to Sequential.
Sequential -> Fastpath	Only the executing trace differs, as described above for RetePlus to Sequential.