Versions Compared

Old Version 7

changes.mady.by.user Fernando Rodriguez

Saved on

compared with

New Version Current

changes.mady.by.user Carla Locke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
 
 
NameMain Background Color

Key

pulsar.layout.mainBackgroundColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This setting defines the background color used for object lists and object detail screens. Notes/Comments
 
 
NameMain Text Color

Key

pulsar.layout.mainTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The primary color used for text used in object lists and object detail screens. Notes/Comments
 
 
NameLabel Text Color

Key

pulsar.layout.labelTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The color used for labels used in object lists and object detail screens. Notes/Comments
 
 
NameNavigation Title Text Color

Key

pulsar.navigation.linkTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The color used for the text displayed on the title of the navigation barNotes/Comments
 
 
NameSection list and related list selection screen text color

Key

pulsar.layout.splitMasterTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The color used for labels used in section and related list selection screens.

Notes/Comments
 
 
NameSection list and related list selection screen background color

Key

pulsar.layout.splitMasterBackgroundColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The background color used in section and related list selection screens. Notes/Comments
 
 
NameSection list and related list selection screen highlighted text color

Key

pulsar.layout.splitMasterHighlightedTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The highlighted text color used in section and related list selection screens. Notes/Comments
 
 
NameDefault


NameDefault To Related Lists

Key

pulsar.layout.defaultShowRelated

Value

Comma or new line separated API names of the objects for which you would like this behavior.

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Use this option to view Related List as opposed to the Details of the object. Sometimes the parent object is just a place holder for all the related items. So this makes the navigation easier. 
Notes/Comments


 
 


Name
Activity List Setting
Attachment Image Quality

Key

pulsar.
layout
attachment.
activityListItems
ImageQuality

Value

Comma or new line separated activity items.
Integer numeric value (between 0 - 100)

Default Value (if any)

Note, Attachment, Task, Event, Calendar
100
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Use this option to specify what shows up under + and 'eye/view' icon

This setting will reduce image quality in order to reduce image size. 100 would be full quality (no compression) and 0 would be full compression.

Notes/Comments
 
 



Name
Hide Add Activity Button
Attachment Max Side Pixels

Key

pulsar.
layout
attachment.
hideAddActivityButton
maxSidePixels

Value

Comma or newline separated <object API name>:<RecordTypeDeveloperName> listNotes/Comments

ObjectAPIName1:RecordTypeName1,ObjectAPIName2:RecordTypeName2,ObjectAPIName3:RecordTypeName3

Use the word "Default" to denote that the setting applies to all of that object's record types not explicitly specified.

 
 
NameHide View Activity Button

Key

pulsar.layout.hideViewActivityButton

Value

TRUE / FALSE
Integer numeric value

Default Value (if any)

1024
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

For whatever reason, if the admin wants to deny this capability. They can enable this setting.. 

This setting will shrink image attachments along the maximum side (width in landscape or height in portrait) to the given pixel value, preserving the aspect ratio of the image.  Images with both dimensions less than the setting value will not be altered.

Notes/CommentsAvailable in Pulsar 11.0.2+
To disable scaling attachments, set the value of this setting to zero (0).  Please note that unscaled image attachments can represent significant cost in terms of both storage and network sync time.



NameAttachment Thumbnail Max Side Pixels

Key

pulsar.attachment.thumbnailMaxSidePixels

Value

Integer numeric value

Default Value (if any)

FALSE
50
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Hide view activity button

Attachment thumbnail images will be generated/scaled to this value along the maximum side (width in landscape or height in portrait), preserving the aspect ratio of the image.  Thumbnails are only used within the Pulsar app for image attachments.

Notes/Comments
 
 

Value

TRUE / FALSE
Range for this setting is 32 - 512 pixels



Name
Hide Social Buttons

Key

Pulsar.hideSocialIcons
Barcode Valid Formats/Symbologies for Scanning

Key

pulsar.<object API Name>.barcodeValidFormats

pulsar.<object API Name>.barcodeValidFormats.android

pulsar.<object API Name>.barcodeValidFormats.windows

