...
| Name | Location Services Cache Frequency |
|---|---|
Key | pulsar.location.updateFrequencySeconds |
Value | number of seconds to wait between actual queries of device location |
Default Value (if any) | 0 |
| Compatibility | Pulsar v12 +
|
Description | Default 0 (seconds), which means that Pulsar will always query the device location services when requested (via PSL, JSAPI, etc), which may be a time-consuming operation. Use this Pulsar Setting to tune the trade off between accuracy/speed. With a setting value > 0, Pulsar will use the last location if it was queried less than that number of seconds ago. |
| Notes/Comments |
...
| Name | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
| Name | Custom Database Indexes | ||||||
Key | pulsar.customIndexes | ||||||
Value | |||||||
Default Value (if any) | |||||||
| Compatibility | Pulsar v12 +
| ||||||
Description | Pulsar automatically creates database (sqlite) indexes on Id/Reference fields in addition to fields shown on synced object list views. To create additional indexes, use this setting and specify as many indexes as necessary using one index per line. Each index contains an object api name, a semicolon, and a list of comma-separated fields. The list of fields may be a single field or be multiple fields. Each field may also be specified with collation and ordering options with each option separated by colons. Individual index format (for single and multiple column index): indexed-column: collation options: binary (default), nocase, rtrim ordering options: asc (default), desc Examples: Creating three custom indexes with varying number of fields and options:
| ||||||
| Notes/Comments | If specifying ordering but not specifying collation for a field, you must still include the collation colon (:) as a placeholder. If not specifying options, the defaults noted above are used. If there is any parsing issue or if an object or field does not exist, then the index will be skipped. To confirm that your custom indexes have been created, you can navigate to Pulsar's sqlite area and run a command similar to: select sql from sqlite_master where type = 'index' and tbl_name = '<object api name>' When modifying an existing custom index that has been already created, the previous index will be dropped and the new one added. | ||||||
...
| |||||||
|---|---|---|---|---|---|---|---|
| Name | Additional FTS Searchable Fields | ||||||
Key | pulsar.search.<sobject type>.searchableFields | ||||||
Value | Comma or New Line separated list of field api names | ||||||
Default Value (if any) | |||||||
| Compatibility | Pulsar v14 +
| ||||||
Description | Pulsar automatically indexes non reference fields for Full Text Search (FTS) if they are included on any listview downloaded by Pulsar. This setting may be used to include additional fields for FTS that exist in the object schema but not on any synced listview. Example: Key: pulsar.search.Custom_Object__c.searchableFields | ||||||
| Notes/Comments |
...