Salesforce1 Mobile App Developer Guide

(1)

Salesforce1 Mobile App Developer Guide

Version 5, June 2015

Written by Dianne Siebold Samantha Ready Michelle Chapman-Thurber With contributions by Michael Alderete Cliff Armstrong Jay Hurst Dean Moses Tammy Rahn Samantha Reynard Jim Sinai Quinton Wall Emily Wilska

(2)

This book introduces you to both the declarative (point-and-click) and the

programmatic (code-based) features of Salesforce1. To help you get familiar with the different pieces that make up the Salesforce1 Platform, and to show you how you can optimize existing features such as Visualforce pages and quick actions for the Salesforce1 mobile experience, this book walks you through the process of enhancing an existing organization to make it mobile-ready.

Salesforce1 Mobile App Developer Guide

©_{Copyright 2000–2015 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of} salesforce.com, inc., as are other names and marks. Other marks appearing herein may be trademarks of their respective owners.

Various trademarks held by their respective owners.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior consent

(3)

SALESFORCE1 ADMINISTRATION

. . . 17

Chapter 4: Configuring Salesforce1. . . 17

Defining Which Users Can Use Salesforce1 . . . 18

About Notifications. . . 19

Try It Out: Enable Notifications. . . 20

About Offline Access in Salesforce1 . . . 20

Chapter 5: Customizing the Salesforce1 Navigation Menu . . . 23

About the Salesforce1 Navigation Menu. . . 24

Try It Out: Configuring the Salesforce1 Navigation Menu. . . 25

Test Out the Salesforce1 Navigation Menu . . . 26

How the Salesforce1 Navigation Menu Works. . . 27

Chapter 6: Customizing How Your Data Shows Up in Salesforce1. . . 29

(4)

Rethinking Your Page Layouts for Mobile . . . 31

Try It Out: Create a Custom Page Layout for the Mobile Technicians Profile. . . 33

Test the Page Layout. . . 35

Tips for Optimizing Page Layouts for Mobile. . . 36

About Compact Layouts. . . 37

Try It Out: Create a Compact Layout . . . 38

Test the Compact Layout. . . 40

Tell Me More: Compact Layouts. . . 41

Chapter 7: Using Actions in Salesforce1. . . 43

About Quick Actions . . . 44

Action Categories . . . 46

Point and Click Your Way to Actions. . . 47

Try It Out: Create an Object-Specific Action. . . 47

Try It Out: Assign the Action to the Account Page Layout. . . 48

About Global Quick Actions. . . 49

Tell Me More: Actions. . . 50

About Action Layouts. . . 50

Try It Out: Customize an Object-Specific Action Layout . . . 52

Test Out the Object-Specific Quick Action. . . 53

About Predefined Values in Actions. . . 55

Try It Out: Set a Predefined Field Value on an Action. . . 56

Test the Predefined Value. . . 57

About Custom Actions. . . 58

Chapter 8: Guidelines and Best Practices for Administrators. . . 61

Action Guidelines and Best Practices. . . 62

Custom Icon Guidelines and Best Practices. . . 62

DEVELOPING FOR SALESFORCE1

. . . 65

Chapter 9: Welcome to Salesforce1 Platform Development. . . 65

Our Scenario . . . 66

Who This Part is For. . . 66

When to Use Declarative vs. Programmatic Tools to Create Salesforce1 Apps. . . 67

When to Use the Salesforce1 Platform vs. Creating Custom Apps. . . 68

(5)

Salesforce1 Platform Development Process. . . 69

Development Prerequisites. . . 70

Change the System Administrator Page Layout Assignment. . . 70

Chapter 10: Designing Mobile-First User Interfaces. . . 73

Design for Mobile. . . 74

Keep Navigation Simple. . . 74

Put Important Information at the Top. . . 74

Minimize the Number of Fields. . . 75

Use Field Defaults. . . 76

Minimize User Interface Text. . . 76

Tap Target Size. . . 77

Chapter 11: Extending Salesforce1 with Visualforce Pages. . . 79

Try It Out: Create a Visualforce Page. . . 80

Create a New Tab . . . 83

Add the Tab to the Navigation Menu. . . 84

Test Out the Visualforce Page . . . 85

Tell Me More: Where Visualforce Pages Can Appear in Salesforce1. . . 87

Tell Me More: About the Code. . . 89

Chapter 12: Adding Functionality with Visualforce Custom Actions. . . 93

Custom Actions Scenario . . . 94

Try It Out: Create a Visualforce Custom Action. . . 94

Add the Visualforce Custom Action to the Page Layout. . . 95

Test Out the Visualforce Custom Action. . . 96

Tell Me More: About the Code. . . 98

Chapter 13: Integrating Your Web Applications in Salesforce1 with Force.com Canvas . . . 105

About Force.com Canvas . . . 106

Extending Salesforce1 with Canvas Custom Actions. . . 106

Try It Out: Clone the Shipify Web Application. . . 107

Create the Shipify Canvas App. . . 108

Configure Who Can Access the Shipify Canvas App. . . 110

Configure the Heroku Environment Variables. . . 111

(6)

Add the Action to the Global Publisher Layout. . . 112

Test Out the Canvas Custom Action. . . 113

Tell Me More: Get Context in your Canvas App. . . 115

Extending Salesforce1 with Canvas Apps in the Feed. . . 120

Try It Out: Clone the DeliveryTrakr Web Application. . . 120

Create the DeliveryTrakr Canvas App. . . 122

Configure Who Can Access the DeliveryTrakr Canvas App. . . 124

Configure the Heroku Environment Variables. . . 124

Create a Global Action. . . 126

Add the Action to the Global Publisher Layout. . . 127

Test Out the DeliveryTrakr Canvas App. . . 128

Tell Me More: About the Code to Create Feed Items. . . 133

Chapter 14: Calling Quick Actions from the API. . . 135

Try It Out: Create an Invoice Action. . . 136

Add the Code to Call the Action. . . 137

Test Out Calling the Action from the API. . . 139

Tell Me More: Quick Actions and the REST API. . . 142

Chapter 15: Extending the User Interface with Lightning Pages. . . 153

What Is a Lightning Page?. . . 154

About Lightning Pages . . . 154

Lightning Pages: The Big Picture. . . 156

Before We Begin: Download the Deliveries App. . . 157

Creating a Lightning Page . . . 157

Try It Out: Create a Lightning Page. . . 158

Assigning Quick Actions to A Lightning Page. . . 159

Try It Out: Add a Quick Action to Your Lightning Page. . . 160

Deploying a Lightning Page. . . 161

Try It Out: Deploy a Lightning Page. . . 161

About Lightning Page Tabs. . . 162

Try It Out: Create a Lightning Page Tab. . . 162

