Specifying decision types

The decision types are specified in the WODM Integration Lookup Table in Product Master.

About this task

If a decision type is applicable to all (or most of the products) in the catalog, then the solution designer can associate the decision type with the primary spec of the catalog.

If the decision type is applicable to only products in a particular category, then the solution designer can associate the decision type with an item secondary spec for that category.

The solution designer uses the existing Product Master screens to add a decision type entry into the Decision Types Lookup Table, to modify an existing entry, or remove an entry.

There can be multiple rule projects that are associated with an entry, which means multiple decision types are displayed in the Manage decisions tab.

Procedure

Identify a list of decision types that are used by the solution.
For example, the solution designer must decide on the following:
  1. Decision type Key.
    The primary key.
  2. Decision Type Name (localized).
    The localized name of the decision type is displayed to the user in the Product Master user interface when you work with rules associated with the product.
    Note: The default locale is en_US. When the localized Decision Type Name is not provided, the Decision type Key itself is used as the display name.
  3. Rule Package Name.
    The Rule Package Name identifies the package that Product Master expects to exist in all rule projects that are used for the decision type. Any new rules that are created from Product Master user interface for the decision type is created under this rule package.
  4. Spec Name.
    The solution designer updates the identified spec in Spec Name attribute and adds a attribute in the spec at the path that is identified in the Rule Project Attribute Path column for the decision type.
  5. Rule Project Attribute Path.
    The type of the Rule Project Attribute in the Spec could be String or String enumeration and is ideally to be marked as hidden to prevent it from showing in the Attributes tab of the single edit or multi-edit page in Product Master user interface.
    Note: By using a string enumeration type attribute with an enumeration rule, the solution can provide the ability for a business user to choose a Rule Project through the Product Master user interface from a set of applicable rule projects for the item or category. In this model, however, the attribute might not be marked hidden, and the solution needs to tackle any cleanup actions that are needed when disassociating rule projects from an item or category.