Value

Any number of the following terms separated by commas, semicolons, and/or newlines.

upca , upce , ean13 , code39 , code39mod43 , ean8 , code93 , code128 , pdf417 , qr , aztec

Default Value (if any)

FALSENotes/Comments
 
 
NameHide Lead Convert Button

Key

pulsar.hideLeadConvertButton

Value

TRUE / FALSE
None – uses the default formats/symbologies native to the platform
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

If the admin wants to not display the LinkedIn, Twitter, Google and Map icons, we can skip them entirely

NOTE:

  • upca is the same as ean13 in iOS Pulsar
  • These and additional barcode formats may or may not be supported on Windows UWP and Android depending on the scanner device.  Leaving this value as an empty string will use the default formats on UWP and Android platforms.




NameLoad Objects as HTML document

Key

pulsar.layout.loadAsHTML.objects

Value

Comma, semicolon, or newline separated list of <sobjectType>:<contentDocumentId>

Default Value (if any)

FALSE

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

For whatever reason, if the admin wants to deny this capability. They can enable this setting
From the specified Object List Page, this will load the specified HTML/JS content library document.
Notes/Comments
 
 
NameLead Convert Options

For example:

Account:06950000002zmNNAAY;
Some_Custom_Object__c:06950000002PSGMAA4;




NameHide the + (Create) button on any related list item

Key

pulsar.layout.

leadConvertOptions

hideRelatedListAddButton

Value

Any/All of the following three choices (Opportunity, Attach, Contact)

New line separated values of the following pattern

ParentObjectName : Record Type Developer Name : Related List Name

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

If the admin wants to only use one of the three default options, they can use this setting
 
 
NameLead Custom Field Mapping

Key

pulsar.layout.leadConvertMapping

Value

<lead custom field api name> : <target object type> . <target field custom field api name> 

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Custom field mappings from the lead object to the Account, Contact, and Opportunity objects can be specified for the lead conversion process.Notes/Comments

Custom_Lead_Field_1__c:Account.Custom_Account_Field__c
Custom_Lead_Field_2__c:Contact.Custom_Contact_Field__c 

Custom_Lead_Field_3__c:Opportunity.Custom_Opportunity_Field__c
 
 
NameHide OrgChart Button
Use this option to hide the + button on any related list against a parent object.
Notes/Comments

Opportunity - Lets the user convert the lead to a new opportunity

Attach - Lets the user attach the lead to an existing opportunity

Contact - Lets the user convert the lead to a contact without creating an opportunity. 

Example: If you wanted to hide the + button on Contact related list on the Account of record type Customer, you would specify the following:

Account  : Customer : Contacts

Note: If you specify default in the place of any of these three parameters, it will apply to all in that category. For example, if you specified Account  : Default : Contacts, it will hide the + button for Contact related list for all account record types.  (You can get this information from workbench by using the REST explorer and running the following query: /services/data/vx.x/sobjects/Account/describe/layouts and then find the url for the layout and drill down to find the related list names).

If you specify Account : Default : Default, it will hide the + button on all related objects for all account record types.

If you specify Default : Default : Default, it will hide the + button on all related objects for all parent records. 



NameHide the Delete button on any related list item

Key

pulsar.layout.

hideOrgChartButton

hideRelatedListDeleteButton

Value

TRUE / FALSE

New line separated values of the following pattern

ParentObjectName : Record Type Developer Name : Related List Name

Default Value (if any)

FALSE
N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Hide org chart capability
 
 
NameEnable Signature Capture
Use this option to hide the Delete button on any related list against a parent object.
Notes/Comments
 
 
NameHide Additional Checkbox Fields in the Layout for Case, Lead, Task and Event

Key

pulsar.layout.hiddenFields

Value

