Creating macro rules

Macro rules allow non-technical users to create macro conditions without any knowledge of K# macro syntax. The rules are internally implemented as predefined macro expressions but appear as purely text-based clauses describing certain requirements. Users build conditions out of macro rules inside a dedicated Rule designer interface.

The system contains many different types of rules by default and allows you to create custom rules to fulfill any requirements of your users. There are several categories of macro rules:

Rule category


Managed in


Global rules are available when creating conditions in any part of the system.

Note: Certain types of conditions that are closely related to individual applications do not offer global rules.

Macro rules -> Global

Form validation

Allow the system to validate input values of form fields. Users can select the validation rules when defining fields in the field editor (general fields).

Macro rules -> Form validation


Users can select workflow rules when adding conditions to workflow scopes or advanced workflow steps.

Workflows -> Macro rules

On-line marketing

Users can select on-line marketing rules when building conditions for:

Contact management -> Configuration -> Macro rules


Users can select reporting rules when specifying conditions for Report subscriptions.

Open the Reporting application, select any report category in the tree and open the Macro rules tab (in the collapsible panel).


The system provides rules for creating conditions that can limit the following types of discounts and offers:

Store configuration or Multistore configuration -> Discount rules

Defining macro rules

To prepare new macro rules for your users:

Tip: For a step-by-step example of creating a macro rule, see Creating a macro rule.

  1. Navigate to the management interface for the appropriate type of rule (see the table above).

  2. Click New macro rule.

  3. Fill in the following properties:


    Display name

    Sets the name displayed to users in the list of macro rules in the rule designer. Also serves as a basic description of the rule’s purpose.


    Serves as a unique identifier of the rule (for example in the API).


    A text description of the rule’s purpose and parameters. The text appears as a tooltip when users hover over the rule in the rule designer.


    Specifies the context in which the macro rule can be evaluated. Rules marked with Main application or MVC live-site appear in the rule designer only for macro conditions that are resolved by the corresponding application. This can be useful if you wish to hide macro rules for conditions where they would not work correctly (certain macro expressions cannot be resolved by MVC live site applications).

    The following types of conditions are resolved by the MVC live site application (all other conditions in the system are resolved by the main application):

    - Visitor targeting conditions for content A/B tests on MVC sites

    For example, macro rules marked as MVC live-site are only available in the rule designer of the Visitor targeting condition of A/B tests on MVC sites.


    If disabled, users cannot select the rule when building conditions.

    Note: Disabling a rule does not affect the functionality of existing conditions where users have added the given rule.

    Rule data

    User text

    Defines the text displayed in the rule designer when users insert the rule into a condition.

    To add parameters into the text, enter the Field name of a specific parameter enclosed in curly brackets, for example {days}. In the rule designer, the parameter appears as an underlined section in the text. Users can set the parameter’s value by clicking the underlined text.

    See the Adding rule parameters section for more information.


    The actual condition represented by the rule. Define the condition through standard macro code (K#). The field provides autocomplete support.

    Add any parameters offered by the rule to the appropriate position in the code, using the same syntax as for the User text field, for example {days}. When the system resolves the condition, the parameter expression is replaced by the value set for the parameter by users in the rule designer.

    Required data

    Limits for which conditions the macro rule is available. The rule only appears when building conditions that have the specified data items available in the resolving context. You can add multiple required data items separated by semicolons (;).

    Leave this property empty unless you are creating rules specifically for conditions with a customized resolving context.

    Requires context

    Enable this property if the rule’s condition needs to access context data (information about the current user, the currently viewed page, etc.) in order to work correctly. This ensures that the rule only appears for conditions that have the context available when they are resolved.

    For example, the context is accessible when evaluating the conditions of Content personalization variants on a Portal Engine website’s page, but not when the system is building condition-based Contact groups.

  4. Click Save.

Adding rule parameters

Parameters are variables inside macro rules that modify the resulting condition. By adding parameters, you can make flexible rules that are usable for a wide range of scenarios. For example, in a macro rule that requires the current user to be a member of certain roles, the names of the roles would be a parameter.

To create a parameter for a macro rule:

  1. Edit the macro rule.

  2. Open the Parameters tab.

  3. Prepare the parameter as a form field. Every parameter has a certain data type and various other settings. The interface that users see when editing the parameter’s values depends on the selected Form control.

    Refer to Reference - Field editor for details about working with the field editor.

  4. Click Save.

  5. Switch to the rule’s General tab.

  6. Place the parameter into the rule’s User text and Condition code.

    • The syntax for inserting parameters is the parameter’s Field name enclosed in curly brackets, for example  {role} .
    • When the system resolves conditions containing the macro rule, the parameter expressions in the condition code are replaced by the values entered by users. You need to position the parameter expression accordingly.
  7. Click Save.

Users can now set the values of the rule’s parameters when building conditions.

Automatic rule parameters

There are several predefined parameters you can use to add common functionality to macro rules:

  • {_is}, {_has}, {_was}, {_will}, {_perfectum} - provide an easy way to negate a rule’s condition. Each variant offers different wording, so you can use the one that matches the text of your rule. The parameters allow users to choose between a positive and negative option, for example, is or is not. If the negative option is selected, the parameter resolves into the K# negation operator “!” in the condition code. With the positive option, the parameter returns an empty string.
  • {_any} - useful for rules where a list of items needs to be specified through another parameter. The parameter allows users to switch between two options that determine how the rule processes the item list — any (at least one of the items must meet the given condition) or all (the condition must be fulfilled for all items in the list). When resolved, the parameter returns either a false (any) or true (all) value. In the condition code, you can insert the parameter as an additional argument of macro methods that work with object lists, which automatically ensures the required functionality. For example: CurrentUser.IsInRole(“{roles}”, {_any})

When you enter one of the automatic parameters into the User text field of a rule, the system automatically creates a field with the corresponding configuration and default values on the Parameters tab.

Escaping special characters in text parameters

Certain characters inside the values of text parameters could cause the macro condition of rules to become invalid if unhandled. For example, if a rule’s condition is CurrentUser.UserNickName == “{name}”, a quote character inside the value of the name parameter would prematurely close the string, leading to invalid macro syntax and an incorrect parameter value.

To avoid the problem, the system automatically escapes quote and backslash characters inside parameters entered as string literals (directly enclosed inside quotes).

For more complex parameters, you can explicitly enable escaping of string special characters by adding |(escapestring) to the parameter, for example:
“Prefix {parameter|(escapestring)}”

Modifying existing macro rules

When you make changes in the definition of a macro rule or its parameters, the system does NOT update the functionality of existing conditions. This may lead to incorrect behavior of conditions containing the modified rule.

To make sure your conditions are up-to-date, you need to manually perform the following steps after modifying an existing macro rule:

  1. Find the condition fields that contain the rule. You can use the macro report tool to search.
  2. Click Edit next to the field to open the rule designer.
  3. If required, update the parameters for all occurrences of the modified rule.
  4. Click Save & Close.

When you save the condition, the system uses the current definitions of the contained macro rules.

Example – Creating a macro rule

The following is a step-by-step example that demonstrates how to create a custom macro rule. The sample macro rule allows users to create conditions that are fulfilled only during selected months.

  1. Open the Macro rules application.

  2. Click New macro rule under the Global tab.

  3. Fill in the following properties:

    • Display name: Current month is
    • User text: Current month {_is} one of the following months: {months}.
    • Condition: {_is}CurrentDateTime.Month.EqualsAny(“{months}”.Split(“|”))
  4. Click Save.

  5. Switch to the Parameters tab. Kentico automatically creates the months field from the {months} parameter entered into the User text and Condition fields.

  6. Select the months field.

  7. Fill in the following properties:

    • Field caption: select months
    • Form control: Multiple choice
    • Data source: List of options
  8. Copy the following into the Data source text area:

  9. Click Save at the top of the page.

Custom rule parameters

Your custom macro rule is now finished, available globally across all your sites, and ready to be inserted into conditions through the Rule designer dialog.

For example, you can use the rule to limit the visibility of a feedback form field asking for a user’s opinion about a campaign running only from June to August. The following demonstration uses the Send us a message form available on the Dancing Goat Portal Engine sample website:

  1. Open the Forms application.
  2. Edit the Send us a message form.
  3. Switch to the Fields tab.
  4. Select the UserMessage field.
  5. Click Edit next to the Visibility condition setting under the Field advanced settings section. This opens the Edit macro condition dialog.
  6. Select your macro rule from the list and insert it by clicking Add rule ().
  7. Click on select months within the macro rule text. A Set parameter value dialog window opens.
  8. Select the June, July, and August options and click Set parameter.
  9. Click Save & Close.
  10. Click Save.

Now whenever a user visits a page with the Send us a message form outside of the specified three-month interval, the UserMessage form field will be hidden.