Query synchronization between Rule Designer and Decision Center

Queries work both in Rule Designer and Decision Center. When you synchronize a rule project between Rule Designer and Decision Center, queries in both modules are also synchronized, except for certain module-specific query constructs.

You can create and run queries in either Rule Designer or Decision Center. However, you do not have to write the same query twice: when you synchronize rule projects between Rule Designer and Decision Center, queries in both modules are also synchronized.

The query BOM and vocabulary files are shared between Rule Designer and Decision Center. However, certain query constructs are not: if you write queries using module-specific constructs, these queries are synchronized but you cannot run them in the other module. If this is the case, you receive an error message. To make sure that a query written in one module can be run in the other, avoid using module specific constructs.

Rule Designer query constructs

The following condition predicates are specific to Rule Designer:

{this} is editable
{this} is not editable
{rule artifact} is using BOM class
{rule artifact} is not using BOM class
{rule artifact} is using BOM member
{rule artifact} is not using BOM member
the parent package of {a rule package}
{rule package} is in package {rule package}
{variable} is in package
the rule query class

The following action predicate is specific to Rule Designer:

set the editable status of {this} to {0}

Decision Center query constructs

The following condition predicates are specific to Decision Center:

the creator of {this}
the creation date of {this}
the last modifier name of {this}
the last modification date of {this}
the view class
the group of

The following action predicate is specific to Decision Center:

set the group of {project element} to {group}