<Object API Name> : <Record Type Developer Name> : <CuriumAutoAssigned or CuriumEmailSent>

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Just like the Salesforce.com backend, Pulsar displays the 'Use Assignment Rules' and 'Send Notification Email' checkboxes on objects that require it, i.e: CASE, LEAD, TASK, and EVENT. If the organization doesn't need to see these fields, you can hide them using this setting.  NOTE: To hide the Auto Assignment checkbox, use the field identifier 'CuriumAutoAssigned' and to hide the Send Notification Email checkbox, use the field identifier 'CuriumEmailSent'.Notes/CommentsLead:Default:CuriumAutoAssigned
Task:Default:CuriumEmailSent

Example: If you wanted to hide the Delete button on Contact related list on the Account of record type Customer, you would specify the following:

Account  : Customer : Contacts

Note: If you specify default in the place of any of these three parameters, it will apply to all in that category. For example, if you specified Account  : Default : Contacts, it will hide the + button for Contact related list for all account record types.  (You can get this information from workbench by using the REST explorer and running the following query: /services/data/vx.x/sobjects/Account/describe/layouts and then find the url for the layout and drill down to find the related list names).

If you specify Account : Default : Default, it will hide the Delete button on all related objects for all account record types.

If you specify Default : Default : Default, it will hide the Delete button on all related objects for all parent records. 



NameHide the Edit button on any object detail record

Key

pulsar.layout.
enableSignatureCapture
hideEditButton

Value

 List of Object API Name

New line separated values of the following pattern

ParentObjectName:Record Type Developer Name

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This will display a signature icon on the object layout that can be used to capture a quick signature.
Use this option to hide the edit button on any object detail page
Notes/Comments

Example: If you wanted to hide the Delete button on the Account of record type Customer, you would specify the following:

Account:Customer

Note: If you specify default in the place of these two parameters, it will apply to all in that category. For example, if you specified Account:Default

Opportunity:Default

 
 
NameEnable Camera Uploads/ Enhanced Attachment Mode

Value

TRUE

, it will hide the Edit button for all Account record types.

If you specify Default:Default, it will hide the Edit button on all object records.



NameField Lookup Filter

Key

pulsar.

attachment.enableEnhancedMode

<object_API_name>.<Record Typer Developer Name>.<field_API_name>.whereClause

Value

DEFAULT{

Action=SetResult;

Result=<field filter>;

}

Default Value (if any)

FALSE
N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This
will let the user take pictures right from within the app that
Setting can be
attached
used to
records as well as let them add multiple pictures from the album at the same time.

Value

TRUE / FALSE
filter lookup fields as defined on Salesforce
Notes/Comments
 
 
NameHide Objections Field in OrgChart View

Key

pulsar.layout.orgStruct.hideObjectionsField

Value

TRUE / FALSE

Default Value (if any)

FALSECompatibility
  •  iOS
  •  Windows
  •  Android

Description

Hide org chart objections text viewNotes/Comments
 
 
NameEnable Opportunity Product Chaining

Key

pulsar.opportunity.enableProductChaining

Example: If User need to  show the accounts related to "Retail Industry" only in while creating a contact record. They can use the below Pulsar settings

Key:

pulsar.Contact.AccountId.whereClause

Value:

DEFAULT{

Action=SetResult;

Result=Account.Industry = 'Retail';

}

Note: If you specify Default for record type or leave it blank, it will apply this to the Master record type. 




Name
Anchor
pulltorefresh
pulltorefresh
Enable Pull to Refresh

Key

pulsar.layout.enablePullToRefresh

Value

A list of object types separated by newlines

Default Value (if any)

FALSE
 
 
NameEnable Call Logging

Key

pulsar.enableCallLogging

Value

TRUE / FALSE

Default Value (if any)

FALSECompatibility
  •  iOS
  •  Windows
  •  Android

Description

When enabled, any call initiated from within Pulsar, upon ending, will ask the user if they wish to log the previous call. Opting to do so will create a new completed Task object with the corresponding information.Notes/CommentsNameEnable barcode scan for lookup object

Key

pulsar.<object API Name>.barcodeLookupFields

Value

List of field API names to match with the barcode scan
all
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

When creating an opportunity, upon pressing the Save button, Salesforce (if setup to do so) automatically navigates the user to a screen where they are prompted to add Products that are relevant to this Opportunity.Notes/Comments
 
 
NameEnable Temporary Population of the Auto Number Name field for an object

