This document provides an overview and instructions for implementing and customizing Pivotal CRM for the iPad application. It discusses the features and architecture of the app, server-side requirements, customization options like forms, navigation, and security permissions. It also addresses troubleshooting, known issues, and a Q&A section.

1. PIVOTAL CRM for iPad
Manal Samaan
Technical Trainer

2. Agenda
• Pivotal CRM for iPad Overview
- Features
- Solution Architecture
- Server Side Requirements
- Customization
• Q/A
2

3. Overview

4. Pivotal CRM for iPad Overview
• Is a new mobile option from Pivotal
– Allows users to access Pivotal data from anywhere
• Has a client and server component
– Pivotal CRM for iPad App
– Pivotal Device Server
4

5. Pivotal CRM for iPad Features
• Mobile access to CRM information
– Create and manage CRM information from anywhere
– Search capabilities
– Read-only offline support
• iPad Dashboard: charts, URLs, and SRLs
• Integration with other Apps - Skype
• Use of native features (GPS, camera, signature
capture)
• Customizable using Pivotal Toolkit
– Flexible navigation and form layout

6. SERVER SIDE
REQUIREMENTS

7. Sever Component Deployment Requirement
• Server Machine
– Windows Server 2008 Service Pack 2 / R2 / R2 SP1
– Microsoft Internet Information Services 7.0 or above
– .NET 4.0
• Pivotal CRM System
– SP10
• Pivotal Business Server 6.0.10 Hot Fix 1
• Pivotal Toolkit 6.0.10 Hot Fix 2
– Any Pivotal CRM application (CMS, FS or PCM)

8. Client Component Deployment Requirement
• iPad
– iOS 5.0.1 and above
– iPad 2 or 3 is recommended for better performance
• App download from the on App Store
• A one time download

9. SOLUTION ARCHITECTURE

10. Three-tier Architecture
• Data Layer - Includes the databases
– The Business Module contains the metadata for the iPad
application
• Active Forms
• SRLs
• Business Objects / Navigation
• Security permissions
• Business Logic Layer
– Pivotal Device Server
– Pivotal Business Server
• Presentation Layer
– Device Client - based on Appcelerator’s Titanium Framework

11. Deployment
Components
in the DMZ
Open Ports 80/434

12. Deployment
within the private
network
Device Server on same
network as PBS
VPN from iPad is
required

13. DEPLOYMENT

14. Installing The Device Server
• Provide:
– Pivotal Business Server URL
– Pivotal system name

15. Editing the Web.config File
• Location:
– Drive:Program FilesCDC SoftwarePivotal
CRMDeviceServer
• Settings:
– ServerUrl: Pivotal Business Server URL
– CRMSystemName: Pivotal CRM system name
– UserDomain: used when the user logs on without providing a
domain name
– File value: log file location
– Level value: logging level

16. Editing the Web.config File cont’d
• MaxSearchRecordCount:
– recommended <= 500 (note: currently is set to
2000, set to 500)
• CacheObjectExpiration:
– expiration time of the meta data used by the server
– Should be equal to Idle Time-out application pool
setting for consistent object cache expiration
– Minimum is 15 min
• maxRequestLength

17. Supporting Multiple Pivotal Systems
• Create a new folder for the second Pivotal Device
Server
• Copy all the contents - including sub-directories
• Grant Network Service Id (read, write) permission to
the App_Data folder

18. Supporting Multiple Pivotal Systems cont’d
• Create a new application pool
– Verify that the .Net Framework version is 4.0.30319

19. Supporting Multiple Pivotal Systems cont’d
• Add a new application on the Default Web Site
– provide the alias for the new Pivotal Device Server
• used in Device Client to connect to this application
http://<server IP address>/<deviceserver2>
– set the physical path to the new Device Server folder
– create a COM+ partition for the Pivotal system
– set the ServerURL and CRMSystemName parameters
in the web.config file

20. TROUBLSHOOTING

