how to Start a flow and based on the value of a property entered by user and then decide which case Specialization to choose in constellation
Imagine there is a new customer and he clicks on membership type Gold /Silver based on that value another case should instantiate which has Gold and Silver specialization
In App Studio, you can navigate to the Settings tab of a case type and configure the Specialization Option. Based on your example, Customer Status (Gold/Silver)
Do think about which specialization option is the best here. If there are no specific reporting or security requirements related to the difference in MemberShipType, then ask yourself if a separate case is really necessary.
I.e. if there is a page .MemberShip on the case, the class of MemberShip itself could vary according to its MemberShipType.
I could then call a flow on the .MemberShip page and at runtime, rule resolution determines which specialization is called.
Another route could be a data-instance-first pattern where a customer chooses a MemberShip type, and then starts a case that uses circumstancing. It simplifies your design if you still need a distinct case type for MemberShip types so you don’t have to account for case-subcase dependencies, data management and things like locking issues.
Ultimately, anything is possible but Occam’s razor considering…
I was thinking the same as @BasRulesMatter, keeping it simple, generating the case you’ve selected (data reference).
This approach works in both a Traditional UI and Constellation context, which for me, is important for the future compatibility (if you are on Traditional now).
I last did this on a Theme-Cosmos (Traditional UI), where we had “a case that creates another case” based on some details filled out on the initial form. It can only be achieved in Dev Studio (as that has the “other” option, that allows dynamic use of a property from your data reference to set the class)
Hi Marc,
Thanks for your inputs.But here the actual requirement is little different.We want the same class for Gold and Silver ,only stages are different. On constellation how to have a starter flow,where we can take user inputs (which decide which specialization to choose and create the case).Should i create a new case type just to receive inputs and decide which specialization to choose.
Thanks for your inputs.But here the actual requirement is little different.We want the same class for Gold and Silver ,only stages are different.We have already Gold case type built and that should be the base and have a silver case as a case specialization(Not class). On constellation how to have a starter flow,where we can take user inputs (which decide which specialization to choose and create the case).Should i create a new case type just to receive inputs and decide which specialization to choose.
I havent seen dynamically changing class implemented in constellation. Let us know how it goes, i forsee you might have challenges.
A case that creates the right case is more Blueprint / App Studio friendly, which is why I would go down that path. Thar said, depending how different the cases are, you couls just use “start process” when rules for gold/silver all in one case. I have seen that work very well and no need for specialisation or circumstancing etc.
