Hi Team,

I have seen a few of the applications has ApplicationData page under pyWorkPage, as a best practice, in order not to keep everything on the pyWorkPage. I will take a sample application to explain more:

Application:Ins,  CG: ABC-Ins-Work, Case types- ABC-Ins-Work-Case1, ABC-Ins-Work-Case2, Data class: ABC-Ins-Data(Abstract)

From the above application class structure, I have a few queries about this:

1. Where should I create my ApplicationData Page

2. What should be the definition of ApplicationData Page

3. Is it best practice to create a separate concrete/abstract class (ABC-Ins-Data-Case1/Case2/etc..) for each case type, and create a page like ApplicationData(ABC-Ins-Data-Case1/ABC-Ins-Data-Case2) under each case type class

   a) If we create a separate class, how can we exchange the data between the 2 case types?

4. If we go with ApplicationData(ABC-Ins-Data), do we need to make it concrete?

    If I store all the data under ApplicationData page, If I want to report on data under the ApplicationData page context, do we need to expose it from the work page(.ApplicationData.ComplaintNumber), or as we created it as a concrete class can directly query on the freshly created table?