The Distribution Modeler provides the means for deploying specific DO data to mobile devices. The deployment variations are determined for each DO by adding rules for a distribution model, creating dependencies for a distribution model, and adding rules for a dependency.
A distribution dependency is a distribution relationship between two standard DOs that is defined in a distribution model. One of the DOs is defined as the Leading DO and the other as the Following DO. Whenever a message of a Leading DO is distributed to some mobile device, the corresponding messages of the Following DO will also get distributed.
Dependencies can be defined based on associations which have been created between two standard DOs in the DO Builder.
One can define a rule or bulk rule over a dependency and can define conditional dependencies in the Distribution Modeler. These features allow you to further filter the Following DO messages to be distributed.
In this blog we will talk about a simple dependency between two data objects.
Distribution Dependency
Definition
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. The application developers use a distribution dependency to ensure that related DOs are distributed together to mobile devices. The developer can base the definition of the dependency on an association defined at DO node level.
Here will take the example scenario for dependency.
In this example, the users are supposed to meet customer and address the customer's concerns Please refer
Distribution Modeling in Data Orchestration Engine - 4. Each user gets an update on their device about the customer and based on the update user goes and meet the customer, update the customer status. Further for simplicity assume each device is having one and only one user, and similarly each user is assigned to one device only.
Let the following list represent the available users/receivers in the system:
All receivers are assigned the DM-SWCV where the rule is modeled.
Let the records of customer object are having following fields: Name, type, item ordered and quantity.
So suppose the set-A, as identified by CDS table entries look like:
Let us consider the business case in which the sales person also needs the item information which is stored in the different DO altogether. So to achieve this functionality the application developer can create a dependency between the Customer DO and Item DO and can define the relationship. While creating a dependency the application developer can select the leading and the following data object, the node and the key that actually refers to the following data object instance. He can also create a dependency based on the association that has already been created at the time of DO creations.
In this case suppose the information about Item Ordered is stored in ITEM-DO and the following information is there in the CDS table of the ITEM-DO. Let's consider it as set- A for ITEM- DO
Suppose in this case, administrator assigns only RCVR-B to rule. So the set-C will now look like:
So in this case, the set-D, final output will look like:
The dependency will be calculated by taking the Cartesian product of final set -D with the CDS table entries of set-A of ITEM DO based on the reference key of CUSTOMER to ITEM-DO . In this case the final set D contains CUSTOMER-A, CUSTOMER-B and CUSTOMER-C. So the dependent DO instances will be calculated based on that and the following items will be sent to the receivers
The dependency itself will not distribute the data of its own rather it will send the following DO instances whenever the leading DO instances are sent to the device by distribution rule on it. The distribution rule can be of any type like bulk rule, Constant Rule, Date Pattern, Device attribute mapping, Subgen Mapping
In this case, the evaluation of Item Data object will take place whenever:
i- Rule on leading 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
