Understanding PeopleSoft Documents in the Mobile Application Platform

PeopleSoft Documents provide the data structure for mobile applications you build with the Mobile Application Platform framework.

PeopleSoft Pure Internet Architecture applications pass the complete business object to the client where the data must be serialized. However, since the mobile applications you build using the Mobile Application Platform use PeopleSoft documents for the business object definition, only the necessary data is passed to and serialized on the client.

The PeopleSoft Documents framework is documented in the Documents Technology.

If you are familiar with developing applications for the PeopleSoft Pure Internet Architecture (PIA), the following comparisons may be helpful.

  • In the PeopleSoft Pure Internet Architecture a rowset provides the data structure for a PeopleSoft Pure Internet Architecture page. In the Mobile Application Platform, a PeopleSoft document provides the data structure for your mobile application pages contained in a layout.

  • A parent PeopleSoft document roughly equates to a Level 0 record in the PeopleSoft Pure Internet Architecture framework. And document compound and collection elements roughly equate to Level 1 records in the PeopleSoft Pure Internet Architecture framework.

Documents allow multi-level objects to be flattened down to the equivalent of Level 1 records because there is no key dependency needed between the levels. The actual keys for a row of data are part of the application URL created. Any processing of the data is then performed on the web server.

The following examples show a three-level typical rowset keyed structure, flattened to an equivalent PeopleSoft document structure.

Image: Three-level rowset keyed structure

This example illustrates a typical three-level rowset keyed structure:

Typical three-level rowset keyed structure

In the example the Level 0 record is QE_FLIGHTDATA, the Level 1 record is QE_ARMAMENT, the Level 2 record is QE_WPN_PRESETS, and the Level 3 record is QE_STAT_CONFIG.

Image: PeopleSoft document equivalent of the three-level rowset structure

This example shows the same structure defined in a PeopleSoft document:

Three-level keyed structure in a PeopleSoft document

In this example QE_FLIGHTDATA is equal to a Level 0/root record. QE_ARMAMENT, QE_WPN_PRESETS, and QE_STAT_CONFIG are equivalent to Level 1 records. The following icons appear in the document structure:



Primitive element

Primitive document element.

Collection element

Collection document element.

Compound element

Compound document element.

In the PeopleSoft documents terminology, the previous example shows QE_FLIGHTDATA is the root element, that has ten (10) primitive elements defined (QE_ACNUMBER, QE_MSI_SENSOR, QE_OFP, and so on.)

ARM_COLLECTION is a compound child element of the QE_FLIGHTDATA element. Within that the compound element, a collection child element called QE_ARMAMENT is defined. And QE_ACNUMBER, QE_STATIONNBR, QE_AGMODE, and so on, are primitive child elements of the QE_ARMAMENT compound element.

Similarly, WPN_COLLECTION and STAT_COLLECTION are collection child elements of QE_FLIGHTDATA. Each of those collection elements has a child compound element defined, QE_WPN_PRESETS and QE_STAT_CONFIG respectively. And each of those compound elements has several child primitives defined.