Paging

Web applications that are created with X4 Activities Web App automatically support paging in the master/detail and list components. Therefore, the process that provides data for these components must also support paging an process information on how many objects are to be read from which area.

With paging, data is only loaded in subsets from the data source step by step. This avoids large data streams that are very difficult to process by the data source or the browser. Unlike conventional Web applications, Web applications created with X4 Activities Web Apps make it possible to reload the new data while scrolling. The user does not have to explicitly turn to the next page.

Sample request

The component that is linked with a Technical Process sends paging requests that can be processed. offset is used to define from which object the readout is to start. limit specifies how many objects are to be queried.

<?xml version="1.0" encoding="UTF-8" ?>
<Search offset="0" limit="50">
	<OrderBy />
	<Where />
</Search>

Attribute	Description
offset	Defines the offset of the data query, i.e. from which data set the data source is to be read. Possible values: Integer
limit	Number of data sets to be included in the response. Possible values: Integer greater than 0 The value of this attribute is automatically stored by the pageSize attribute of the List component!

Sample response

The response that is returned by the Technical Process must contain information on how many objects are contained in the list (attribute size) in addition to the requested objects, so that it is clear if further objects need to be queried.

<OkList size="2">
	<List>
		<Description>Value</Description>
		<Id>0</Id>
	</List>
	<List>
		<Description>Value</Description>
		<Id>1</Id>
	</List>
</OkList>