As Per requirement,
Separation is also required by Division, but only for the Recall process. That is, for performance reasons, Recall records must be stored separately for the Velo, Luxo, and Floato divisions.
Question 1: Can we go for CG/does not belongs to CG.In WCRFW Sample case study in Application Design Topic.
Are mentioned as CG. Can we make it as Does not belongs to CG.
Question 2: How abt: Velo-Boat-WCRBoat-Work-Recall ( No any specific. Just we have only floato line.)
Do we need to create CG/Does not bleongs to for
Velo-Boat-WCRBoat-Work-Recall / Velo-Boat-WCRBoat-Work-Recall-Floato.
In Solution why we did not created Velo-Boat-WCRBoat-Work-Recall-Floato instead of Velo-Boat-WCRBoat-Work-Recall. Here Velo-Boat-WCRBoat-Work-Recall is belongs to Velo-Boat-WCRBoat-Work. In this case, Recall is sharing table space where Claim/ClaimTask/Part Return stored in tables.
Question 1: No, this is still a case (or work type) therefore the setting should be "is a class group" since it is to be stored seperately.
Question 2: See above. Does not belong to a CG implies it is a data class which is not correct.
Question 3: The design in the solution satisfies the requirement that Floato Recall case is stored separately from the Velo and Luxo Recall cases. It is ok that it shares space with the Claim/Claim Tasks.
An important point to realize from this case study is that class groups allow independant storage and that a class configured as a class group may inherit and be stored independantly from another class configured as a class group.