...
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 |
|
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/Comments | Lead:Default:CuriumAutoAssigned Task:Default:CuriumEmailSent |
Name | Attachment Image Quality |
---|---|
Key | pulsar.attachment.ImageQuality |
Value | Integer numeric value (between 0 - 100) |
Default Value (if any) | 100 |
Compatibility |
|
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 |
Name | Attachment Max Side Pixels |
---|---|
Key | pulsar.attachment.maxSidePixels |
Value | Integer numeric value |
Default Value (if any) | 1024 |
Compatibility |
|
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/Comments | 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. |
Name | Attachment Thumbnail Max Side Pixels |
---|---|
Key | pulsar.attachment.thumbnailMaxSidePixels |
Value | Integer numeric value |
Default Value (if any) | 50 |
Compatibility |
|
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/Comments | Range for this setting is 32 - 512 pixels |
Name |
---|
Key
pulsar.<object API Name>.enableReferenceLookupShortcut
Value
Default Value (if any)
- iOS
- Windows
- Android
Description
Name | Barcode Valid Formats/Symbologies for Scanning |
---|---|
Key |
|
Value | Any number of the following terms separated by commas, semicolons, and/or newlines.
|
Default Value (if any) | None – uses the default formats/symbologies native to the platform |
Compatibility |
|
Description | NOTE:
|
Name | Show Hidden Layout Section Headers |
---|---|
Key | pulsar.layout.showHiddenSections |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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). |
Name | Override an object's name field |
---|---|
Key | pulsar.<object API name>.nameField |
Value | <field API name> |
Default Value (if any) | |
Compatibility |
|
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 |
Name | Define the currency locale for a single currency org |
---|---|
Key | pulsar.singleCurrencyOrg.locale |
Value | <a locale identifier> |
Default Value (if any) | |
Compatibility |
|
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. |
Name | Load Objects as HTML document |
---|---|
Key | pulsar.layout.loadAsHTML.objects |
Value | Comma, semicolon, or newline separated list of <sobjectType>:<contentDocumentId> |
Default Value (if any) | |
Compatibility |
|
Description | From the specified Object List Page, this will load the specified HTML/JS content library document. |
Notes/Comments | For example: Account:06950000002zmNNAAY; |
Name | Enable 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 |
|
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:
To disable this feature for all objects, specify the setting and leave the value empty. |
Name | Enable "Flattened" Picklist Style (new with Pulsar 3.9+) |
---|---|
Key | pulsar.layout.enableFlattenedPicklistStyle |
Value | TRUE or FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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.
|
Name | Hide 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 |
|
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 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. |
Name | Hide 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 |
|
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 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. |
Name | Hide 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 |
|
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 If you specify Default:Default, it will hide the Edit button on all object records. |
Name | Field 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 |
|
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'; } |
Name | Show Online Status Button on List View and Record Detail View |
---|---|
Key | pulsar.enableOnlineStatusForListAndDetail |
Value | TRUE or FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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 |