Tell Me More: Lightning Page Tabs. . . 163

Making Your Lightning Page Available in Salesforce1. . . 164

Try It Out: Add a Lightning Page to the Salesforce1 Navigation Menu. . . 164

Test the Lightning Page in Salesforce1. . . 165

(7)

Tell Me More: Lightning Pages. . . 166

Chapter 16: Development Guidelines and Best Practices. . . 169

When to Use the Navigation Menu or the Action Bar. . . 170

Visualforce Guidelines and Best Practices . . . 172

Sharing Visualforce Pages Between Mobile and Desktop . . . 172

Excluding Visualforce Pages from Mobile or Desktop. . . 173

Choosing an Architecture for Visualforce Pages in Salesforce1. . . 173

Standard Visualforce Pages . . . 173

Mixed Visualforce and HTML. . . 175

JavaScript Remoting and Static HTML. . . 177

Visualforce Components and Features to Avoid in Salesforce1. . . 183

Unsupported Visualforce Components. . . 184

Choosing an Effective Page Layout . . . 184

User Input and Interaction. . . 188

Managing Navigation . . . 192

Navigation with the sforce.one Object. . . 194

How sforce.one Handles API Versions . . . 197

Visual Design Considerations. . . 201

Using Visualforce Pages as Custom Actions. . . 203

Creating Visualforce Pages That Work in Mobile and Desktop. . . 204

Performance Tuning for Visualforce Pages. . . 205

Force.com Canvas Guidelines and Best Practices. . . 206

Canvas Apps in the Chatter Publisher and Salesforce1 Action Bar. . . 206

Canvas Apps in the Feed . . . 208

Canvas Apps Context. . . 208

Custom Icons for Canvas Apps . . . 209

Chapter 17: Learning More. . . 211

INDEX

. . . 213

(8)

(9)

CHAPTER 1 Introduction

Mobile has become the new normal for staying connected in both our personal and professional lives. More and more, we’re living our lives In this chapter ...

• Introducing the

Salesforce1 Platform connected to the Internet, but instead of sitting at a desk, we’re connecting_{on planes, in cabs, in between meetings, in hotels, or even in line for coffee.} • Salesforce1 Platform

Features

We follow friends, update status feeds, research local businesses, collaborate with colleagues, email suppliers, and much more—all tasks increasingly performed on the go.

• Introducing the

Salesforce1 Apps _{And at the same time, every company is working harder and faster to} innovate and stay ahead of the competition. The successful businesses of • Getting Around in

Salesforce1 _{the future must embrace this mobile-first world and the freedom this} • What about the

Other Mobile Apps?

mobility provides to get things done, regardless of where you are and what you’re doing.

Salesforce1 solves the problems of lagging innovation and a lack of mobile specialists with a revolutionary approach to app development for the social and mobile-first world. Salesforce1 delivers breakthrough productivity for all users because it puts the customer—employees, partners, consumers, and devices—at the center of everything.

The result is a fast, connected mobile solution with the potential to be as disruptive as Software as a Service. It’s time to build the future today!

(10)

Introducing the Salesforce1 Platform

Salesforce1 is a mobile app development platform for everyone. It gives ISVs, developers, administrators, and every user the freedom to innovate.

This approach to unlocking mobile app development for organizations is built for today’s needs: mobile and social solutions delivered in days or weeks. Apps are driven by metadata and intelligently provide context to the user experience. These apps deliver information-based mobile device features: addresses can be plotted on maps, phone numbers can be dialed with a simple tap, feed-centric workflows can be created, and much more.

Business users and administrators can develop apps with clicks, not code, complete with powerful workflow rules, approval processes, and dynamic user interfaces. Unlike other solutions where business users often create independent applications in which IT has little visibility into their security or reliability, Salesforce1 gives administrators the tools to centrally manage apps without limiting the business’s need to innovate. Designed for scale with open APIs for extensibility and integration, and powerful developer tools, there’s no limit to what developers and ISVs can build on the platform. Salesforce1’s flexible development models let every administrator or developer create custom apps that are supported by mobile back-end services and a unique, yet familiar, mobile user experience. ISVs developing on the Salesforce1 Platform can develop apps that take advantage of advanced packaging and version management controls, complete enterprise marketplace capabilities with the AppExchange, and feed-first discovery of their apps within the Salesforce1 Platform.

Salesforce1 Platform Features

The Salesforce1 Platform brings together Force.com, Heroku, and ExactTarget Fuel into one incredibly powerful family of social, mobile, and cloud services—all built API first.

The Salesforce1 Platform delivers:

Social Data

The ability to share, follow, collaborate, and take business actions directly on data within Salesforce1 is at the core of the platform. Users can follow records and data with a single tap. They can be notified of changes in real time, and collaborate directly within the record feed. This feed-based approach to working lets users focus on what’s most important to them.

By treating data as social and as an important participant in business, Salesforce1 allows data to share updates, trigger workflows, and be part of the collaboration process with workers, teams, partners, and Chapter 1 Introduction

(11)

customers. The result is an unparalleled opportunity to create new business apps and processes for business productivity.

Declarative and Programmatic Development

IT departments have struggled to keep pace with the level of change required for businesses to remain competitive. Too often, IT is resource-constrained because they must manage existing on-premises systems while at the same time recruit and retain professional developers—especially those with mobile application development experience.

Salesforce1 solves this problem by providing intuitive drag-and-drop tools for storing and working with data, defining cloud-based logic with workflows, creating approval processes and formulas, and creating mobile-ready apps.

Professional developers can use the most popular open-source languages, tools, and standards to build completely custom apps and user interfaces. Unlike other platforms, Salesforce1 delivers a unique experience where developers and administrators create apps on the same platform, eliminating the effort required to build complicated integration solutions.

Action-Based App Model

Salesforce1 puts the customer at the center of the development process. Rather than require complicated development cycles, apps can be declared through actions: create an order, set a delivery date, select a route, and so on. Administrators can define default values for actions to streamline apps down to the click of a mouse or a swipe of the finger.

Actions defined via the desktop are instantly available in context-sensitive menus on mobile devices. And, for developers building integrations with Salesforce1, actions are automatically enabled with RESTful endpoints capable of accepting either XML or JSON data envelopes.

Connect to Everything with Open APIs

Salesforce provides the flexibility to create apps that connect to everything using efficient and scalable APIs that perform over 1.3 billion transactions a day. Every object or data entity is instantly REST-enabled. Our APIs include bulk APIs for data loading, social APIs for ubiquitous collaboration anywhere, cutting-edge streaming APIs to support push notification integrations, and metadata APIs that describe every aspect of your app and business such as permissions, data access policies, field types, and user experience.

(12)

Introducing the Salesforce1 Apps

