NOT condition

As part of the Rules Engine introduced as part of ActiveControl 8.0, it is possible to setup complex step logic which drive the behaviour of Approvals and/or Skipping within ActiveControl.

“AND” and “OR” step types were already possible in /BTI/TE_RE_STEP – but on the back of Customer feedback, this has now been extended as part of ActiveControl 8.40 to also include “NOT”.

NOT allows the inversion of the original True or False output of the underlying Step Condition, and is a good way of avoiding multiple OR step conditions. As a simple example, if a Transport Form should stop for an additional approval if it is [Priority] = “Emergency”, but not skip if it is “Low”, “Normal” or “High” priority. Prior to ActiveControl 8.40, it would have been necessary to setup three skipping conditions. Now the same requirement can be achieved with only one NOT-based skipping condition, resulting in less configuration.

Configuration Steps

An example of NOT step type configuration can be found in this online Knowledge Article.