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.
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 for mobile applications:
Implements security.
Filters the data that is downloaded to the mobile device.
Depending on the business objects, PeopleSoft Enterprise Customer Relationship Management (PeopleSoft Enterprise CRM) mobile applications utilize the distribution rules and spider out methods to distribute data from the database to the mobile device.
Defining data distribution rules creates structured query language statements that run during synchronization to select the data set 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 data set may differ depending on the mobile device. |
|
The result of spidering are rows of data can be required for the mobile device in addition to those 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, but it also retrieves Ontario because Ontario is already present on the mobile device. |
Objects |
|
|
|
Consumer (RDM_PERSON_CI) |
|
|
Relationship Component (BO_REL_MOBILE)
The Relationship component sources the data in the various components' relationship viewers.
Using distribution 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 amount 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. There is an option in the mobile installation options to spider out from the customer components. This will enable automatic spider-out of relationships one level deep from each customer. This is one mechanism to supplement or replace data distribution rules.
See Also
PeopleTools PeopleBook: PeopleSoft Enterprise Components
PeopleTools PeopleBook: PeopleTools Mobile Agent
PeopleTools PeopleBook: PeopleCode Reference
In PeopleSoft Enterprise CRM, you can define the options for using the PeopleSoft Enterprise CRM Customer Data Model for the mobile application. The PeopleSoft Enterprise CRM Customer Data Model 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 the data distribution methods that are used to display the Relationship Viewer and the 360–Degree View on mobile devices. |
Access the Mobile Customer Option page.
Default SetID |
Filters the customer data. |
Show Relationship Viewer |
Select this check box to display the Relationship Viewer on mobile devices. This field will not be enabled if the corresponding option in the Business Object Model System Options is not checked. |
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 check this box, there may be a slight decrease in system performance. |
|
Show 360 Degree View |
Select this check box to display the 360–Degree View on mobile devices. This field will not be enabled if the corresponding option in the Business Object Model System Options is not checked. |
Bill To Customer |
Select this check box if you want customers created on the mobile device to be Bill To customers. Addresses created for a Bill To customer will automatically be marked as a Bill To Address and the primary address will automatically be marked as a Primary Bill To Address. Bill To Customer means that invoices can be sent to the customer or site. |
Ship To Customer |
Select this check box if you want customers created on the mobile device to be Ship To customers. It should be noted that addresses created for such a Ship To customer will automatically be marked as a Ship To Address and the primary address will automatically be marked as a Primary Ship To Address. Ship To Customer means that invoices can be shipped to the customer or site. |
Sold To Customer |
Select this check box if you want customers created on the mobile device to be Sold To customers. It should be noted that addresses created for such a Sold To customer will automatically be marked as a Sold To Address and the primary address will automatically be marked as a Primary Sold To Address. Sold To Customer means that invoices can be sold to the customer or site. |
Address Purpose Type |
These are the defaults for the address contact methods that are created on the device. Delivered values are: Physical Location, Business, Campus, Dormitory, Home, Legal, Mailing, and Other. |
Email Purpose Type |
These are the defaults for the email contact method. Delivered values are: Business, Campus, Dorm, Home and Other. |
Phone Purpose Type |
These are the defaults for the phone contact method. Delivered values are: Business, Cell, Default, FAX, Home, Telex, Campus, Dormitory, main and Other. |
Person Configuration |
Select options to set default actions in the Person component. These actions determine how you view the content in the person component. Delivered options include: When User Clicks "Add" Button
View for Persons with Multiple Roles
|
Role Type ID |
Displays the identification code associated with the business object role type. When adding a new role type, the system automatically assigns a value using automatic numbering functionality. |
Role |
Displays the role for which you want to view relationships. |
Business Object Name Type |
Displays the business object name type for which this role type is valid. |
Relationship View Name |
Select the relationship view that you want to associate with the role |
During a synchronization, as transactions are encountered this option will control whether the sync process will spider out to the relationships. Note. If you select this option and also select Spider out to Customer, all customer data will be moved to the mobile device which may impact the performance (depending on the volume of customer data in the system). |
|
360 Degree Tree Name |
The tree displays all activities and interactions for the company or contact. Plus, it can 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. |
360 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
Before you use the mobile product, you need to set up the following options:
Type of attachments.
Custom size of the attachments (if you want to specify the size of some attachments).
Size of the 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 mobile sales attachment rules. |
|
Mobile Product Defaults |
MOC_OPTIONS_PG |
Set Up CRM, Install, Mobile, Mobile Product Options |
Define mobile product attachment rules. |
Mobile Order Capture Defaults |
MOC_OC_OPTIONS_PG |
Set Up CRM, Install, Mobile, Mobile Order Capture Options |
Define mobile order capture attachment rules. |
Mobile Field Service Options |
RF_MOB_SYNC_OPT |
Set Up CRM, Install, Mobile, Mobile Field Service Options |
Define mobile field service attachment rules. |
Access the Attachment page.
Select the synchronization options for attachments to be passed down from the database to the mobile device. Valid values are: All, Size Up To, and None. When you select Size Up To, the system enables you to select attachments up to a certain size. |
|
Select the synchronization options for attachments to be passed down from the database to the mobile device. Valid values are: All, Size Up To, and None. When you select Size Up To, the system enables you to select attachments up to a certain size. |
Access the Mobile Product Defaults page.
Laptop Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer. Valid values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
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. The default is Medium Image. |
PDA Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the PDA. Values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the PDA. The system will only deliver 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 PDA. Valid values are: Large Image, Medium Image, No Image, Small Image,and Zoom Image. The default is Medium Image. |
Access the Mobile Order Capture Defaults page.
Laptop Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer. Valid values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
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. |
PDA Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the PDA. Values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the PDA. The system will only deliver attachments that are less than the specified size. |
Access the Field Service Options page.
Laptop Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the laptop computer. Valid values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
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. |
PDA Settings
Type |
Select the synchronization option for attachments that are to be passed down from the database to the PDA. Values are: All Attachments, Custom Size and No Attachments. When you select Custom Size, the system enables you to select attachments that are less than a certain size. |
Size (bytes) |
Specify the size (in bytes) of the attachments that you want to pass down from the database to the PDA. The system will only deliver attachments that are less than the specified size. |
The four components (Company, Contact, Consumer, Site) in the PeopleSoft Enterprise CRM mobile applications utilize the Basic table to accommodate out-of-date detection. In order to set up for out-of-date detection, you must enable basic data for the company, contact, individual consumer, 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 |
Define the role type for the components and to enable out-of-date detection. |
Enabled for Basic Data |
Select to enable maintenance of the Basic Data table. This also enables out-of-date detection for mobile customer applications. |
See Also
PeopleTools PeopleBook: PeopleSoft Mobile Agent
Working with the Relationship Viewer
Interactions and 360-Degree Views