| Name | Top Level List View Filters |
|---|---|
Key | pulsar.<sobjectAPIName>.topLevelList.filters.whereClause |
Value | Newline separated values of filter fields with optional where clauses |
Default Value (if any) | Account Contact Opportunity Lead |
| 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. |
| 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.<sobjectAPIName>.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 | Hide the Search Bar |
|---|---|
Key | pulsar.<sobjectAPIName>.toplevellist.hideSearchbar |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | Administrators use this setting to prevent free text search of particular list views, forcing the user to use the filters only. |
| Notes/Comments |
| Name | Hide the Create Button |
|---|---|
Key | pulsar.<sobjectAPIName>.toplevellist.hideCreateButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | Administrators use this setting to override the user's permission so that they are unable to add records from the object's main list view. Note that a setting of 'false' will not grant the user access to create records if they are currently unable to do so on the Salesforce Web UI. |
| Notes/Comments |
| Name | Show the 'Recent' records listview |
|---|---|
Key | pulsar.listviews.recentView.enabled |
Value | TRUE / FALSE |
Default Value (if any) | TRUE |
| Compatibility |
|
Description | By default, Pulsar includes an additional listview for every object named 'Recent'. This listview shows only records accessed from that device since the first sync. You may specify this setting with a value of FALSE to hide this listview. |
| Notes/Comments | This listview represents records accessed from this device only and not any records accessed via the Salesforce website. |
| Name | Reference field filters for create/edit |
|---|---|
Key | pulsar.<sobjectAPIName>.<sobjectFieldName>.whereClause pulsar.<sobjectAPIName>.<recordTypeDevName>.<sobjectFieldName>.whereClause ... |
Value | PSL that returns a result string via SetResult action |
Default Value (if any) | |
| Compatibility |
|
Description | Choosing a value for a reference/lookup field when creating/editing an object may by default require the user to navigate a very large selection of choices (depending on the size of the data set). This Pulsar Setting allows running a specific PSL filter to constrain the user's choices. The value returned by the final |
| Notes/Comments | In the following example, imagine a In this example, choosing a value for the |
| Name | Show the ListView selector when selecting objects to fill lookup fields |
|---|---|
Key | pulsar.listViews.enableReferenceListViewSelector |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | When enabled, this setting allows the user to use any of the available ListViews when selecting an object for a lookup field. |
| Notes/Comments | This listview represents records accessed from this device only and not any records accessed via the Salesforce website. |
| Name | Enable the Option to Perform Online Searches in Object and Reference ListViews |
|---|---|
Key | pulsar.search.enableOnlineSearchOption |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
| Compatibility |
|
Description | New to version 5.0: This functionality adds the ability to fetch records that may not be synced on a user's device. When enabled, this option adds a button titled "Click here to search online" to the end of Object and Reference ListViews. If selected, any subsequent searches will be performed against SFDC's servers using a SOSL query. If any record is selected from an online search, that record will be integrated into the device's database using single-object sync (the same functionality that underlies pull-to-refresh). |
| Notes/Comments | Any queries made with online search currently disregard the currently selected PickList and any applied filters - all records are searched. Only 10 records are returned. Salesforce Object Search Language (SOSL) is a search language that is used to perform text searches in records against any applicable text field. More information can be found here: https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_sosl_intro.htm |