You are on page 1of 2

Guardrails for developing mobile applications 1. Use controls supported by Pega Mobile.

The Pega-Mobile RuleSet contains a decision table, pyMobileControlMapping, that maps over 100 commonly used controls to mobile versions of those controls. For e xample, the pxTextInput control is mapped to pxTextInputMobile. Do not use the m obile version of the controls. Instead, use the standard (or desktop) version of the control, and allow PRPC to perform the mapping to the mobile version for yo u. Supported controls include: o DynamicSelect with a Report Definition data source o PromptSelect for local list or prompt list o pxTextInput o pxTextArea o Any DateTime format o pxCheckbox o Autocomplete Two controls, pxGMapDirectionsMobile and pxGMapLocationMobile, are used in mobil e applications with no mapping required. If your application uses custom controls, edit the pyMobileControlMapping decisi on table to map your control to one of the listed mobile controls. For example, if you have a control called CustomAAADateTime, map it to pxDateTimeMobile, so t hat a date-time control renders on a mobile device. See How to configure section rules for a mobile device. 2. Use only layouts supported by Pega Mobile. Single Smart Layouts are fully supported. Double Smart Layouts are fully supported. On a phone device, the second column a ppears below the first column. Repeating Grids are supported with some considerations. o Read Only, Modal Dialog, Embedded Pane, and Expand Pane are fully suppor ted. o Rows can be added, deleted, edited, and selected for all modes except Re ad Only. Note that if user selects a row, then clicks Submit, the pySelected pro perty is set to 'true', allowing the item to be used in post-processing. Tabbed layouts are supported. The user switches between 'tabs' with a swiping mo tion on the device. See How to configure section rules for a mobile device. 3. Specialize your application for mobile devices only when necessary. In most cases, the desktop version of an application successfully generates and renders on a mobile device. Some features, however, are not yet optimized for us e on a mobile device. If your application uses features that are not yet support ed on mobile devices, create rules for the mobile version of your application in one of two ways: Create circumstanced versions of your rules for mobile devices. This method is e asier, but is viable only when the application has no other circumstancing requi rement. When you circumstance a section rule, use Save As to create the circumst anced version, and include property pyPortal.pyDesktopSubType and value Mobile. On the Pages & Classes tab, add the pyPortal page, and class Data-Portal. You ca n ignore the performance warning message. Create specialized mobile versions of rules, and save them into a RuleSet of the same name and version, but one with an _mobile suffix. Specialization allows yo u to create mobile versions of your RuleSets to use PRPC features that are optim ized for use on mobile devices. When the application is accessed from a mobile d evice, PRPC automatically uses the version of a rule from the _mobile RuleSet, i f it exists. See How to create a specialized RuleSet for mobile devices. 4. Observe mobile harness restrictions. Buttons are not supported, with the exception of the Save button on assignments which you configure on the appropriate Perform harness. Control the Read Only state of a harness using the Launch Harness Read Only para meter. Titles in the container property panel are not supported. Add titles to a harnes

s using the header cells in a container. In the Cell Property Value field, you c an specify a property reference or enter a text string for the title. See How to configure section rules for a mobile device. 5. Access Navigation rules in 3 possible locations. Navigation rules control the application menu, toolbars, and actions. Create nav igation rules as Type Mobile. Navigation rules are defined in: Portal rule fields: o Home Navigation Rule - Controls content of main panel on tablet at initi al load of the portal. o Main Navigation Rule - Defines navigation options that typically display on the left on a tablet, and full screen on a phone. o Toolbar Navigation Rule - Provides toolbar navigation options. Harness rule: Display Options tab - Supplemental Toolbar Navigation Rule field. Specify a navigation rule to render as a supplemental toolbar menu.