Layout View Settings


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

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

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.

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;



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

Key

pulsar.layout.hideRelatedListAddButton

Value

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

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

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

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 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 Enable Flattened Picklist Style

Key

pulsar.layout.enableFlattenedPicklistStyle

Value

TRUE or FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

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

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+

Related pages