Distribution Rule 

The data object model defined in the Data Orchestration Engine (DOE) is based on the mobile applications to be installed on the mobile devices. Mobile devices do not require the complete data set as available for a particular data object model on the DOE. So data distribution to the mobile devices must be based on the criteria fields, which are defined by specific values.

These criteria are defined in distribution rules which can be added to an existing data object. You can assign one or many distribution rules to a distribution model.

If you add more than one distribution rule to a distribution model, DOE calculates these rules with an OR condition. This means that the devices receive all the data object instances that satisfy the condition of at least one of these rules. They do not have to satisfy all of them.

Distribution rules can be defined at distribution model level (direct rules) or at dependency level (dependency rules). Dependency rules are used to filter the instances of the following  data object sent to the client, while direct rules are used to filter the instances of the root data object for which the distribution model is defined. Since dependency distribution rules are based on the following data object of a dependency, they are only executed if the conditions of the dependency are met. That is, only if the following  data object is distributed (because the Leading data object is distributed) does the system evaluate the dependency rule.

Assigning distribution rules is not mandatory for a distribution model.

A distribution rule comprises information from the data object and the devices that are to receive specific instances of the object type. The following list identifies the elements of a distribution rule as they are defined in the Distribution Modeler.

·        Rule Details

The rule details contain the name of the rule and its description.

●      Rule Fields

The rule fields define the attributes used as criteria for the rule. In addition, an operator is defined for the mapping of these attributes.

●      Logic Selection

The logic defines the type of mapping used to map the data object attributes to the receiver attributes.

¡        SubGen Mapping

With this option, the attributes are mapped to the receiver attributes via a subscription generation data object.

○       Device Attribute Mapping

With this option, the attributes are mapped directly to the receiver attributes.

○       None

With this option, you use the date pattern or constant value mapping types.

●      Logic Details

This defines the exact attributes to be mapped.

●      Device Binding

This defines how the data object data is to be distributed by device. The options include None, All, and Device Binding.

¡        None

Indicates that the data object is not to be distributed to any devices by rule definition. You have to select specific devices in the SAP NetWeaver Mobile Administrator.

○       All

Indicates that this rule is valid for all devices.

○       Device Binding

Allows you to define this rule as valid for a specific device or for a group of devices matching defined criteria.

●      Execution Plan

This allows you to define the events, for example, Device Addition and Device Removal, for rule evaluation and distribution. Additionally, you can schedule rule evaluation at specific intervals, if required.

The Distribution Rule wizard supports the process of developing a rule. When you have completed the wizard steps, you can activate the rule.