Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to specify application RuleSets in a product rule

Updated on September 10, 2021


When creating a product rule you can specify an application to be included. The RuleSets and versions referenced in the application rule are included in the archive file. This feature eliminates the need to enter each RuleSet in the product rule form. After you have deployed the application RuleSets on your destination system, you can use a product rule to individually update any of the RuleSets or add a new one to the application.

This article describes how you include application RuleSets in your product rule.


Suggested Approach

To package the application RuleSets and their rules, do the following in a product rule form:

  1. On the Contents tab In the Applications to Include section, use SmartPrompt to select an application name and application version in their respective fields as shown here:

  1. Select the Custom/Production RuleSets check box if you would like to include those rules as referenced by the application version for Production RuleSets.
  2. Select the Shared/Component RuleSets check box if you would like to include those rules as referenced by the application version for Component & Shared RuleSets.

Here are the RuleSets in the application rule that will be included in the ZIP archive file:

By default, all versions up to and including the version in the application are included.  For example, if your application references OrderEntryDev:02-03-05, the ZIP archive file produced from this product rule will include all the rules in OrderEntryDev: 02-01-zz, 02-02-zz, and 02-03-zz. During the import process, RuleSets specified in this section are loaded first. Therefore, specifying a maximum version of OrderEntryDev:02-03-05 in the RuleSets to Include section (in the product rule form) has no effect as the version has already been loaded by way of the application rule import. 

After the application RuleSets have been deployed on the destination system, you can use the RuleSets to Include section to update individual RuleSets. Here is an example showing the addition of a new production RuleSet OrderEntryDev4:01-01 and a patch for application RuleSet OrderEntrySystem:02-05-02.


  • Instances in data classes are not imported. Use the Classes to Include section to specify the data required in your application. For more information, see How to ensure that a product rule includes all parts of an application.
  • If the application is built on another application ( Include Parent is selected in the application rule), make sure that its RuleSets are on the destination system. Otherwise, import the parent application first.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us