...
| Name | Location Services Timeout |
|---|---|
Key | pulsar.location.timeout |
Value | number of seconds |
Default Value (if any) | 5 |
| Compatibility | Pulsar v12 +
|
Description | Maximum amount of seconds to wait for location services on the device to return a response. |
| Notes/Comments |
...
| 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. |
...