Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (e.g. React). Learn more.
Articles, Banners, and Collections are represented as cq:Pages in AEM.
They share the same common properties found in any cq:Page in addition to several others shown below that represent Adobe Experience Manager (AEM) Mobile On-Demand services metadata and integration supporting properties.
The following tables describe the content properties and nodes.
Common Integration Properties
Property Name
Type
Defaults or Expected Values
Description
dps-id
String
assigned by AEM Mobile and stored by AEM once uploaded to AEM Mobile or imported from AEM Mobile
dps-resourceType
String
dps:Article
dps:Banner
dps-version
String
version of AEM Mobile entity (also contained within the full aemm-id)
dps-lastSynced
Date
date of last sync/import from AEM Mobile into AEM
dps-lastUploaded
Date
date of last upload from AEM to AEM Mobile
dps-lastUploadedBy
String:userid
id user that performed the last upload request from AEM to AEM Mobile