Versions Compared

Old Version 64

changes.mady.by.user geevall

Saved on

compared with

New Version 65

changes.mady.by.user geevall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


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



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/CommentsTo 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.



NameShow Hidden Layout Section Headers

Key

pulsar.layout.showHiddenSections

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  •  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).




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;




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

Enable "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

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)



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

Key

pulsar.layout.hideRelatedListAddButton

Value

New line separated values of the following pattern

ParentOjectName : 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 : 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: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>.<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';

}




NameShow Online Status Button on List View and Record Detail View

Key

pulsar.enableOnlineStatusForListAndDetail

Value

TRUE or FALSE

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

This setting is used to display the Online Status Button on the Record Detail View and List Views. Enabling this setting will allow the user to start a sync from these locations, which may affect the data displayed on those same screens, potentially causing confusion.
Notes/Comments