A distribution dependency establishes a relationship between Data objects (DOs) so that the related DOs and their data are distributed to the mobile devices as a set. For further filtering the dependent data object instance based on the business criteria we can define a dependency rule over the dependency. The dependency rule by itself will not distribute any data to the mobile device rather it will filter the dependent data object instances to be sent to the device based on the defined criteria. So the instances of the following data object that passes the dependency rule will be the subset of the instances that are calculated based on plane dependency.
Here will take the example scenario for dependency Rule.
Let us take an example and see the same. In this example, the users are supposed to meet the customer and address the customer’s concerns Please refer Distribution Dependendency. The following instances of ITEM DO were calculated based on the dependency i.e. the final set-D of ITEM DO as calculated based on the dependency was
Now let us consider a business case in which the salesperson needs the information about the item only if the Item cost is more than $100.
To achieve this application developer can define a ‘normal dependency rule’ on the dependency saying send the following instance only if it satisfies the criteria
‘Cost Per Unit > 100′.
Now while calculating the following data object instances these criterias defined in the distribution rule will be taken into consideration. In the example of ITEM DO the following CDS entries are available. So the set- contains
|Type||Cost per Unit|
The dependency rule will be calculated by taking the Cartesian product of final set -D with the CDS table entries of the following data object instances i.e. set-A of ITEM DO based on the criteria field defined in the dependency rule. In this case the final output of the set D for ITEM DO will be calculated as:
|Type||Cost per Unit|
So in this case the ITEM-1 will be filtered out by the dependency rule and will not be sent to the receivers.
The dependency rule can be of any of the following type:
1. Constant Rule
2. Date Pattern
3. Device attribute mapping
4. Subgen Mapping
And also it can contain all arithmetic operations similar to the distribution rule. Please refer Distribution Modeling in Data Orchestration Engine – 4.
The working of all the above rules is same as the normal rule with the only difference that dependency rule works on the following data object and it is used to filter the following DO instances calculated by dependency.
The dependency rule in contrast to the normal distribution rule does not send any data to the receivers by itself rather it filters the dependent DO instances calculated by dependency
If the dependency rule is deactivated then none of the following DO instances will be calculated for the device.
In this case, the evaluation of Item Data object will take place whenever:
i- Rule on leading/following DO is activated or de-activated, or
ii- when administrator assign or un-assigns receiver from rule, or
iii- whenever the DM-SWCV for the assigned receiver is changed, or
iv- Whenever new instance is downloaded to DOE which corresponds to the following DO instance. In this case ITEM DO.
Similarly, the user can create a distribution rule with different set of operators such that “<=”, “>”, “>=”, “=”, “! =”, “between” and “CP (Contain Pattern)”.