Query Synchronization Between Rule Studio and Rule Team Server

ILOG JRules User Guide > Querying and Reporting > Concepts > Queries > Query Synchronization Between Rule Studio and Rule Team Server

Query Synchronization Between Rule Studio and Rule Team Server

PREVIOUS NEXT

You can create and run queries in either Rule Studio or Rule Team Server. Rather than having to write the same query twice, when you synchronize rule projects between Rule Studio and Rule Team Server, queries in both modules are also synchronized.

The query BOM and vocabulary files are shared between Rule Studio and Rule Team Server. However, certain query constructs are not. This means that, if you write queries using module-specific constructs, the queries will be synchronized but they may not be runnable. If this is the case, you will receive an error message.

To make sure that a query written in one module can be run in the other, you should avoid using constructs that are specific to one or the other of them.

Rule Studio Query Constructs

The following condition predicates are specific to Rule Studio:

{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 Studio:

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

Rule Team Server Query Constructs

The following condition predicates are specific to Rule Team Server:

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 Rule Team Server:

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