The Salesforce1 apps are Salesforce on the go! These enterprise-class mobile apps give your users real-time access to the same information that they see in the office, but organized for getting work done in those precioius free moments when they’re between customer meetings, waiting for a flight...even when they’re in line for coffee.

You can get Salesforce1 in different ways:

• As a downloadable app from the App Store and Google Play™_.

• As a mobile browser app that runs in supported mobile browsers. This option doesn’t require anything to be installed.

Supported Devices

The way users access Salesforce1 depends on whether they are using one of the downloadable apps or the mobile browser app.

Supported Mobile Browser Supported Mobile OS Supported Devices Salesforce1 App Not applicable iOS 8 or later

iPhone 5 or later models iPad 4 or later models Downloadable app for

iOS, v7.3 or later

iPad mini 2 or later models Apple Watch (push notifications only)

Not applicable Android 4.2 or later

Android phones Downloadable app for

Android, v7.3 or later

Apple Safari Good Access iOS 8 or later

iPhone 5 or later models iPad 4 or later models iPad mini 2 or later models Mobile browser app

Google Chrome Good Access Android 4.2 or later Android phones Android tablets Microsoft Internet Explorer 11 Windows 8.1 Update

Nokia Lumia 1020 and HTC 8X phones

(13)

Supported Mobile Browser Supported Mobile OS Supported Devices Salesforce1 App

Microsoft Surface 2 and Surface Pro 3 tablets

BlackBerry Browser BlackBerry OS 10.2 or later BlackBerry Z10 phones BlackBerry Browser BlackBerry OS 10.2.1.3175 or later BlackBerry Z30 phones

In this book, we’ll be working exclusively with the downloadable apps. See “Enable the Salesforce1 Mobile Browser App” in the Salesforce Help for information on the Salesforce1 mobile browser app.

Getting Around in Salesforce1

Let’s take a tour of the Salesforce1 app.

When users log in to Salesforce1, the first thing they see is a landing page. The first item in the Salesforce1 navigation menu becomes a users’ landing page by default. If your organization has Chatter enabled, and you haven’t customized the Salesforce1 navigation menu to change the first item in the menu to something else, the user’s Feed will be their landing page.

The Feed

The Chatter feed shows users their updates, updates to records and people they follow, and updates in groups they follow. Tapping a feed item displays all of the item’s details. Pulling down on the feed reveals the search bar (1), sort and filter options (2), the feeds drop-down menu (3), and feed items (4).

(14)

From the feed, record pages, and from elsewhere in Salesforce1, users access actions from the action bar.

The Action Bar and Menu

Depending on which feed or record page users are viewing, they see different actions in the action bar and action menu. From the feed, for example, they see a set of global actions. From a record page, however, they see a mix of productivity actions, standard and custom buttons, standard Chatter actions such as Post and File, and global and object-specific actions that are assigned to the layout for that record type. Users can tap from the action bar to open the action menu, which contains the full set of actions that are available for the object.

(15)

We’ll go over creating and customizing actions in Using Actions in Salesforce1 on page 43.

Salesforce1 Navigation Menu

Anywhere users see in Salesforce1, they can tap it to access the navigation menu.

What your users see in the menu is determined by how you, as the administrator, have configured it, what’s available in your organization, and what users have access to, based on their user permissions and profile.

(16)

1. Search box

2. Menu items—any items you place above the Smart Search Items element when you customize the navigation menu

3. Smart Search Items—includes a set of recently-searched objects in the Recent section and a larger set of supported objects under the More link

4. Apps section—contains any items you place below the Smart Search Items element

From the navigation menu, users can access the feed, objects, apps, tasks, notes, and any other item you’ve added to the menu. We’ll go over the components of the navigation menu in more detail in About the Salesforce1 Navigation Menu on page 24. But for now, let’s take a look at records.

The Record View

The record view is made up of the record feed, detail, and related information pages, which your users can swipe left and right to see. If your organization doesn’t have Chatter enabled, the record view only includes the detail and related information pages.

(17)

At the top of each record page is the record highlights area. The icon for standard objects is predefined in Salesforce, and you can select the icon for a custom object using the custom object’s tab style.

You can customize the fields displayed in the record highlights section by using compact layouts, which we’ll look at in About Compact Layouts on page 37.

1. Back arrow—returns the user to the previous page

2. Record highlights—displays the first four fields that are assigned to the compact layout for the object

(18)

What else do I need to know?

From the top of most pages, users can access their notifications by tapping .

Users can create a new record by tapping New at the top of recent object pages, search pages, and related list pages. They can also create and update records by using actions, if create actions have been set up in the organization.

What about the Other Mobile Apps?

Wondering how the Salesforce1 app relates to the other Salesforce mobile products?

• SalesforceA gives administrators mobile access to essential organization management tasks. Use it to edit, unlock, freeze, and deactivate user accounts, reset passwords, and assign permission sets. • The Salesforce mobile offerings still include Salesforce Classic. Salesforce Classic users might find that

Salesforce1 is a better fit for their needs, but Salesforce Classic remains the best option if you need to create and edit in offline mode.

For more detailed information about the full suite of Salesforce mobile apps, see “Salesforce Mobile Products Overview” in the Salesforce Help.

(19)

CHAPTER 2 About This Book

This book introduces you to both the declarative (point-and-click) and the programmatic (code-based) features of Salesforce1.

In this chapter ... • Who Is This Book

For? To help you get familiar with the different pieces that make up the Salesforce1 Platform, and to show you how you can optimize existing • How Do I Begin?

features—such as Visualforce pages and actions—for the Salesforce1 • About the Sample

Scenario mobile experience, this book walks you through the process of enhancing_{an existing organization to make it mobile-ready and mobile-friendly.} • About Acme Wireless

(20)

Who Is This Book For?

This book is broken up into two major sections. The first, Salesforce1 Administration, is aimed at administrators, and takes you through the declarative Salesforce1 tools in Setup, where you can point-and-click your way through getting your organization ready for the Salesforce1 mobile experience. This includes how to optimize your page layouts for mobile, customize the Salesforce1 navigation menu, create actions, and set up mobile notifications.

The second section, Developing for Salesforce1, is for advanced administrators and developers who are comfortable working with code. To fully understand its chapters, you should be familiar with Visualforce, XML, and canvas apps. We’ll walk through optimizing your Visualforce pages for mobile, creating custom actions, and creating custom app home pages for Salesforce1 using Lightning Pages.

Tip: Point-and-click admins, don’t let this deter you! We include code samples in most places, so even if you're not an experienced developer, you can still try the steps in each chapter and get a feeling for what can be done with Salesforce1.

How Do I Begin?

