| Name | Enable Server List Views |
|---|---|
Key | pulsar.sync.enableListViews |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | This setting will read and reflect the list views you have set up on the server. |
| Notes/Comments |
| Name | Top Level List View Fields |
|---|---|
Key | pulsar.objectAPIName.topLevelList.fields |
Value | Comma separated API names of the fields. Fields can be specified with labels, optionally, like this: FieldAPIName;FieldLabel |
Default Value (if any) | |
| Compatibility |
|
Description | Changes the fields for the default list view which is normally based on the default SF search layout. The format is a comma or newline separated API names of the fields, with optional field label specification using a semicolon (;). If this setting is specified, it will replace the search layout, but it is possible to only modify some of the fields in the search layout, leaving the others intact. The '-' (dash) character can be used to indicate a placeholder for the original search layout field. See the examples below. |
| Notes/Comments |
|
| Name | Top Level List View Filters |
|---|---|
Key | pulsar.objectAPIName.topLevelList.filters |
Value | Comma separated API names of the fields |
Default Value (if any) | |
| Compatibility |
|
Description | Changes the filter fields in the list view. You can setup up to two filters for each list view. Please see the enhanced version of this setting below. Please note that if that setting is specified, it overrides this one. |
| Notes/Comments | Status__c, Pricebook2Id |
| Name | Top Level List View Filters (Enhanced) |
|---|---|
Key | pulsar.objectAPIName.topLevelList.filters.whereClause |
Value | Newline separated values of filter fields with optional where clauses |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | Changes the filter fields in the list view. You can setup up to two filters for each list view. This enhanced version of the setting allows you to specify a where clause (if necessary) for a reference (lookup) field. Each filter should be on its own line. The format of the filter line is as follows: <Field API Name> : <SQL Where clause without the 'WHERE' keyword>. Please note that if this setting is specified, it takes precedence over the non enhanced filter setting above. |
| Notes/Comments | Example (note each filter on its own line with the 2nd filter specifying that only active Pricebooks should be presented as filter selections): Status__c Pricebook2Id : IsActive = 'TRUE' |
| Name | Contains Search Fields |
|---|---|
Key | pulsar.objectAPIName.topLevelList.containsSearchFields |
Value | Comma separated API names of the fields |
Default Value (if any) | |
| Compatibility |
|
Description | If the list view of a particular object contains a reference to another object, by default that field is not searchable (for DB performance reasons). You can use this setting to enable reference field search on the list view. |
| Notes/Comments |
| Name | Prevent User from Deleting a Document (On Device Only) |
|---|---|
Key | pulsar.docs.enableDeleteLocal |
Value | TRUE / FALSE |
Default Value (if any) | TRUE |
| Compatibility |
|
Description | By default, a user may swipe a row to unhide the document delete button. When the user presses the delete button, the document is only deleted from the device and does not have any effect on the server. After deleting a document, a user may download the document again from the Document Updates screen. This setting can disable the delete button from displaying when set to FALSE. |
| Notes/Comments |
| Name | Prevent User from Removing a Document from Recent Document List |
|---|---|
Key | pulsar.docs.enableDeleteRecent |
Value | TRUE / FALSE |
Default Value (if any) | TRUE |
| Compatibility |
|
Description | By default, a user may swipe a row on the Recent Documents screen to unhide the delete recent item button. When the user presses the delete button, the document is removed from the recent list, but it still exists on the device. This setting can disable that delete button from displaying when set to FALSE. |
| Notes/Comments |
| Name | Hide the Done button on the custom HTML Page |
|---|---|
Key | pulsar.docs.hideDoneButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | By default, a user can click on the Done button to close the custom HTML page and get back to Pulsar Home Page or a Pulsar record screen. In some cases, customers would like to hide the done button on that page. This setting will let enable that behavior. |
| Notes/Comments |