OmniStudioIntermediatedecision-matrixexpression-setrules
Implement Decision Matrices and Expression Sets for business rules
Real World Scenario
Underwriting eligibility rules change monthly; hardcoded OmniScript formulas require developer deployment each change.
Expected Answer
• Decision Matrix for tabular lookups: state × product × age → eligibility tier
• Expression Set for calculated formulas with versioned rule sets
• Business users maintain matrices via OmniStudio admin UI with change control
• Integration Procedure invokes matrix at runtime passing OmniScript context
• Effective dating on matrix versions for future-dated rule changes
• Audit trail who changed matrix when for compliance
• Test matrix edge cases in sandbox before production activation
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Decision Matrix for tabular lookups: state × product × age → eligibility tier. Expression Set for calculated formulas with versioned rule sets. Pick based on your integration pattern and team capability. Declarative rules belong in Decision Matrices—reserve Apex for rules exceeding matrix expressiveness. Balance speed of delivery with maintainability.
Architect Perspective
Declarative rules belong in Decision Matrices—reserve Apex for rules exceeding matrix expressiveness.