How do VCPs and VCMs work together?

How do VCPs and VCMs work together?

• A. VCMs replace VCPs.
• B. VCPs call one or more VCMs when there are many factors.
• C. They are unrelated.
• D. VCMs only store configuration.

Answer: (B)

In OmniStudio, the page that users interact with (the VCP) handles the input flow and UI, while the configuration logic and data (the VCM) holds the rules for how factors relate, what options are allowed, and how calculations like pricing or eligibility are determined. When there are many factors to consider, the VCP relies on one or more VCMs to provide the needed configuration data and logic rather than trying to encode everything directly on the UI. The VCP passes user input to the VCMs, and the VCMs return valid options, dependencies, and computed results, which the VCP then presents to the user. This separation keeps complex configuration manageable, promotes reuse, and ensures business rules live in a centralized place. For example, if configuring a product with many options, the VCP can ask for selections and then ask the VCMs for available compatible options and pricing. The VCMs encapsulate the rules for what combinations are allowed and how pricing should be calculated, returning results that guide the next steps in the UI. The other options don’t fit because VCMs don’t replace VCPs, they aren’t unrelated, and VCMs aren’t just storage—they encapsulate configuration data and logic used by the VCP to drive the user experience.

In OmniStudio, the page that users interact with (the VCP) handles the input flow and UI, while the configuration logic and data (the VCM) holds the rules for how factors relate, what options are allowed, and how calculations like pricing or eligibility are determined. When there are many factors to consider, the VCP relies on one or more VCMs to provide the needed configuration data and logic rather than trying to encode everything directly on the UI. The VCP passes user input to the VCMs, and the VCMs return valid options, dependencies, and computed results, which the VCP then presents to the user. This separation keeps complex configuration manageable, promotes reuse, and ensures business rules live in a centralized place.

For example, if configuring a product with many options, the VCP can ask for selections and then ask the VCMs for available compatible options and pricing. The VCMs encapsulate the rules for what combinations are allowed and how pricing should be calculated, returning results that guide the next steps in the UI.

The other options don’t fit because VCMs don’t replace VCPs, they aren’t unrelated, and VCMs aren’t just storage—they encapsulate configuration data and logic used by the VCP to drive the user experience.