Question
Offline Data Pages do not accept Params: need advice.
The customer has a requirement to set up offline data on mobile devices (both iOS and Android).
The backend data set is very large (380k [more? records]; probably too large for performance reasons on the back-end PRPC system and probably too large for the Mobile Device storage.
Previously: Parameters were specified on the Data Page in an attempt to cut down the recordset to a few hundred records.
This approach failed (the sync process would 'hang'): and Pega SMEs were engaged.
SMEs identified the reason: Parameterized Data Pages cannot be used in this context (the params are ignored, or not available in this context).
Therefore the entire data-set was downloaded to the mobile device - unfiltered. (At least on the 'initial sync').
The solution depends on getting the data that is actually needed to be worked on.
For example in this case instead of getting all the flight data for all the passengers for 2 years down to the client for a crew member to access in offline, we need to refine the filter criteria at point of retrieval on server during the packaging sync request::
Suggestions -
1. Add a new column for the crew member to the flight master data table (if possible) so the sync gets filtered data only for the flight manifests of which the crew member is part of. It may not be possible to change existing tables / schema. Instead we can do a Join on the crew member roster with the flight passenger data .
OR
2. Add the condition to the report definition to essentially get only data for the current day (or maybe day before and day ahead) so that crew member gets immediately relevant data . 300 * 200 = 60000 rows.
Once we get that manageable subset we may use large data pages to get data for a particular flight when we run the case.
Thoughts ?