Collectors are a mechanism to move data from backend systems into the ONE Cloud to ensure that the clients can quickly retrieve and render Cards. Each Collector is optimized to work with a specific backend system and simply integrates with the ONE Cloud at the point of passing data into the Card API along with the identity of the associated card implementation.
How are cards working with collectors?
Cards are showing up in the “Hub” area of the client app. When cards have actions assigned, they will also show up in the “Tasks” area of the client app.
Cards always have two screens. The summary screen which you see first in the stream and the detail screen which you see, when you tap on a card.
Summary screen has a static header, customizable body and could have an action bar
Components: Cards have always two components. The metadata from the Collector for a given backend system and the Card UI based on an AppBuilder Card project. If cards are using actions, usually a third component is included, the Connector to the given backend system.
Metadata from a Collector
A Collector is a piece of software which usually gets installed in the backend system (e.g. SharePoint or SAP) or at some place from where it can connect with the backend.
Metadata is the data which is already in a well formed format, which can be consumed by the ONE cloud.
Sample Metdata (JSON format):
The AppBuilder Card Project is the UI and translation layer of a Card
The UI defines the look and feel of the card screens (summary and detail).
The translation of the incoming metadata is performed in the code-behind in a “TranslateCard” method. This also allows to manipulate data, enable push notifications and more.
Translation of metadata to screen fields (Definition of header information, Push notification, …)
Mapping of metadata fields to screen fields
Today Cards can have two different kind of actions a single action (“Button”) and a “ConfirmAction”. A single action directly executes an assigned action and a confirm action provides upfront an entry field for a simple string/text.
Actions are usually connecting back to a backend system like on approvals back to SharePoint or SAP. Therefore the ONE connectors can be used to define certain actions
Action Bar on a mobile device
This diagram should give a high level overview of the overall card dataflow