Subject: Best Practice: Filtering DCM Lifecycle Stages Based on a Related Object (Product Type)
Hi Team,
I am looking for advice on the best way to handle a product-specific lifecycle requirement in Creatio using Dynamic Case Management (DCM).
We need to introduce three custom stages into our Opportunity pipeline. However, these stages should only be active and visible if the attached product with specific product value. For all other product types, these stages should be skipped or hidden.
Our product data does not live as a direct dropdown column on the primary Opportunity/Lead page. Instead, products are tracked via a separate child/detail table (Product in Lead / Product in Opportunity).
Because the data lives in a related detail object:
- We cannot directly reference the product type column inside the high-level DCM Condition Selector ("Use this case with records where:") to create a separate Loan case.
- We cannot use UI-level Business Rules, as they cannot dynamically alter or hide entire DCM chevron header stages on the fly.
Questions for the Team
- Is using a background sub-process with a Read Data filter the standard best practice for making steps conditional based on related detail objects?
- Is there a cleaner way in Creatio to swap or filter an two filter condition entire DCM case based on a criteria and product type that lives in a child/detail table rather than a primary column?
Thanks in advance for your insights!