It’s up to you! You could begin by pointing-and-clicking your way through Configuring Salesforce1 and working all the way through Using Actions in Salesforce1. Then, put your developer hat on and create custom actions, or add canvas apps or Lightning Pages to further enhance your users’ Salesforce1 experience. If you’re a seasoned developer, you could jump into the deep end first with the Welcome to Salesforce1 Platform Development chapter.

About the Sample Scenario

The sample scenario for this book builds on the sample Warehouse data and code created in the Force.com Workbook. We took that data set and added some extras. We’ll use what was built there as a launching point, then add more to bring our sample organization into the mobile world of Salesforce1.

To do this, we’ll walk through the steps as if we were someone with administrator privileges at a make-believe company called Acme Wireless.

About Acme Wireless

Let’s find out a little bit about our fictional company. Chapter 2 About This Book

(21)

Acme Wireless is a large company that repairs devices such as mobile phones, tablets, and gaming consoles. The company has a number of brick-and-mortar locations where customers can drop off devices for repair. In addition, these storefronts sell device accessories like tablet covers, mobile phone covers, power cords, rechargers, and so on.

Acme Wireless maintains a central warehouse where all the repair parts and accessories are stored. The storefront locations order parts from the warehouse so that they can keep some inventory on hand. When they need a special part that’s not in stock, storefronts can special order it from the warehouse.

Acme Wireless is also expanding its repair services by doing on-site service. Mobile technicians will go to various customer locations to provide on-site service, including personal residences, hotels, small business offices, and conference centers.

How Acme Wireless Uses Salesforce

Acme Wireless uses Salesforce to track customers. These are often individuals who visit the storefronts, but can also be small businesses that have contracted with Acme Wireless for device support. Acme Wireless also uses Salesforce to track merchandise items and inventory in the warehouse, as well as to manage its billing and invoicing. They use two custom Web applications: one to track orders and process merchandise for shipment and one to track delivery of shipments to storefront locations.

Employees at Acme Wireless’s storefronts and the main office use Chatter internally to communicate about inventory levels, customer accounts, and orders.

How Acme Wireless Wants to Use the Salesforce1 App

Acme Wireless wants to use Salesforce1 to leverage its existing Salesforce organization and enable mobile technicians to access customer and merchandise data. The technicians should be able to see all their repair tickets for the day, locate a customer, look up inventory for any parts needed, order parts, check the status of orders, and so on.

Acme Wireless also wants to enable their truck drivers, delivering products from the warehouses to the storefronts, to track and update their deliveries for the day without having to use a separate app. They also want to give the warehouse workers the ability to track customer orders and process them for shipping. Acme Wireless also wants to enable Salesforce1 integration with legacy Web applications for order management.

(22)

(23)

CHAPTER 3 Setting Up Your Work Environment

To follow along with the exercises in this book, you’ll need a Salesforce account and a Developer Edition organization. If you don’t have a Developer In this chapter ...

• Install the Enhanced Warehouse Data Model

Edition organization, go to http://sforce.co/1om1gHf and sign up for a free Developer Edition account. Developer Edition is a

fully-functional version of Salesforce that you can use to develop Salesforce • Download the

Salesforce1 App

apps. Since it's free, there are limits on the amount of users, bandwidth, and storage you're allowed, but it includes all of the features in Salesforce. After that, you’ll need to install the enhanced Warehouse data model into your organization, and then download the Salesforce1 app, if you haven’t already.

(24)

Install the Enhanced Warehouse Data Model

To prepare your developer organization for the exercises in this book, you need to import the Warehouse data model. You might be familiar with the Warehouse app if you’ve gone through the tutorials in the Force.com Workbook. We took the Warehouse data from that guide and added a few extra things to it to help show you what Salesforce1 can do.

1. Go to www.salesforce.com and log in to Salesforce using your Developer Edition credentials. 2. Open a new browser tab or window, and navigate to

https://github.com/forcedotcom/Salesforce1-Dev-Guide-Setup-Package. Do this in the browser that you logged in to your developer organization with.

3. Open the README file.

4. Click the bit.ly link in the README file.

This is the installation link for the enhanced Warehouse data package. You should be taken directly into your development organization to the Package Installation Details page.

5. Click Continue. 6. Click Next. 7. Click Next. 8. Click Install.

9. Wait for the installation to finish.

10.From the Force.com app menu, select Warehouse. 11.Click the Data tab.

12.Click Create Data.

All right! The last step is to download the Salesforce1 app, then we’ll be ready to roll.

Download the Salesforce1 App

If you’ve already downloaded Salesforce1, you can skip this step.

1. Go to www.salesforce.com/mobile/, and download Salesforce1 for your device. You may be prompted to create a security PIN.

2. Open Salesforce1.

3. Log in using your developer organization credentials. Chapter 3 Setting Up Your Work Environment

(25)

SALESFORCE1 ADMINISTRATION

CHAPTER 4 Configuring Salesforce1

Salesforce1 is automatically enabled for all organizations, except those that have auto-enabling turned off.

In this chapter ... • Defining Which Users

Can Use Salesforce1 Salesforce1 doesn’t require much configuration at the beginning, but before your users start using Salesforce1, you should:

• About Notifications

1. Define which users can access the Salesforce1 mobile apps. • Try It Out: Enable

Notifications 2. Enable notifications. • About Offline Access

in Salesforce1 Since we’re in a developer organization, we don’t need to worry about_{enabling users. Review the information about that in the next section, then} we’ll get started by enabling notifications.

(26)

Defining Which Users Can Use Salesforce1

Important: This information is for reference only. We won’t be enabling users in this book, but this step is important when configuring Salesforce1 in your production organization.

Downloadable Apps

The Salesforce1 downloadable apps are connected apps. As a result, you can control the users who have access to the apps, as well as other security policies. By default, all users in your organization can log in to the Salesforce1 downloadable apps.

You can control security and access policies for each of the Salesforce1 downloadable apps, using settings components that are installed from the managed Salesforce1 connected apps package. These components need to be installed in Salesforce:

• Salesforce1 for Android • Salesforce1 for iOS

These components are automatically installed when one of your users installs a Salesforce1 downloadable app from the App Store or Google Play on a mobile device and authenticates with your organization by logging in to the mobile app.

Alternatively, you can manually install the Salesforce1 and Chatter Apps connected apps package so you can review and modify the default security and access settings before rolling out the Salesforce1 downloadable apps to your users.

When the Salesforce1 connected apps components are installed, they’re added to the Connected Apps page at Setup > Manage Apps > Connected Apps. Here, you can view and edit the settings for each of the apps, including controlling user access with profiles, permissions, and IP range restrictions. An error message is displayed if a restricted user attempts to log in to a Salesforce1 downloadable app.

Mobile Browser App