21. Troubleshooting the Pivotal Device Server
• Verify that the IIS server is functional and reachable
• Verify that the following URL is reachable and
displays a

22. Troubleshooting the Pivotal Device Server cont’d
• Error Code 500: verify that
– the Pivotal Device Server can reach the Pivotal Business
Server
– Pivotal Business Server is running

23. CUSTOMIZING PIVOTAL
CRM TO SUPPORT THE IPAD
APP

24. Customizable Objects
• Forms: Using the Active From Designer
• Navigation bar: Business Objects
• Dashboard: Portal categories and Portal Items
(queries, Graphs and URLs)
• Server Tasks (App Sever Rules): can be associated
with an Active Form
• Setting security permissions

25. iPad User Interface
Search Panel Active Form
Tab Group

26. Viewing Customization Changes on the iPad
• Stop the Pivotal Business Server
• Recycle the Device Server IIS application pool
• Do one of the following to get the latest meta data:
– ACC
– UFO
– Disable Caching of Business Module:
• Logout of App and log back in

27. Creating Active Forms
• Active Forms are design to include
– Tabs
• One Anchored Tab: appears as a header regardless of scrolling
• contain Segments
– Segments
• Primary: fields from the base table
• Secondary: references a linked by a Foreign Key to the form phase
table
• Segments can include:
– Fields
– Static text
– Disconnected fields
– Icons for a secondary

28. Creating iPad Navigation Elements
• Business Objects are used as navigation elements
• Appear as a button in the application tab group
menu
• Clicking a Business Object from the iPad displays
an associated Active Form
• One Business Object per table
– Needed only for forms accessible from the application
tab group menu
• An Icon must be specified

29. iPad Business Objects
• The selected Business Object appears
in the upper-left corner of the Active
Form title
– Reveals a Search Results List

30. Sample Business Object

31. Setting Searches for a Business Object
• Controlled by security
permissions
• Open parameter queries
are not supported
– Only available for Foreign
Key filters on forms

32. Search Results Lists
• The first two visible non-binary
columns are shown in the iPad
search panel
• The first field with data type
DeviceIcon displays an image
• All other non-binary columns are
not visible, but content is used
when filtering
• Any tables referenced in the
SRL, including formulas, must have
at least Read access.

33. Creating a search Results List

34. Customizing the Dashboard
• One Portal Category defines all the
URLs, Queries, and Graphs
– Controlled by security on Portal Items
• Graphs and URLs are displayed in the top half of the
dashboard
• Queries are displayed in the bottom half
• Unpredictable which Dashboard is shown when more
than one is available to a user.

35. Creating a New Portal Category

36. Creating a Portal Item - Graph
The token in the description determines the item location on
the Dashboard

37. Setting Security Permissions
• The Device Client connection type provided in
Pivotal Toolkit 6.0.10 is used to set all application
permissions except:
– View filters - LAN connection type
– Server Task - Client connection type
Note: Reports and Letter Express are currently not
supported.

38. Setting Security Permissions cont’d
• At least Read permission on the Tables
• Visible permissions for the Business Object
• Grant Visible, Default, and Scriptable permissions
for the SRL
• Grant Default and Scriptable permissions for the
Active Form
• If no read access assigned to the table, then the
Active Form & Business Object will not be displayed
in the application
– Check the Device Server log for an error

39. Setting Security Permissions cont’d
• Visible and Scriptable for queries
– Default: the query executed when a Business Object is clicked

40. Setting Security Permissions cont’d
• Portal Items from one Category should be made
Visible

41. Knows Issues
• DE28219: When a new record is added or an existing
record is edited, the changes are not reflected
immediately in the searches
• DE28321 The Icon token does not get applied for
Foreign Key and Attachment fields
• DE28344 The iPad application sometimes crashes
when an incorrect URL is specified in a Webview or
URL field.
• DE28345 The iPad client displays the hidden fields.
Workaround: Add the hidden field to a hidden segment
instead.