When working on rules in both Rule Designer and Decision Center, what is good practice to ensure BOM consistency?

Question

Options

• ADeprecate obsolete classes and members.
• BUse the merge feature to align discrepancies.
• CDelete BOM classes and members in Rule Designer.
• DOnly change arguments in the BOM in Rule Designer.

• A
  17% (4)
• B
  4% (1)
• C
  74% (17)
• D
  4% (1)

Explanation

Deleting BOM classes and members in Rule Designer (option C) is the correct practice because Rule Designer is the authoritative source for the BOM. When you remove obsolete or inconsistent elements there, the cleaned-up BOM is then deployed to Decision Center, ensuring both environments stay aligned. Making structural BOM changes anywhere other than Rule Designer risks leaving orphaned or contradictory definitions in Decision Center.

Why the distractors are wrong:

• A (Deprecate): Deprecation only marks elements as outdated - it doesn't remove them, so inconsistencies remain in the BOM and can still confuse rule authors in Decision Center.
• B (Merge feature): No standard "merge" feature exists in ODM for resolving BOM discrepancies between the two environments; this option describes a non-existent workflow.
• D (Only change arguments): Restricting changes to arguments alone is too narrow - full BOM management (including class and member deletion) must happen in Rule Designer, not just argument-level edits.

Memory tip: Think "Designer Owns, Center Consumes." Rule Designer is the BOM's single source of truth; Decision Center consumes what's deployed from it. To keep them consistent, all structural cleanup - especially deletions - must happen in Rule Designer first.

No community discussion yet for this question.