This chapter provides an overview of data distribution and discusses how to:
Define mobile customer options.
Define mobile attachment rules.
Set up out-of-date detection.
Enable basic data processing.
Mobile devices may have limited processing power, storage capacity, and display space. You can limit the range and quantity of data that is passed to the mobile device by specifying a data distribution method.
Data distribution is used in mobile applications to:
Implement security.
Filter needed data to download to the mobile device.
Depending on the business objects, mobile applications use these methods to distribute data from the database to the mobile device:
Defining dataset rules creates SQL statements that run during synchronization to select the dataset that is delivered to the mobile device. The result of data distribution rules is a set of data that is appropriate to the user’s roles. The dataset may differ depending on the mobile device.
Spider out.
The result of spidering is that rows of data can be required for the mobile device in addition to those that are selected by the OnSelect event. For example, a contact list on a mobile device includes three people: two from the U.S. states of New York and New Jersey and one from the Canadian province of Ontario. The OnSelect event for state calls for only states or provinces that are in the U.S. Using spidering, the Sync Server retrieves all the U.S. states and also Ontario because Ontario is referenced in the address of a company that is selected to download to the mobile device. Therefore, Ontario, as a state (province) data row, is downloaded (spidered down) and present on the mobile device.
This table lists the data distribution methods that customer data model (CDM) objects use:
Object |
|
Company (RDM_COMPANY_2) |
This object uses:
|
Person (RDM_PERSON_CI) |
This object uses:
|
Site (RDM_SITE_2) |
This object uses:
|
Relationship Component (BO_REL_MOBILE)
The Relationship component sources the data that is in the relationship viewer of various components.
Using dataset rules, you can restrict the amount of relationship instances that are downloaded to the mobile device. If the distribution rules are too restrictive, then only a small number of relationships will be downloaded. Conversely, if the rules are too broad, then performance may suffer as too many transactions are downloaded to the device during synchronization. An option in the mobile installation options enables relationships to spider out from the customer components. This option enables automatic spider-out of relationships one level deep from each customer. This mechanism supplements or replaces data distribution rules.
See Also
PeopleSoft Enterprise Components for CRM 9 PeopleBook
Enterprise PeopleTools PeopleBook: PeopleSoft Mobile Agent
Enterprise PeopleTools PeopleBook: PeopleCode Language Reference
This section discusses how to define mobile customer options.
In PeopleSoft Enterprise CRM, you can define the options for using the CDM for the mobile application. CDM maintains entries and relationships among company, site, contact, consumer, worker, and other business entities.
Page Name |
Object Name |
Navigation |
Usage |
RDM_MOBILE_DFLT |
Set Up CRM, Install, Mobile, Mobile Customer Option |
Define general options for displaying customer information on mobile devices. |
Access the Mobile Customer Option page.
Mobile Options |
Enter the name of this customer option profile. |
Default SetID |
Specify a setID that is used for filtering customer data. |
Read Only |
Select to have all CDM information (for companies, persons, and sites) that is downloaded to the mobile device be read-only. Note. This option applies to PeopleSoft Mobile FieldService only. |
Show Relationship Viewer |
Select to display the Relationship Viewer on mobile devices. |
During a synchronization, this option controls whether the synchronization process spiders out to retrieve the full object, that is, Company, Consumer, and so forth, or if only the name is retrieved. Note. If you select this option, system performance may decrease slightly. |
|
Show 360 Degree View |
Select to display the 360-Degree View on mobile devices. |
Purchase Option |
Select one or more of these purchase options:
|
Person Configuration |
Select the default actions to perform in the Person component when users click the Add button and when they view persons who have multiple roles on the device. Select a default action when users click the Add button:
Select a default action when users view persons who have multiple roles:
|
Role Type ID |
Displays the identification code that is associated with the business object role type. When you add a new role type, the system automatically assigns a value using automatic numbering functionality. |
Description |
Displays the role for which you want to view relationships. |
Business Object Name Type |
Select the type of business object name to apply to the corresponding role type. Values are preferred and alternate. |
Relationship View Name |
Select the relationship view that you want to associate with the role. |
As transactions are encountered during a synchronization, this option controls whether the synchronization process spiders out to the relationships. Note. If both the Spider Out To Relationships and Spider Out To Customer options are selected, all customer data is moved to the mobile device. Depending on the volume of customer data in the system, performance can be affected. |
|
360 Degree Tree Name |
Select a 360-Degree View tree that displays all activities and interactions for the company or contact. It can also display an add and search node for the particular activity of the tree. Click the detail link to navigate to the detail pages for the activity. Click the add link to access a page where you can add the activity. Click the search link to access a page where you can search for the activity. |
Three Sixty View Degree Tab Number |
Displays the tab number of the page in the corresponding component. |
See Also
Working with the Relationship Viewer
Business Object Management Basics
Interactions and 360-Degree Views
This section discusses how to:
Define attachment rules for the PeopleSoft Enterprise Mobile Sales.
Define attachment rules for the Mobile Product component.
Define attachment rules for the PeopleSoft Enterprise Mobile Order Capture.
Define attachment rules for the PeopleSoft Enterprise Mobile FieldService.
Before using the mobile product, set up these attachment settings:
Type of attachments.
Custom size of attachments (if you want to specify the size of some attachments).
Size of product images to be displayed on the mobile device.
Page Name |
Object Name |
Navigation |
Usage |
RSF_SYNC_ATTACH |
Set Up CRM, Business Unit Related, Mobile Rules |
Define attachment rules for the PeopleSoft Enterprise CRM Mobile Sales application. |
|
MOC_OPTIONS_PG |
Set Up CRM, Install, Mobile, Mobile Product Options, Mobile Product Defaults |
Define attachment rules for the Product component on mobile devices. |
|
MOC_OC_OPTIONS_PG |
Set Up CRM, Install, Mobile, Mobile Order Capture Options, Mobile Order Capture Defaults |
Define attachment rules for the PeopleSoft Enterprise CRM Mobile Order Capture application. |
|
RF_MOB_SYNC_OPT |
Set Up CRM, Install, Mobile, Mobile Field Service Options, Mobile Field Service Options |
Define attachment rules for the PeopleSoft Enterprise CRM Mobile FieldService application. |
Note. The Synch to PDA option is no longer in use.
Select the synchronization options for attachments to be passed down from the database to the mobile devices by business unit. Options are All, Size up to, and None. When you select Size up to, enter the maximum attachment size that is allowed in bytes. |
Access the Mobile Product Defaults page.
Note. The PDA Settings group box is no longer in use.
Laptop Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer. Options are All Attachments, Custom Size, and No Attachments. If you select Custom Size, enter the maximum attachment size that is allowed as well. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the laptop computer. The system delivers only attachments that are less than the specified size. |
Images |
Select the size of the product images that you want to pass down from the database to the laptop computer. Values are Large Image, Medium Image, No Image, Small Image,and Zoom Image. |
Access the Mobile Order Capture Defaults page.
Note. The PDA Options group box is no longer in use.
Laptop Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer. Options are All Attachments, Custom Size, and No Attachments. If you select Custom Size, enter the maximum attachment size that is allowed as well. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the laptop computer. The system delivers only attachments that are less than the specified size. |
Access the Mobile Field Service Options page.
Laptop Options and PDA Options
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer and the personal digital assistant (PDA). Options are All Attachments, Custom Size, and No Attachments. If you select Custom Size, enter the maximum attachment size that is allowed as well. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the laptop computer and the PDA. The system delivers only attachments that are less than the specified size. |
This section discusses how to set up out-of-date detection.
The four CDM components (Company, Person, Worker, and Site) in the mobile applications use the Basic Data table to accommodate out-of-date detection. To set up for out-of-date detection, you must enable basic data for the company, person, worker, and site roles on the Role Type page.
Page Name |
Object Name |
Navigation |
Usage |
RBM_DD_ROLE |
Set Up CRM, Common Definitions, Customer, Role Type |
Set up out-of-date detection for role types. |
Select the Enabled for Basic Data option, which enables the maintenance of the Basic Data table and out-of-date detection for mobile customer applications.
See Also
Working with the Relationship Viewer
Interactions and 360-Degree Views
Enterprise PeopleTools PeopleBook: PeopleSoft Mobile Agent
This section discusses how to enable basic data processing.
Page Name |
Object Name |
Navigation |
Usage |
BO_INSTALLATION |
Set Up CRM, Common Definitions, Customer, Customer Installation Options, Customer Data Management System Options |
Enable basic data processing for mobile applications. |
Access the Customer Data Management System Options page.
Process Basic Data Summary |
Select this check box if PeopleSoft mobile applications are in use. This feature updates basic data tables and overrides the setting for roles. |
See Also
Defining Customer Data Management System Options