In order to be used during order decomposition and orchestration, Vlocity Order
Management technical products must be described using attributes, not fields.
What does it mean when process boxes are stacked vertically in an orchestration plan?
What do you use to sequence orchestration items within an orchestration plan?
When creating a Many-to-One (M:1) decomposition relationship, what will happen if the source and destination attributes have the same name?
In a mapping rule, destination values can be mapped from a field or an attribute on the product entity?
The Depends On dependency type specifies that the Dependency Item must reach a Completed state prior to processing the linked orchestration item definition.
What is the maximum number of decomposition levels recommended by Vlocity as a best practice?
Which type of mapping rule allows you to specify the exact string content of a destination attribute value?