Case Type rule Should be in Fw layer or Impl layer?
in ECS class structure, most of the rules we keep in the Framework layer, and some of the rules which need specialization we bring to Implementation layer. We keep work class both in FW layer and Impl layer, because to pint different work table.
now question is for Case Type rule, assume there is no requirement of specialization in the case type rule for Impl layer, then what is the best practice?
whether same case type rule should be in both FW and IMPL layer
Case types are usually created in implementation layer, but according to the point you have mentioned, you no more do any implementation on the case type. So, you create this in FW layer.
To suggest best practice you create case type in FW when you don't have any enhancements in future.
We're facing similar question in our client project. Looks like if IMPL can reuse FW case type as it is without any customization, then we can define case type in FW. But, most likely, IMPL will want to change something in FW case type (e.g. add a new stage step). Once we 'Save As' a case type from FW to IMPL, then this is no longer a reuse.
Looks like each IMPL will eventually end up having its own case type (which can be originally saved from case type in FW).
In terms of best practice, it won't hurt to define a case type in FW with as many capabilities as possible, but note that IMPL will want to eventually Save As and extend it.