Professional Documents
Culture Documents
Cheatsheet
Salesforce1 is a mobile app development platform for everyone. When displayed in the Salesforce1 app, the standard Salesforce
Designed for scale with open APIs for extensibility and integration, header and sidebar are automatically removed. However,
and powerful developer tools, theres no limit to what you can build Visualforce pages used as custom actions in the publisher are
on the platform. Salesforce1s flexible development models enable shared with the full Salesforce site, and pages added to the
every user to create custom apps backed by mobile back-end Salesforce1 navigation may or may not be shared. Pages shared
with the full site shouldnt have these items explicitly removed,
services and a unique, yet familiar, mobile user experience. ISVs
unless thats the standard practice for all Visualforce pages in
can develop apps that take advantage of advanced packaging and your organization.
version management controls, complete enterprise marketplace
capabilities with the AppExchange, and feed-first discovery of their
apps within the Salesforce1 Platform.
You can access Visualforce pages from the following areas of the
mobile app; each area is optimized for a specific purpose:
Navigation Menu For pages that arent related to other objects
or that require a full screen, add the page to the navigation menu,
or as a global action in the publisher.
Global or Object-Specific Publisher Actions If you want a 1. The Salesforce1 header, which provides access to the main
Visualforce page to surface in the publisher, you can create it as a Salesforce1 menu, is a fixed height. The contents of the
global or object-specific action. Custom actions arent specific to header cant be changed.
mobile users, and appear in both the Salesforce1 app and in the 2. The rest of the device screen is dedicated to the
full Salesforce site. In the Salesforce1 app, custom actions appear Visualforce page.
in the publisher. In the full Salesforce site, custom actions appear
in the publisher menu. Note: You must be sure to select the Available for Salesforce
mobile apps checkbox. This designates that the page is
These options are explained in more detail in the following sections. mobile-ready and can be used in Salesforce1.
Salesforce1 Developer Cheatsheet
1
3
2
2
4
4
3
5
5
3. A Visualforce page added to the objects page layout. 4. Control the height of the mobile card by setting the height
in pixels in the page layout editor. The mobile card area
4. Set the width to 100%; the element sizes automatically, uses exactly that height, even if the mobile cards content
minus some padding on either side. is shorter. In that case, the extra area is blank. If the cards
content is taller, the content is clipped. As a best practice,
5. Control the height of the Visualforce pages area by setting dont create mobile cards taller than the smallest device
the height of the item in pixels in the page layout editor. screen you intend to support. Be sure to set the height of
The Visualforce element uses exactly that height, even if the screen elements relevant to your environment. So if you have
content is shorter. In that case, the extra area is blank. If the an element thats always 300 pixels high, set the height to
pages content is taller, the content is clipped. As a best practice, 300 pixels.
dont set inline Visualforce pages to be taller than the smallest
device screen you intend to support. 5. The records related items are displayed after all mobile cards.
Creating a Visualforce Custom Action Navigation
Creating a Visualforce custom action is the same process as global Salesforce1 provides a framework for handling various navigation
actions or object-specific actions described on the Salesforce1 controls and events, which isnt available to Visualforce pages
Admin Cheat Sheet. To use a Visualforce page in a global or object- when they run on the full Salesforce site. For pages shared
specific action, select Custom Visualforce for Action Type. between the Salesforce1 app and the full site, use the sforce
object when its available, and standard Visualforce navigation when
Note, when making an object-specific Visualforce publisher action,
its not. Salesforce1 app and the publisher menu in the full site.
you need to set the Standard Controller of your page to the SObject
you want to create the action on. The intent of the code is to navigate to the detail page for the
account for whom the order was placed, and it needs to work in
both places:
// Go back to the Account detail page
if( (typeof sforce != 'undefined') && sforce &&
(!!sforce.one) ) {
// Salesforce1 navigation
sforce.one.navigateToSObject(aId);
}
else {
// Set the window's URL using a Visualforce
expression
window.location.href =
'{!URLFOR($Action.Account.View, account.
Id)}';
}
sforce.one.navigateToRelatedList Navigates to a related list for the parentRecordId .relatedListId is the API
(relatedListId,parentRecordId) name or ID of the related list to display.
sforce.one.navigateToList( Navigates to the list view thats specified by the listViewId , the ID of the
listViewId,listViewName, scope) list view to be displayed. listViewName sets the title for the list view. Set
scope to the name of the sObject in the view.
sforce.one.createRecord(entityName [,recordTypeId]) Opens the page to create a new record for the specified entityName .
recordTypeId specifies the record type for the created object.
See "Navigation with the sforce.one Object" in the Salesforce1 Mobile App Developer Guide for additional detail.
Salesforce1 Developer Cheatsheet
b. p.auxText The text that you want to post. We The message would look like:
concatenate this text with whatever the user enters into the {
"What are you working on" field. There must be some text "body" : {
provided (either by the user in the text box, or by your app) "messageSegments" : [ {
or there will be an error. "type" : "Text",
"text" : "Please Approve my trip: Release
Planning at HQ"
2. Link Post This is the standard link type of post. The LinkPost } ]
payload must contain: },
a. p.feedItemType = "LinkPost" "attachment" : {
b. p.auxText This is the text that appears over the link box "description" : "This is a travel itinerary
in the feed item for Itinerary - Release Planning at HQ. Click the
link to open the Canvas App.",
c. p.url This is the URL the link will direct to "parameters" :
d. p.urlName This is the friendly name that appears over the "{"itinerary":"123"}",
URL in the link box "title" : "Itinerary - Release Planning at HQ",
"namespacePrefix" : "",
3. Canvas Post - This is a new feed item type that will create a "developerName" : "Itinerary_App",
feed item that can load a Canvas App directly in the feed. "height" : "100px",
The CanvasPost must contain: "thumbnailUrl" : "https://icons.iconarchive.
com/icons/
a. p.feedItemType = "CanvasPost"
aha-soft/perfect-transport/48/ Airplane-icon.
b. p.auxText This is the text that appears over the canvas png",
box in the feed item "attachmentType" : "Canvas"
c. p.namespace The namespace of your Canvas App (if }
set) }