Product Patch rules
Completing the Create, Save As, or Specialization form

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

• Creating a rule or data instance
• Copying a rule or data instance
• Creating a specialized or circumstance rule

This information identifies the key parts and options that apply to the record type that you are creating.

Create a product patch rule by selecting Product Patch from the SysAdmin category.

Key parts:

A product patch rule has three key parts. In the first two key parts (Product Name and Product Version), identify the existing product rule to which this patch applies:

NOTE: Choose the RuleSet and version into which you place the new product rule carefully. Its direct or indirect prerequisites, listed in the Requires RuleSets and Versions list, must include the RuleSets and versions to be included in the product.

Rule resolution

Product patch rules not ordinarily referenced in other rules. However rule resolution does apply. When searching for a product patch rule, the system:

• Filters candidate rules based on a requestor's RuleSet list of RuleSets and versions
• Finds circumstance-qualified rules that override base rules with the same key

Time-qualified resolution features are not available for product patch rules.

About Product Patch rules

Open topic with navigation