Key

pulsar.layout.autoNumberNameFields.enableTempData

Value

TRUE / FALSE

Default Value (if any)

TRUECompatibility
  •  iOS
  •  Windows
  •  Android

Description

While offline, Pulsar cannot automatically fill in an auto number field since these fields are best left sequenced by the server in a multi-user environment. However, if you have specified an auto number field for an object's name field, Pulsar will enter in some placeholder text by default. The placeholder text has this format: <object type> + " - Offline - " + <datetime object was created>  (e.g., "Account - Offline - Aug 20, 2015 11:00 AM").  This is done so that this record can be readily identified while offline.Notes/CommentsFor example, a parent object might only display that object's name field in the related list.  After a sync, the placeholder text is replaced with a real value from the server.

This setting is used to enable the pull to refresh feature on the native detail and related screens.  By default the 'all' special text is used to enable pull to refresh for all object types.  To enable a subset of objects instead, specify them like this:

Object1
Object2
Object3

Pull to refresh runs a special type of quick sync. This means that we first download the latest record on which pull to refresh was called from, and then we also pull down the latest records associated with one level above (parent or lookup records) as well as one level below (child records from associated related lists).

To disable Pull to Refresh, the Value field should be left blank.

Notes/CommentsOn iOS and Android, the pull to refresh feature works by dragging the screen downwards until the pull to refresh action is started.  On Windows, when pull to refresh is enabled, a new refresh button is added on the toolbar. 





Name
Anchor
enableFlattenedPicklistStyle
enableFlattenedPicklistStyle
Enable Flattened Picklist Style

Key

pulsar.layout.enableFlattenedPicklistStyle

Value

TRUE or FALSE

Default Value (if any)

None  NameShow Hidden Layout Section Headers

Key

pulsar.layout.showHiddenSections

Value

TRUE / FALSE

Default Value (if any)

FALSECompatibility
  •  iOS
  •  Windows
  •  Android

Description

By default, Pulsar honors the visibility set via SFDC for section headers defined on an object's layout. Specify this setting and assign it a TRUE value in order to override and show all hidden section headers. Notes/CommentsFeature as of Pulsar version 2.5.9 (101).  NameOverride an object's name field

Key

pulsar.<object API name>.nameField

Value

<field API name>
FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

When enabled for a specific object, any lookup field that references that object will provide the option to scan a barcode when edited in Pulsar. For example for the setting with key pulsar.Account.barcodeLookupFields and value "AccountNumber, Name", Pulsar will the search the database for Accounts that have either the AccountNumber or the Name fields that match the scanned barcode.

This setting changes the rendering of picklists from an inline multi-line selection UI to a single row field that opens a separate UI with the picklist choices.

See also pulsar.layout.flattenedPicklistThreshold, which defines the number of items threshold before the flattened picklist style is used.

Notes/Comments





Name

Anchor
flattenedPicklistThreshold
flattenedPicklistThreshold
Flattened Picklist Threshold

Key

pulsar.layout.flattenedPicklistThreshold

Value

number of items

Default Value (if any)

5
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

An object's name field is the field displayed for reference fields on another (related) object's layout. For example, on the Contact object layout, the Account field is a reference field that displays the text from the Account Name field. Specify this setting with a valid field to change what Pulsar will use as the display text for reference fieldskey: pulsar.Case.nameField
value: CaseNumber

This setting is not used unless pulsar.layout.enableFlattenedPicklistStyle is defined as TRUE. 

Picklists up to and including the "threshold" number of items will render as an inline multi-line selection UI. Otherwise, a single row field that opens a separate UI with the picklist choices will be rendered.

Notes/Comments

Feature as of Pulsar version 2.5.9 (100).

For most objects, the name field is literally the 'Name' field, but for some standard objects it is something different (e.g., Subject for Task/Event). Please note that for the Case object, Pulsar uses the Subject field by default instead of the CaseNumber field. To change this to mimic Salesforce, create this setting:

 Available in Pulsar 9.0+