Addons Properties

The majority of Addons implementations should be configured correctly to perform as desired.

For example, the SET action allowing to set a value accepts 2 parameters: « source », representing the source value and « target », representing where to put this value.

Tables bellow provide details on available proprerties for all Addons integrated to MRules. Some properties’ ID are underlined: it means that it’s their default property. A value affected to this Addon without anymore directive is automatically assigned to this property (cf. Build the instance).

All Addons

In every cases, properties defined in this table are available for all addons.

Attention: The internal data of table “2” is corrupted!

Evaluation Operators

Attention: The internal data of table “4” is corrupted!

Logical Operators

Attention: The internal data of table “6” is corrupted!

Mathematical Operators

Attention: The internal data of table “20” is corrupted!

Accessors

Attention: The internal data of table “8” is corrupted!

* Advanced proprerty. Its usage might have s consequences on global exécutions performances.

** For a standard compilation, this property is mostly unuseful: target typeis automatically determined.

*** The Rounder class allows to round numbers. A representation as char sequence is possible, under the form
[T|F]{0,1}[0-9]*[RoundingMode Value]{0,1}

With:

  • T|F : delete non-representative zeros (i.e. on the right of the decimal part) : True or False. True if omitted.
  • Decimals number.
  • RoundingMode : CEILING, DOWN, FLOOR, HALF_DOWN, HALF_EVEN, HALF_UP, UNNECESSARY, UP.

Example : “2UP” means 2 décimals, rounded up.

**** “source” and “values” may have different semantics :

  • If one is filled, it will be the source of all values. Convenient for sums, averages, etc …
  • If both are filled, “source” will be the first number(or numbers if it’s an iterable) and values will follow. Convenient for subtractions.

***** “coefficient” and “coefficients” may have different semantics:

  • If only “coefficients” is filled, it must provide Numbers and will be the source of all coefficients.
  • If only “coefficient” is filled, it will be used to read a sub-property on iterated values.
  • If both are filled, “coefficients” will iterated and “coefficient” will be used to read a sub-property on iterated coefficients.

Actions

Attention: The internal data of table “10” is corrupted!

* All flow control commands are :

  • DONTSTOP: If targeted block has the “stopAtFirstValidatedCondition” to true, forces an exception to this directive. “appliesTo” property might precise the block targeted by the exception. If not, first parent block is targeted.
  • STOP: Stops execution. “appliesTo” property might precise a block to stop. If not, first parent block is stopped.
  • RESTART: Restarts execution. “appliesTo” property might precise a block to restart. If not, first parent block is restarted.
  • CONTINUE: Specific command of the “FOREACH” addon, tells to continue directly to the next element.
  • RAISEERROR: Throws an error, error code “RAISEERROR”, containing the optional “message” property. “appliesTo” property is ignored.

Les Exécutables

Attention: The internal data of table “12” is corrupted!

* Advanced proprerty. Its usage might have s consequences on global exécutions performances.

Les Conditions

Attention: The internal data of table “14” is corrupted!

* Advanced proprerty. Its usage might have s consequences on global exécutions performances.

Les Fabriques de Contexte

Attention: The internal data of table “16” is corrupted!

Le Rule Set

Attention: The internal data of table “18” is corrupted!