You can control whether users can access the Salesforce1 mobile browser app when they log in to Salesforce from a mobile browser. By default, the mobile browser app is turned on for your organization.

1. From Setup, click Mobile Administration > Salesforce1 > Settings.

2. Select Enable the Salesforce1 browser app to allow all users in your organization to access the app. Deselect this option to turn off access to the app.

3. Click Save.

(27)

When this option is turned on, users who log in to Salesforce from a supported mobile browser are automatically directed to the Salesforce1 interface. Logging in from an unsupported mobile browser loads the full Salesforce site.

Important: Use of the full Salesforce site in a mobile browser isn’t supported. While you can disable the mobile browser app for your organization—and individual users can turn off the app for themselves—regular use of the full site in a mobile browser isn’t recommended. Your users may experience problems that Salesforce Customer Support won’t investigate.

About Notifications

Notifications let your users know when certain events occur in Salesforce. For example, notifications let users know when they receive approval requests or when someone mentions them in Chatter. Two types of notifications can appear to Salesforce1 users.

In-app notifications

In-app notifications keep users aware of relevant activity while they’re using Salesforce1. By tapping , a user can view the 20 most recent notifications received within the last 90 days.

If Salesforce Communities is enabled for your organization, users see notifications from all of the communities they’re members of. To help users easily identify which community a notification came from, the community name is listed after the time stamp.

Push notifications

Push notifications are alerts that appear on a mobile device when a user has installed the Salesforce1 downloadable app but isn’t using it. These alerts can consist of text, icons, and sounds, depending on the device type. If an administrator enables push notifications for your organization, users can choose individually whether to receive push notifications on their devices.

Some notifications include text that your users enter in Salesforce. To ensure that sensitive information isn’t distributed through a third-party service without proper authorization, push notifications include minimal content (such as a user’s name) unless you enable full content in push notifications. For example, suppose an in-app notification reads: “Allison Wheeler mentioned you: @John Smith, heads-up! New sales strategy for Acme account.” By default, the equivalent push notification would be “Allison Wheeler mentioned you.” However, if you enabled full content in push notifications, this push notification would include the same (full) content as the in-app notification.

By enabling the option to include full content in push notifications, you’re agreeing on behalf of your company to the terms and conditions displayed when you save the setting. For details, see “Salesforce1 Mobile App Notifications” in the Salesforce Help.

As the first task in our fresh new development organization, let’s set up notifications for all the Acme Wireless mobile users.

(28)

Try It Out: Enable Notifications

We want all the Salesforce1 users in the Acme Wireless organization to receive notifications about events happening in the full Salesforce site, such as approval requests, or when they’re mentioned.

1. From Setup, click Salesforce1 Setup > Notification Options.

2. If they’re not already selected, select both Enable in-app notifications and Enable push notifications.

3. Click Save.

Note: Enabling in-app notifications is an all-or-nothing process. Either they’re on for everyone, or off for everyone. Mobile users can’t customize, enable, or disable in-app notifications for themselves. Now that we’ve addressed notifications, let’s look at offline access in Salesforce1.

About Offline Access in Salesforce1

Offline access is available for users in the Salesforce1 downloadable apps only. We won’t be working with Salesforce1’s offline mode in this book, but this information is important if you have any users who want to take advantage of it.

Salesforce1 can cache recently accessed data so it’s available when a user’s device is offline or unable to connect to Salesforce. Offline access is currently read-only, and is available in the Salesforce1 downloadable apps for iOS and Android devices.

Offline access is enabled the first time a user in your organization installs one of the Salesforce1 downloadable apps. You can manage this setting in Setup, from Salesforce1 Setup > Offline Cache. Cached data is encrypted and stored in a secure, persistent data store.

Available for Offline Use Salesforce1 Element

Yes Navigation Menu

Previous searches only Global Search

Previously viewed only Notifications

Previously viewed only Feeds, Groups, and People

Main page and mobile event records if previously view

Salesforce Today

(29)

Available for Offline Use Salesforce1 Element

Previously viewed only Salesforce Events

Yes (top five) Recent Objects

No Other Objects

Yes (30 most recent records) Record Details

Previously viewed only Related Records

Previously viewed only List Views

Only tasks from the first page of the My Tasks list (up to 10 tasks), and only if the list was previously viewed or after the user manually updates the cache Tasks

Yes (top five) Dashboards

No Approvals (submit, approve, or reject)

No Visualforce pages No Canvas Apps No Lightning Pages Yes Settings

Cached data is refreshed when a user switches to Salesforce1. If a user switches to another app, the user’s cached data is automatically refreshed if the existing data store is over one hour old.

Users can manually cache their data at any time—for example, before switching into airplane mode or entering an area with no service. From the Salesforce1 navigation menu, select Settings > Offline Cache > Cache Now.

(30)

Note: The cache is saved for two weeks. Users can clear the cache by logging out of the Salesforce1 app.

All right! We’ve addressed notifications and offline access, now let’s look at the Salesforce1 navigation menu.

(31)

CHAPTER 5 Customizing the Salesforce1

About the Salesforce1 Navigation Menu

Anywhere your users see the icon in Salesforce1, they can tap it to access the menu. As an administrator, you can customize what the menu contains.

What You Can Include

Depending on how your organization is configured and what they have access to, your users could see multiple items in their navigation menu.

Description Menu Item

Displays a list of the user’s pending approvals. Users can tap an approval item and approve or reject it from within Salesforce1. Available in the Salesforce1 downloadable app for iOS and the Salesforce1 mobile browser app. Approval Requests

Appears for organizations that have enabled a canvas app to appear in the Salesforce1 navigation menu.

Canvas apps

Availability depends on edition and user permissions. If you don’t include this item in the menu, a Dashboards item is automatically added to the set of Smart Search Items.

Dashboards

Lists events that are owned by the user, that the user created for him- or herself, and that the user or a user’s groups are invited to.

Events

Appears for organizations that have Chatter enabled. Feed

Only custom Lightning components that have a Lightning component tab associated with them can appear in the Salesforce1 navigation menu. Lightning component

tabs (Beta)

Custom Salesforce1 app pages. Lightning Pages

Appears for organizations that have Chatter enabled. If you don’t include this item in the menu, a Groups item is automatically added to the set of Smart Search Items.

Groups

Displays a list of flow interviews that the user paused. An interview is a running instance of a flow. Users can tap an interview and resume or delete it from within Salesforce1. Available in the Salesforce1 mobile browser app only. Paused Flow Interviews

(33)

Description Menu Item

Appears for organizations that have Chatter enabled. If you don’t include this item in the menu, a People item is automatically added to the set of Smart Search Items.

People

Adds Salesforce objects to the Recent section in the menu. This item also adds a set of recently-searched objects to the Recent section and adds the More Smart Search Items

