References/Resource Category: Difference between revisions

* Monetary-component propagation runs through Celery, so descendants' <code>calculated_monetary_components</code> is eventually consistent after a write.

* Monetary-component fields serialize only for <code>resource_type == &quot;charge_item_definition&quot;</code>; during merges, component identity rests on the nested <code>code.system</code> + <code>code.code</code> pair.

{{Related}}