Using Primary Pull to Retrieve Custom Attributes

You can define custom attributes for every item in your inbox. For example, you have an item an invoice receipt. Apart from the standard attributes, you can define custom ones, for example invoice value. When you define custom attributes, they are retrieved to your inbox asynchronously from the standard attributes. This means that once an item arrives, these custom attributes are retrieved in additional calls to the backend. For performance reasons, in order to minimize response times to the end user, this may happen while the item is displayed to the end user - causing such attributes to be empty initially and only to appear in subsequent requests.

Depending on the implementation of the connector, the item provider may also define hollow attributes for each item. This means that after the first call to the backend retrieves all items for users, some attributes (the hollow attributes) remain empty. They are displayed and populated with value with subsequent calls to the backend. You cannot edit or configure the hollow attributes.

It is possible to synchronously load the custom and hollow attributes with the primary pull of items of the connectors you configured for. In this case you do not need to do several refreshes to fill in the custom attributes. To do this, you can enable the synchronous retrieval of items, standard attributes and custom attributes.

For more information on custom attributes, see CustomAttributes, CustomAttributeSource and Attribute .