ILOG Rules for .NET User Guides > ILOG Rule Team Server for SharePoint > Rule Properties

Rule properties contain information not related to the logic of the rule. The properties of a business rule appear in the Rule Property Editor.

You cannot create new properties yourself but some can be modified.

Note
The properties described are the default properties. Depending on your specific rule project, you may have others.

The Rule Property Editor will not save rule properties that are incorrect; it will revert to the last correct value.

Authoring properties

The following table describes the default rule properties related to the authoring of rules and indicates whether you can modify these.

Property 
Used To... 
Modifiable 
Author 
See who created the rule or decision table. 
No 
Category 

 
Rules are assigned the Any category by default. 
No 
Creation Date 
See when the rule was created. 
No 
Documentation 
Specify any extra information about a rule, for example what the purpose of the rule is or under what context it was created. 
Yes 
Last Modification Author 
See who last modified the rule. 
No 
Last Modification Date 
See when the rule was last modified. 
No 
Name 
Give a name to the rule or decision table. 

 
There are no limitations on how you can name your rules. However, avoid typing in a space as a name, since it will be difficult to read in the Rule Editor. Similarly, avoid putting a period in your name, since the full name displayed in the Rule Editor is the name followed by the package, separated by a period. 
Yes 
Package 
Give a package name to the rule. 

 
Although your rules are stored in RuleDocs, they are also associated logically to a rule package. When you create a new rule, you must specify the rule name as well as the name of the rule package to which it belongs. The best practice is to place all the rules belonging to a package inside a RuleDoc bearing the same name. 

 
If you choose another rule package, the new rule will be associated logically with the other rule package even though it is stored in the current RuleDoc. 

 
Also, you can introduce a subpackage by placing a period between the name of the package and the subpackage, for example mypackage.mysubpackage

 
There are no limitations on how you name your packages. However, avoid typing in a space as a name, since it will be difficult to read in the Rule Editor. Similarly, avoid putting a period in your name, since the full name displayed in the Rule Editor is the rule name followed by the rule package, separated by a period. 
Yes