Versions Compared

Old Version 56

changes.mady.by.user Vikas Verma

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.


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)


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
Hide 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:CuriumEmailSentNameEnable Signature Capture

Key

pulsar.layout.enableSignatureCapture

Value

 List of Object API Name:Record Type Name

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This will display a signature icon on the object layout that can be used to capture a quick signature.Notes/Comments

Account:Default

Opportunity:Default

NameAttachment Image Quality

Key

pulsar.attachment.ImageQuality

Value

Integer numeric value (between 0 - 100)

Default Value (if any)

100
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

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



NameAttachment Max Side Pixels

Key

pulsar.attachment.maxSidePixels

Value

Integer numeric value

Default Value (if any)

1024
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

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)

50
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

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/CommentsRange for this setting is 32 - 512 pixels
NameSingle Object Lookup Shortcut

Key

pulsar.<object API Name>.enableReferenceLookupShortcut

Value

TRUE or FALSE

Default Value (if any)

NoneCompatibility
  •  iOS
  •  Windows
  •  Android

Description

When enabled for a specific object, any lookup field that references that object will skip the selection list if there is only one object available to fill. This shortcut takes into account the configured filters and where clauses for a particular object, but not any default List View filters for the object.



Name
Enable barcode scan for lookup object - Match Fields

Key

pulsar.<object API Name>.barcodeLookupFields

Value

List of field API names to match with the barcode scan

Default Value (if any)

NoneCompatibility
  •  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 then search the database for Accounts that have either the AccountNumber or the Name fields that exactly match the scanned barcode.NameEnable barcode scan for lookup object - Where Clause

Key

pulsar.<object API Name>.barcodeLookupWhereClause

Value

PulsarSettings Language (PSL) to generate a valid SQL where clause

Default Value (if any)

NoneCompatibility
  •  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. Once scanned, the barcode value will be available in the PSL code using the @@CurrentScanCode  special variable. The expected result of the PSL is a SQL where clause, returned using the SetResult action. NOTE: This setting is overriden by the barcodeLookupFields setting above when both are enabled.Name Skip the barcode "Next" button

Key

pulsar.<object API Name>.barcodeScanSkipNextButton

pulsar.<object API Name>.barcodeScanSkipNextButton.android

pulsar.<object API Name>.barcodeScanSkipNextButton.windows

Value

True or False

Default Value (if any)

FALSECompatibility
  •  iOS
  •  Windows
  •  Android

Description

When enabled for a specific object, the barcode scanner will skip the 'Next' button press, and will proceed with the first valid barcode scanned.
NameBarcode 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)

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

Description

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.
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/Comments
Feature as of Pulsar version 2.5.9 (101).NameOverride an object's name field

Key

pulsar.<object API name>.nameField

Value

<field API name>

Default Value (if any)

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 fields.
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:

key: pulsar.Case.nameField
value: CaseNumber

Changes the presentation of picklist and multipicklist fields with a small number of selections so that the choices all appear directly on the edit layout rather than requiring a popup to see.

  • Flattened picklists appear as Radio Buttons. If the field is a multi-select picklist, it will appears as square checkboxes, instead of round radio buttons.
NOTE: To conserve screen real estate and formatting, picklists with over 5 items will still use the normal picklist presentation (popup selection list)
NameDefine the currency locale for a single currency org

Key

pulsar.singleCurrencyOrg.locale

Value

<a locale identifier>

Default Value (if any)

Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The locale identifier is expected to be in the form of: a 2 character language descriptor (ISO 639-1), followed by an underscore, followed by a 2 character region descriptor (ISO 3166-1). For example, the locale identifier for the continental United States is: en_US
Notes/Comments

Salesforce does not provide an API to determine what the currency locale is for a single currency org. If this setting is not specified, the locale for currency will instead be based on the user's locale as defined in Salesforce.

NameLoad Objects as HTML document

Key

pulsar.layout.loadAsHTML.objects

Value

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

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

From the specified Object List Page, this will load the specified HTML/JS content library document.
Notes/Comments

For example:

Account:06950000002zmNNAAY;
Some_Custom_Object__c:06950000002PSGMAA4;

NameEnable pull-to-refresh on object detail screens

Key

pulsar.layout.enablePullToRefresh

Value

Comma, semicolon, or newline separated list of <object API Name>

Default Value (if any)

None.  However, by default, if this setting does not exist, all objects are enabled.
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

The pull-to-refresh feature allows users to drag the object detail screen down and when released, to perform a quick sync if the user is online. This type of sync refreshes the current object from the server, refreshes all records referenced in lookup fields, and syncs down any child records for the object.  In addition, any offline records associated with the current object are pushed to the server.  If any issue is encountered during pull-to-refresh, the user is prompted to instead run a normal sync so that they can resolve.

If you would like to enable users to perform a pull-to-refresh gesture only for certain objects, specify this setting with that object list.

All objects are enabled for pull-to-refresh:

  • If this setting does not exist, or
  • If this setting does exist, and the word "all" is the only value.

To disable this feature for all objects, specify the setting and leave the value empty.

NameEnable "Flattened" Picklist Style (new with Pulsar 3.9+)

Key

pulsar.layout.enableFlattenedPicklistStyle

Value

TRUE or FALSE

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description




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

Key

pulsar.layout.hideRelatedListAddButton

Value

New line separated values of the following pattern

ParentOjectName ParentObjectName : Record Type Developer Name : Related List Name

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Use this option to hide the + button on any related list against a parent object.
Notes/Comments

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.hideRelatedListDeleteButton

Value

New line separated values of the following pattern

ParentOjectName ParentObjectName : Record Type Developer Name : Related List Name

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Use this option to hide the Delete button on any related list against a parent object.
Notes/Comments

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.hideEditButton

Value

New line separated values of the following pattern

ParentOjectName ParentObjectName:Record Type Developer Name

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

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, 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.<object_API_name>.<Record Typer Developer Name>.<field_API_name>.whereClause

Value

DEFAULT{

Action=SetResult;

Result=<field filter>;

}

Default Value (if any)

N/A
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This Setting can be used to filter lookup fields as defined on Salesforce
Notes/Comments

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
Quick Action display upon create  (new with Pulsar 3.9+)
Anchor
pulltorefresh
pulltorefresh
Enable Pull to Refresh

Key

pulsar.layout.enablePullToRefresh

Value

A list of object types separated by newlines

Default Value (if any)

all
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

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.

enableQuickActionCreateDisplay

enableFlattenedPicklistStyle

Value

TRUE or FALSE

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Setting this to TRUE enables the display of an object that was just created by a Quick Action.

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

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 Available in Pulsar 9.0+