Macro Step Condition overrides

Macro steps now contain the Override Condition field to support defining alternate conditions of execution, while adding a macro step condition function IsTag(tagname). This feature supports extensibility of the standard configuration without having to copy or create custom macros to alter the execution of certain steps.

Typical use cases include:

• Avoid executing a step where the standard content does; for example, when not using functionality or not specifying certain data. For example: 1 == 2.
• Execute a step in different, or additional, conditions; for example, a user-defined application variable, controlled by an override value; or a standard application variable + some extra condition. For example: "Test" == "1".
• Execute a macro step on the inclusion of a Tag for the current context; for example, a cycle period or planning engine. For example: IsTag('DPLS-AdvForecast').

Override Conditions are preserved on loading new versions of the standard templates. These are included as part of the Overrides template, therefore, can be extracted for migration to another tenant or instance.

IsTag() can also be used in the default Condition of a macro step, as part of the standard content. This is useful when a function or process may include, or exclude, some configuration using a tag but also impacts the standard process or interfaces. This can be done as a single setting, instead of separate tags and application variables which must be kept in alignment.