item so users can access all the objects they have permission to use and that are supported in Salesforce1. If you don’t include this item in the navigation menu, users can’t access any objects in Salesforce1.

Note: If your users don’t yet have a history of recent objects, they initially see a set of default objects in the Recent section. It can take up to 15 days for the objects that users work with regularly in both Salesforce1 and the full Salesforce site to appear in the Recent section. To make objects appear under Recent sooner, users can pin them from the search results screen in the full site.

Lists of a user’s open and closed tasks and tasks that have been delegated. Tasks

An app that helps users plan for and manage their day by integrating mobile calendar events with associated Salesforce tasks, accounts, and contacts. The Today

app also allows users to instantly join conference calls, quickly log notes about events, and more. Available in the Salesforce1 downloadable apps only. Only Visualforce pages with the Available for Salesforce

mobile apps checkbox selected will display in Salesforce1. Visualforce page tabs

We won’t get into Visualforce pages in these exercises, but to learn more about them and how they work in Salesforce1, see Extending Salesforce1 with Visualforce Pages on page 79.

Try It Out: Configuring the Salesforce1 Navigation Menu

1. From Setup, click Mobile Administration > Mobile Navigation.

Some items are automatically added to the menu.

The order in which you put the items in the Selected list is the order that they display in the navigation menu. Also, the first item you put in the list becomes your users’ Salesforce1 landing page. The Acme Wireless mobile technicians will probably be using the Today and Tasks menu items the most, so we want to put those at the top.

(34)

2. Using the Up or Down arrows, arrange the top items in the Selected list like so: • Today

• Tasks • Feed

• Smart Search Items • Dashboards

Now whenever a mobile technician logs in to Salesforce1, the Today page will be the first thing they see.

3. Click Save.

Let’s go look at our changes.

Test Out the Salesforce1 Navigation Menu

1. Open the Salesforce1 app on your mobile device.

2. Tap to access the navigation menu.

3. Pull down and release the navigation menu to refresh it.

You should see the Today, Tasks, and Feed items at the top, and then the Recent section, which is created from the Smart Search Items element.

4. Scroll down to the Apps section.

This section contains any menu item that was put below the Smart Search Items element, whether it’s really an “app” or not.

(35)

Now that we’ve addressed the Salesforce1 navigation menu, let’s look at configuring our data for mobile.

How the Salesforce1 Navigation Menu Works

• The first item in the Selected list becomes your users’ Salesforce1 landing page. • You can’t set different menu configurations for different types of users.

• When organizing the menu items, put the items that users will use most at the top. The Smart Search Items element can expand into a set of eight or more menu items and it might end up pushing other

(36)

elements below the scroll point if you put it near the top of the menu. Anything you put below the Smart Search Items element appears in the Apps section of the navigation menu.

• Before you can include Visualforce pages, Lightning Pages, or Lightning components in the Salesforce1 navigation menu, you must create tabs for them in Setup, at Create > Tabs.

• Anything that is represented by a tab in Salesforce—such as standard and custom objects, Visualforce pages, the Feed, People, or Groups—is visible for a user in the Salesforce1 menu, based on the user’s profile settings. For example, if a user is assigned to a profile that has the Groups tab set to Tab Hidden, the user won’t see the Groups menu item in Salesforce1, even though an administrator has included it in the menu.

Some objects are excluded from the Recent section in the Salesforce1 navigation menu, even if you accessed them recently.

• Tasks and events

• People, groups, and dashboards, if these items were added directly to the navigation menu • List views, which are shown only on object home pages, not in the navigation menu

• Objects that aren’t available in Salesforce1, including any objects that don’t have a tab in the full Salesforce site

About the Dashboards, People, and Groups Menu Items

If you don’t add the Dashboards, People, or Groups menu items to the Selected list for the navigation menu, then they’re automatically included in the Smart Search Items set of objects and show up in the Recent section of the menu in Salesforce1. If you do add Dashboards, People, or Groups individually to the Selected list for the navigation menu, then they show up outside of the Recent section and their location in the Salesforce1 menu can be customized, just like Tasks, Today, and other individual menu items.

Pin an Object into the Recent Section

Users can customize the objects that appear in the Recent section of the Salesforce1 navigation menu. If they search for an object in the full site, they can hover their mouse over the object name and click to pin it to the top of the search results. The order of pinned objects in the full site determines the order of the objects that stick to the top of the Recent section of the navigation menu. However, pinning objects in this way causes the unpinned objects remaining in the Recent section to drop into the More element. Chapter 5 Customizing the Salesforce1 Navigation Menu

(37)

CHAPTER 6 Customizing How Your Data Shows

Up in Salesforce1

We’ve done the basic configuration for the Salesforce1 app; now it’s time to consider how we can optimize things in the full Salesforce site to give In this chapter ...

• How Page Layouts

Work in Salesforce1 our users the best possible mobile experience. First, we’ll customize how_{our Salesforce data shows up when presented in a mobile context.} • About Compact

Layouts Two factors in Salesforce affect how information is displayed in Salesforce1. One has been around for a while: page layouts. The other is newer: compact layouts. You’ll learn about both in this chapter.

(38)

How Page Layouts Work in Salesforce1

You can use the enhanced page layout editor in the full Salesforce site to customize the layout of an object’s record detail pages, configure actions, and adjust which fields and related lists appear.

In Salesforce1, page layouts drive these areas of the mobile experience: Record Related Information and Detail Pages

When you view a record in Salesforce1, you see the fields, Visualforce pages, and related lists that are based on the record type and the user’s profile. Related lists show up as single-line cards containing the name of the page or related list. Tapping the related list card displays its details.

Mobile Cards

You can add expanded lookups, components, canvas apps, and Visualforce pages to the Mobile Cards section of your page layout to have them show up as mobile cards in Salesforce1. The elements you place in this section don’t show up on a record’s detail page in the full Salesforce site. They only appear on the record’s related information page in Salesforce1.

Note: In organizations that are created after Spring ’14, the Twitter component is added by default to the Mobile Cards section of page layouts for objects that support it.

Actions

In Salesforce1, actions in the Actions in the Salesforce1 Action Bar section of a page layout appear in the action bar and action menu on the object’s record pages.

Here are the record detail page, related information page, and action menu for a sample account, Edge Communications:

(39)

We’ll cover actions in a later chapter. For now, let’s focus on record pages and mobile cards.

Rethinking Your Page Layouts for Mobile

Page layouts containing dozens of fields and lots of related lists might be manageable when viewing records on a computer screen, but on a small mobile device, viewing that same record can be overwhelming. People accessing information using a mobile device are looking for a quick way to get what they need, and making your users sift through hundreds of fields and related lists just doesn’t make sense. For example, in our Warehouse data model, our custom page layout has 32 standard and custom fields. That may not seem like many, but in a mobile context, fields add up quickly. In the full Salesforce site, an account record detail page using the Warehouse Schema Account Layout looks like this:

