Using Rules console

Access the Rules console from the left pane by Data model manager > Rules engine. The Rules console page displays total number of rules and number of selected rules.

Prerequisites

Following are the prerequisites for using the Rules feature:
  • Run the migration script and verify you can see the tctg_rle_rule table created in the database.
  • Import the mdmce-env.ZIP file at the $TOP/mdmui/env-export/mdmenv folder. Verify that you can see the RulesLookupTable in the Lookup Table console.

Tasks

You can perform following tasks in the Rules console page.
Clone Select a rule, and click to open the cloned rule in the Rules details page.
Delete Select a rule, and click . The Delete confirmation pop-up window opens. To delete the rule, click Yes.
Composite Displays whether the rule is basic or composite.
  • A Basic rule is a rule created on a specific extension (stand-alone rule).
  • A Composite rule is a rule that consists of 2 or more Basic rules.
Status Click to enable a rule directly from the Rules console page.
Settings Click to open the Settings pop-up window.
  • To remove a column, clear the checkbox for the column.
  • To select all the columns, click Select All.
Clear all filters Click to clear all the existing filters from the columns.
Note: This icon is disabled until you apply a filter.
Filter Click to filter a column by a value. In the Search field, enter the value, and click Apply.

You can also sort the values in a column by ascending or descending order. The default value is ascending order. You can also click a column header to sort the values.

To see details of any rule, click <rule name> link.

Known Limitations

Following is the list of known limitations:
Rules feature
If you apply a filter on the Composite column, then you are not able to apply filter to any other column. This is a known limitation and will be fixed with a future release.
  • The Rules engine does not support the following:
    • Password, binary, image, thumbnail image, grouping, localized grouping, and external content reference attributes
    • Post-save rule extension (catalog)
    • Nested if/else statements
  • Linked type of attribute is only supported for catalog.
  • If you manually remove a script from the Admin UI from an extension point that also has a rule that is attached from the Persona-based UI, the rule script does not run. As a workaround, save the same rule again from the Persona-based UI to generate a dummy script.
  • Conditions that were added during creating basic rule are only considered in a composite rule.
  • If a basic rule in a composite rule is edited, the update is not considered.
  • Rule with length operator and the predicate type attribute is not supported.
  • During rule creation if you use Is mapped to operator in the IF part of the rule to map Item to a category, the rule fails.
  • Currently, rule support is for an Item only.
  • String enumeration attribute type with string enumeration rule script has string type editor instead of the string enumeration drop-down list.
  • The category path of mapping expression (condition or action) in a rule should not contain Forward slash / character, which is a delimiter for the category path.
In and Not in operators
  • Currently, supports only the Value predicate.
  • Multi-value-selector:
    • To add data, you need to press Enter for multi-value selector.
    • Only deals with list of strings.
    • No validations are present in the multi-value selector.
  • Rich text editor: A rule is not applied if during rule creation the HTML tags that need to be compared are not added.
  • Specialized editors - Following attributes have specialized editors:

    Date, Date-time, Timezone, Relationship, Lookup table, and Linked.

    Lookup table and Relationship attributes
    Following is the display format for Relationship and Lookup table attribute:
    Lookup table attribute
    LKPNAME_PK_DISPATTRIB
    LKPNAME_PK
    Relationship Type attribute
    CTG_PK_DA
    CTG_PK
    The CTG_name or the LKPNAME is mandatory in the display format while you are creating rules or else the primary key or the display attribute cannot be fetched and the rule creation fails.
    Date attribute
    The Input and Output format should be set same as specified in the Settings page.
    Multi-occurrence attribute
    You cannot add Sequence in the Then part of the rule.
    Catalog, spec, and workflow do not support type Then part of the rule.