Defining the Distribution Model

Use

A distribution model designates a data object and its data to be distributed to mobile devices. This tutorial requires one distribution model. This is defined for the Service Order data object.

Procedure

1. Select the Service Order data object as the distribution model data object and create a distribution model called SERVICEORDER.

   More information: Creating a Distribution Model

2. Add two dependencies to the SERVICEORDER distribution model, using the associations defined between the Customer data object and the Service Order data object and between the Equipment data object and the Service Order data object. This ensures that the Customer and Equipment data object data is distributed together with the Service Order data object data.

   More information: Creating a Distribution Dependency

   Field	Values for Customer data object	Values for Equipment data object
   Leading data object Name	SERVICEORDER	SERVICEORDER
   Following data object Name	CUSTOMER	EQUIPMENT
   Link data object Type	LEADING	LEADING
   Link data object Name	SERVICEORDER	SERVICEORDER
   Link Segment (node)	CUSTOMER	EQUIPMENT
   Source Field	EXTRACTKEY	EXTRACTKEY
   Target Field	CUS_SYNCKEY_MMW	EQU_SYNCKEY_MMW

   1. Add a rule to the SERVICEORDER distribution model to ensure that only service orders for customers that belong to the region serviced by the employee's work center and that match the employee's qualifications are distributed to the device.

      More information: Adding Rules to a Distribution Model

   2. In the Distribution Rule wizard, proceed as follows:

      In the Rule Fields section:

      1. Select the CUSTOMER node, the REGION attribute of this node and EQ as the operator.

      2. Select the EQUIPMENT node, the EQUIPMENT_TYPE and EQUIPMENT_BRAND attributes of this node, and EQ as the operator for both.

      In the Logic Selection section:

      1. Select SubGen Mapping as the mapping option, and MOBILE as the receiver category type (RMM).

      2. Select WORKCENTER as the subscription generation data object.

         The root node is entered automatically in the SubGen Node field.

      3. Choose the Device Attribute Mapping pushbutton, navigate to the receiver attribute WORKCENTER_ID of your customizing group in the list, select the EQ operator and WORKCENTER_ID in the Attribute Low column.

         This associates the receiver attribute with the corresponding SubGen data object attribute.

      In the Logic Details section:

      1. Select the REGION attribute of the CUSTOMER node and choose the SubGen data object pushbutton, because the value for the region is to be taken from the subscription generation data object.

      2. In the Distribution Rule screen, choose REGION in the Attribute Low column to map the REGION attribute of the subscription generation data object to the REGION attribute of the Service Order data object.

      3. Select the EQUIPMENT_TYPE and EQUIPMENT_BRAND attributes and choose the Device Attribute pushbutton.

      4. In the Distribution Rule screen, choose EQUIP_TYPE and EQUIP_BRAND, respectively, in the Attribute Low column to map the EQUIPMENT_TYPE and EQUIPMENT_TYPE attributes of the Service Order data object to the corresponding device attributes.

         • The Execution Plan lists the events that trigger rule evaluation. Add a custom job here that triggers rule evaluation every day at 1 a.m., as the service staff retrieve their jobs first thing in the morning. This makes sure that they receive all orders currently assigned to them.

         • Complete the rule.

   3. Activate the distribution model.

3. Activate the rule.

4. Add a data completeness group to the software component version by selecting the two dependencies you have defined for inclusion in the group. This makes sure that the service orders are distributed by the DOE only to the service staff if the customer and equipment information is also available.

   More information: Defining a Data Completeness Group

You have now defined the distribution logic. You can continue with defining the back-end adapters for the data objects.