(40)

In Salesforce1, the same account detail page looks like this: Chapter 6 Customizing How Your Data Shows Up in Salesforce1

(41)

Three pages of scrolling, and that’s from a page layout with only 32 fields! If you were a mobile user trying to find specific fields in a record detail with dozens of fields on your phone, you’d have to scroll... and scroll... and scroll. It’s not the best user experience, and it’s definitely not good for your users’ productivity. You have two options for handling page layouts for your mobile users: re-engineer your existing page layouts, or create new page layouts that are mobile-friendly from the outset.

We’ll look at both options. First, we’ll walk through creating a fresh mobile-friendly page layout, then we’ll discuss tips and tricks for optimizing existing long layouts for a mobile audience.

Try It Out: Create a Custom Page Layout for the Mobile Technicians

Profile

Users like the mobile technicians at Acme Wireless will spend the majority of their time accessing Salesforce from a mobile device. We can create a streamlined, mobile-optimized page layout assigned to the Mobile Technician profile, with only the items they need when on-site, and, voilà! Instant productivity boost. In addition, using the specialized Mobile Cards section of the page layout, we can enhance the Salesforce1 record’s related information page by adding Visualforce pages and lookup cards.

1. From Setup, click Customize > Accounts > Page Layouts. 2. Click New.

3. Leave the Existing Page Layout drop-down list set to –None–.

We want to start with a clean slate for this page layout, so we’re choosing not to clone an existing page layout.

4. Enter Account Mobile Technician Layout in the Page Layout Name field. 5. Click Save.

Required fields and “Always on Layout” fields are pre-populated onto the page layout. We just need to add a few more that are pertinent to the mobile technicians.

6. Drag these fields from the palette into the Account Detail portion of the page, below the existing fields.

• Shipping Address • Business Hours • Phone

7. Click the Visualforce Pages category in the palette and drag Account Location into the Mobile Cards section.

(42)

Account Location is a preconfigured Visualforce page that shows the user the location of the selected account on a Google map. In Salesforce1, this will show up as a mobile card on the account record related information page.

Note: Only Visualforce pages with the Available for Salesforce mobile apps checkbox selected will display in Salesforce1. Mobile-enabled Visualforce pages show up as slightly differently colored elements in the palette than their

non-mobile-enabled counterparts. Hovering your mouse over a Visualforce page element in the palette shows whether the Visualforce page is mobile-enabled.

For more detailed information about using Visualforce in Salesforce1, see Extending Salesforce1 with Visualforce Pages on page 79.

8. Click the Expanded Lookups category and drag Parent Account into the Mobile Cards section, above the Account Location mobile card.

Parent Account is a lookup field, and putting it into the Mobile Cards section makes it display as a related lookup card on the account’s related information page in Salesforce1.

9. Click the Related Lists category and drag the Cases and Contacts related lists to the Related Lists section.

Related lists show up on the record related information page in Salesforce1. When the mobile technicians navigate to an account’s related information page, they’ll see preview cards for the related lists that they can tap to get more information about the cases and contacts for that location. 10.Click Save.

11.Click No when asked if you want to override users’ customized related lists. 12.Click Page Layout Assignment.

13.Click Edit Assignment.

In this step, you would normally assign the new mobile-optimized page layout to a user profile for the mobile technicians. However, since you’re logged in as a system administrator, we’re going to have you assign it to the System Administrator profile instead.

14.Click the System Administrator line item to select it.

15.Select Account Mobile Technician Layout from the Page Layout to Use drop-down list. The System Administrator profile should now be assigned to the Account Mobile Technician Layout.

16.Click Save.

Now let’s check out what we did in the Salesforce1 app.

(43)

Test the Page Layout

1. Open the Salesforce1 app on your mobile device and log in. 2. Tap to access the navigation menu.

3. In the Recent section, tap Accounts. You may have to tap More... to find it. 4. Tap the search bar.

5. Enter Barbary.

6. Tap Search.

7. Tap Barbary Coast Wireless.

You’re on the Barbary Coast Wireless record detail page, which is the default view when accessing a record. Scroll down a bit, and you should see the same fields we added to the page layout, in the same order.

8. Tap Related to get to the related information page.

You should see the Parent Account lookup card and the preview card for the Visualforce page first. Chapter 6 Customizing How Your Data Shows Up in Salesforce1

(44)

Scroll down and you should also see the related lists that we added to the page layout. Tap a related list to see its details.

Now that we’ve created this specialized page layout and added the fields our mobile technicians will need, their jobs will be much easier when they go on site. When they visit an account record’s related information page in Salesforce1, they won’t have to shuffle through a long list of unnecessary fields to find the ones they really want. And, since we added the Visualforce page as a mobile card, they’ll be able to see the location of an account on a Google map.

In the Actions chapter, we’ll enhance this page layout with special actions we’ve created just for our mobile technicians. But for now, let’s go over some recommendations for paring down existing page layouts to make them more mobile friendly.

Tips for Optimizing Page Layouts for Mobile

In many cases, creating a new mobile-only page layout may not make sense. Here are some tips and tricks to making your existing page layouts more mobile friendly.

When optimizing a page layout, consider:

• What are the important things to see at a glance?

(45)

• What are the important moments for your users when they’re working in Salesforce1? • What can you automate so your users don’t have to do it?

The Key: Organize and Minimize Fields

• Use sections to organize information logically, putting the most important things at the top of the page so they show up first. Your users don’t want to search for fields individually. Organizing similar fields in sections will help your users find what they need. They can then easily scroll down the page to the section they care about.

• For accounts, contacts, and leads, you don’t need to put phone or email fields near the top. They’re already quickly accessible via the and icons on each record page’s action bar.

• You don’t need to keep fields in one column, as the page will render dynamically based on the device that’s viewing it. A phone will reorder the fields into a single column, and a tablet or desktop will show two columns.

• Put the most important fields into the compact layout—which drives record highlights and record preview cards in Salesforce1—so they’re available right up front, and so your mobile users don’t have to drill into the record detail. We’ll get into compact layouts in more detail soon.

• Keep the number of required fields to a minimum. Setting a field to required means it must appear on the detail page of all page layouts, so consider whether each field is truly required. You might have to convince stakeholders that a field isn’t actually necessary for a record to be saved.

• If available in your organization, think about using record types so that fields that aren’t common to all records don’t have to appear on all records.

• To reduce the number of fields on a screen, consider using default values for new records instead of having the user enter the data.

