Decomposition rule

[Joshua Chen FX]

in the servicenow doc, it says decomposition rule are only valid for product specification (source) 

https://docs.servicenow.com/bundle/vancouver-order-management/page/product/tmt-order-mgt/task/order-...

yet, I've been testing in my instance with demo data, and i see decomposition rule for Service spec > Resource spec + resource order is created only if the decomposition rule is met

am i missing something?

[Community Alums]

Hi @Joshua Chen FX ,

Only if you have a decomposition rule then this rule has to be met to  Resource spec + resource order created.

[ShashankInamdar · Accepted solution]

Hi @Joshua Chen FX ,

Decomposition Rules are not just limited to the source = product specification.

They are applicable across all Specification Relationships in the P-S-R model. Your observations in your personal instance are correct.

I can see why this statement (The specification relationships include the product specifications as the source specifications.) in the documentation link may have caused some confusion.

We can get this rectified to make it more clear. Thank you for bringing this to our attention.

Note: You can also submit your feedback for the documentation via the thumbs up/down icon on the documentation page.

[Joshua Chen FX]

@ShashankInamdar  thanks for the confirmation,

There are few mentions in the doc that create a bit of confusion, including this paragraph:

Note: Decomposition rules are only valid for a product specification. If you create attribute propagation maps, the following message appears when you try to create a decomposition rule that depends on a previously defined attribute-mapping rule:
The decomposition rule record (rule ID) will have dependency on the Attribute mapping rule (rule id). Update this record to avoid dependency on the attribute mapping rule.