There are different ways in which Data Pages can be utilized. These different ways depend on how data is needed in the application.
For example, lets look at a scenario where an HR Application needs an employee record for certain HR related process. In that case we may just get the employee data from System of Records (it could be an external database or client’s legacy platform) and load it into a data page. This data page will remain in memory based on its scope (scope of data page is discussed in Data Page Introduction topic). Application can use this data page whenever it needs to refer employee data in HR process.
Another scenario could be when a particular Application needs data at specific point in process and it is expected that data might change with time. Data accuracy with time might play an important role in decision making in the business process.
For Example, an Application uses Stock value of a Company, business requirement might dictate that snapshot of Stock value is taken at certain point in time (i.e. in morning) and used in the business process as it might change during the day. In this case, data will still be retrieved and loaded into the data page but that data will also be copied into the work object and whenever stock value need to be used, reference in work object will be used instead of reference in data page.
So now we can see the difference in above 2 scenarios, in first scenario we used Data Page directly as the reference point but in second scenario we used data in work object as reference point.
There are common patterns which we frequently encounter in the Applications. Below are the 4 patterns which dictate how data page should be used.
- SOR Pattern
- Snapshot Pattern
- Reference Pattern
- Keyed Access Pattern