We’ve gone over page layouts. Now let’s get into another kind of layout, created especially for mobile: the compact layout.

About Compact Layouts

In the last section, we learned how page layouts affect the look and content of records in the Salesforce1 app. But page layouts aren’t the only thing used to help customize how your Salesforce data appears in a mobile environment.

Compact layouts are used in Salesforce1 to display a record’s key fields at a glance. Compact layouts are designed for viewing records on touchscreen mobile devices, where space is limited and quick recognition of records is important.

(46)

In the full Salesforce site, compact layouts determine which fields appear in the Chatter feed item that appears after a user creates a record with a quick action.

Note: To avoid inadvertent sharing of information through the feed, the fields displayed in the Chatter feed items for tasks created using a quick action are determined by the Task page layout. In Salesforce1, the first four fields that you assign to a compact layout are displayed in:

• An object’s record highlights area

• Expanded lookup cards on a record’s related information page

If a mobile user doesn’t have access to one of the first four fields that you’ve assigned to a compact layout, the next field on the layout is used.

The first four fields you assign to your compact layout populate the record highlights section at the top of each record view in Salesforce1, so we’ll put the fields we think our mobile technicians most want to see into the list.

Creating and customizing compact layouts for objects isn’t required for Salesforce1, because system defaults are provided out of the box. However, we recommend using compact layouts to put important fields into object record headers—and elsewhere—to help your mobile users get the information they need quickly. Let’s give it a try.

Try It Out: Create a Compact Layout

If you don’t create custom compact layouts for an object, all of the object’s record highlight fields, preview cards, and action-related feed items are driven by a read-only, predefined system default compact layout that contains a predefined set of fields. After you create one or more custom compact layouts, you can set one as the primary compact layout for the object. The primary compact layout is then used as the default for that object.

We’ll create a custom compact layout, and then set it as the primary compact layout for the Merchandise object. Our new compact layout is used to render important merchandise record fields first in Salesforce1 for the Acme Wireless mobile technicians.

Before we can see compact layouts in action, though, we need a Merchandise record in our organization. Let’s quickly create one.

1. From the Force.com app menu, select Warehouse. 2. Click the Merchandise tab.

3. Click New.

4. For Merchandise Name, enter iPhone 4.

5. For Price, enter 299.

(47)

6. For Quantity, enter 1.

7. Click the Warehouse lookup, then select Oaklandia. 8. Set the Condition to Refurbished.

9. Click Save.

Currently, the Merchandise object uses its system default compact layout, which only has the Merchandise Name field assigned. Here’s what our iPhone 4 record looks like in Salesforce1:

Let’s add more fields alongside that “iPhone4” so our mobile users can see more pertinent information right at the top of the Merchandise record pages.

1. In Setup, click Create > Objects.

Tip: Merchandise is a custom object. If we were creating a custom compact layout for a standard object, the path in Setup would be Customize > Object > Compact Layouts. 2. Click the Merchandise object name.

3. Scroll down to the Compact Layouts related list and click New. 4. In the Label field, enter Customized Compact Layout.

(48)

5. Select these fields for the compact layout, then click Add.

When on site, these are the most important fields for our mobile technicians to see. You can select and add them individually or select them as a group using CTRL-click.

• Condition

• Merchandise Name • Price

• Quantity

6. Using the Up or Down buttons, adjust the list so that the fields are in this order: Merchandise Name, Quantity, Condition, Price.

7. Click Save.

Now we need to set our compact layout as the primary. 8. Click Compact Layout Assignment.

You can see that the primary compact layout is set to the System Default here. We need to change that.

9. Click Edit Assignment.

10.Select the compact layout you just created to use as the primary compact layout. 11.Click Save.

We’ve customized a compact layout for the Merchandise object. Now let’s see what its related information page looks like in Salesforce1.

Test the Compact Layout

When you customize a compact layout and assign it as the default, as we just did, the changes are reflected in Salesforce1 immediately.

1. Open the Salesforce1 app on your mobile device. 2. Tap to access the navigation menu.

3. In the Recent section, tap Merchandise. You may have to tap More... to find it. 4. Tap the iPhone 4 item.

(49)

As you can see, the record highlights area has the fields from our newly-created custom compact layout. Instead of seeing just the merchandise name, as on the system default layout, the Acme Wireless mobile technicians can now see much more: that there is one refurbished iPhone 4 in stock at the warehouse, and it costs $299.00.

Tell Me More: Compact Layouts

We’ve gone over a lot about compact layouts, but here are a few more more tidbits about how they work. Compact layouts support all field types except:

• text area • long text area • rich text area • multi-select picklist

Users who don’t have access to certain fields in Salesforce won’t see them on the compact layout. Removing a field from a page layout doesn’t remove it from the object’s compact layout. The two layout types are independent.

(50)

Compact Layouts and Record Types

If you have record types associated with an object, you can override the primary compact layout assignment and assign specific compact layouts to different record types. If you don’t set any record type overrides, all record types use the object’s primary compact layout by default.

To find out more about compact layouts and record types, see “Assigning Compact Layouts to Record Types” in the Salesforce Help.

(51)

CHAPTER 7 Using Actions in Salesforce1

As an administrator, you can enable valuable micro-moments for all of your users by creating unique actions. When thinking about what actions In this chapter ...

• About Quick Actions _{you might want to create specifically for Salesforce1, ask your users what} they wish they could do in the mobile context.

• Point and Click Your Way to Actions

For example, an administrator at a food service company could create an “Emergency Order” action that allows their delivery drivers to immediately • About Action Layouts

• About Predefined Values in Actions

order extra or missing food items using their mobile phone while still at a customer site. Creating actions for Salesforce1 can drive adoption in your organization and make you a hero to your users!

• About Custom

Actions _{In this chapter, we’ll learn about types and categories of actions, how to} create and customize them in Salesforce using point-and-click tools, and how they can help mobile users get essential work done while away from the office.

(52)

About Quick Actions

Create actions and add them to the Chatter publisher on the home page, on the Chatter tab, in Chatter groups, and on record detail pages. In Salesforce1, actions appear in the action bar, its associated action menu, and as list-item actions. In addition, actions have their own action layouts, which let you specify which fields are included in the action, and in which order.

Where Do Actions Appear?

In the Salesforce1 app, actions appear in the action bar and its action menu.

Actions also appear in Salesforce1 in an action bar on list items such as task lists and related record lists. This gives your mobile users the ability to work with records directly from lists and update records without having to open them. To access list item actions, navigate to the task list or open a related list from an object’s related information page. Then swipe left on the desired record.

Types of Actions

There are several types of quick actions you can create using point-and-click tools in Salesforce. Chapter 7 Using Actions in Salesforce1

Salesforce1 Mobile App Developer Guide