Configuration Tips - Logics

Checking data dependencies

Avoid any complex logic/fetches from the database. Ideally, you should never need more that a single api.find call to check if some data that grants a user the access to some object or not.

Add New Calculation Logic

Placing input parameters in logic

Place input parameters high up in the logic, with no or as little as possible dependencies / conditional logic on them.

How Input Generation Mode Works

Format Type ‘Money’

Do not count on the Format Type ‘Money’ to do any currency conversions. It is only a format.

Add and Define Element

Inherited elements should not be changed

When using a parent logic, do not delete or change the order of inherited elements (this is not enforced by the application).

Parent Logic

Order of elements in logic

The order of elements (with the function definition) in the logic is important because the function will be visible only to later elements. E.g. a function defined in the 2nd element will be visible to 3rd, 4th, … element, but it will not be visible to the 1st element.

Libraries

Display Mode ‘Never’

The setting Never affects also warning messages from api.addWarning. These messages are then displayed with the next visible element (if there is any).

Add and Define Element

Syntax check mode specifics

Beware that in the syntax check mode, some things do not work the same way as in regular execution, e.g. result values of elements return mock values, and some API calls (e.g. api.stream()) return null, instead of real values.

Logic Inputs

Change of default logic

When you set or change the default calculation logic in Configuration, it has no impact on existing Price Lists or Live Price Grids.

Defaults for Price Lists and LPGs

Calculation Context for Rebate Agreements logics

If you do not specify particular groups (contexts) in Calculation Context of a Rebate Agreement, the logic of this element will be executed in ALL contexts.

Rebate Agreements Calculation Logic