<< Prev Question Next Question >>
Question 13/30
What are the four reasons one might create a technical product entity in Vlocity Order Management?
1The commercial product entity cannot fully describe the product entity in terms that can be understood by the downstream systems.
2.The details of the product entity should be masked from the customer.
3.The product entity maps to a multitude of underlying products, services or resources.
4. To consolidate the number of callouts to a downstream system.
To adhere to TMForum / SIDs product modelling best practices.
To create a fully articulated product hierarchy.
Because Vlocity Order Management requires technical products and their attributes to describe commercial products in terms that can be understood by downstream systems.
In order to be used during order decomposition and orchestration, Vlocity Order Management technical products must be described using attributes, not fields.
1The commercial product entity cannot fully describe the product entity in terms that can be understood by the downstream systems.
2.The details of the product entity should be masked from the customer.
3.The product entity maps to a multitude of underlying products, services or resources.
4. To consolidate the number of callouts to a downstream system.
To adhere to TMForum / SIDs product modelling best practices.
To create a fully articulated product hierarchy.
Because Vlocity Order Management requires technical products and their attributes to describe commercial products in terms that can be understood by downstream systems.
In order to be used during order decomposition and orchestration, Vlocity Order Management technical products must be described using attributes, not fields.
