Is there a way to call the CaseType rule created in FW layer from an Implementation layer?
If there is a case type in the FW layer and I have to instantiate that case type from my implementation layer is there any way to call it other than copy that CaseType to my implementation layer? ( assume I don not have to customize anything in the impl layer , however I do have an Impl layer)
In other words If I do not use a casetype , I can create a dummy flow in my impl layer and call the flow in the FW layer.
( I could customize the pyStartCase flow by changing the underlying activities etc etc but it does not seem to be the right way)
Thanks a lot for your response! What you say is definitely right. However this would create an instance/case of FW class which is not intended. I still want to create cases of Impl layer class. Just that I want to make use of the case type created in FW class instead of duplicating the same in all my implementation layers.
In the non case world -- we can make use of all flows in the FW layer without creating any instances of FW layer class. ie we create a starter flow in the impl layer and then call flows in the FW layer. this would create instances of impl layer.
In the case world -- is there a way to achieve the same . Ie instance has to still be my impl layer , I do not want to create case of FW layer , just use the FW case type.
The limitation is if the case is a top level case, it has to exist in the implementation layer to create a new top level case and also list which sub case classes can be added to this top level case. Unfortunately the allowed sub cases field is not dynamic in the case type rule. With a sub case however, the implementation layer case type rule for the sub case can simply be deleted and it would be inherited from the FW layer (assuming there are no other sub cases added to this sub case).
1. Retrieve the IMPL class name using DCR and invoke the OOTB activity "pxCreateTopCase" by passing appropriate parameters - should create a case instance of IMPL class but execute the case type rule defined in FW layer
2. If instantiating manually using create menu, put the implementation class and case type in the cases & data tab of the application rule
3. You can also create a case type rule in IMPL layer and just drag and drop flows / steps from FW layer onto the same; in future if there are updates to the appropriate step/flow, no updates are required in the case type rule and the latest update will automatically be incorporated.
You can import/extend a framework layer casetype so that all the features/functionality of FW layer can be utilized or you can create a casetype in implementation layer call a flows/rules so that workobject will be created of implementation class.