Miscellaneous Settings

Default Log Level

pulsar.loglevel

Plain text. One of the following:

info

warn

error

debug

Verbose

info

Specify the log level you wish to appear in the Pulsar log. The available levels are:

• "info" - The default level. Logs will include the "[INFO]" tag 

• "warn" - Logs will include the "[WARN]" tag 

• "error" - Logs will include the "[ERROR]" tag 

• "debug" - Logs will include the "[DEBUG]" tag and will only appear when debug logging has been turned on in Pulsar

• "Verbose" - Extra debug-level information will appear in the logs.

Default Email Signature

pulsar.email.defaultsignature

Plain text. Can be rich-formatted using HTML. Images not supported at this time.

Sent by Pulsar for Salesforce.<br>http://www.luminixinc.com"

Change the default email signature for outgoing mail from the app. (This currently applies mainly to content library documents sent from the app).

Hide Advanced Settings Button

pulsar.settings.hideAdvancedSettings

TRUE/FALSE

 FALSE

When this setting is enabled, the settings page within Pulsar app will not display the Advanced Settings button for the user.

Email recipient(s) for Pulsar Logs

pulsar.logs.email

comma-, semi-colon-, or newline-separated list of email addresses

When this setting is enabled, the email the user is sending will be sent to the email address(es) specified

CC Email for Pulsar Logs

pulsar.logs.email.cc

comma-, semi-colon-, or newline-separated list of email addresses

When this setting is enabled, a copy of the email the user is sending will be sent to the email address specified

Require a password to use logs Button

pulsar.password

TRUE / FALSE

FALSE

When this setting is enabled, the settings page within Pulsar app will prompt the user to enter a passcode before the logs will be displayed for them. Some institutions only want the admin users to be able to send us logs and this is a way to work with that.

Disable device calendar events

pulsar.calendar.disableDeviceCalendar

TRUE / FALSE

TRUE

Some users would only like to see SFDC events and not the Exchange/Gmail and other calendars, so managing events is easier for them.

Change the color of Salesforce events

pulsar.calendar.event.sfcolor

An R,G,B color tuple with values between 0-255

Pulsar v12 +

Change the default color of the Salesforce events displayed in your calendar

For example : 0,127,255

Deprecated: key value for Pulsar < v12 =  `pulsar.event.sfcolor`

Change the color of Salesforce events based on an Event object field

pulsar.event.sfcolor.field

The name of a field in the Event object.  To be used in conjunction with pulsar.event.sfcolor.valuesToColors

Changes the color of the Salesforce events displayed in your calendar based on the value of the field specified.

For example : Subject

Colors of Salesforce events keyed by Event object field values

pulsar.event.sfcolor.valuesToColors

key : R,G,B values separated by newlines.  To be used in conjunction with pulsar.event.sfcolor.field

Changes the colors of the Salesforce events displayed in your calendar based on the value of the field specified.

For example if you specified pulsar.event.sfcolor.field to be Subject , the color will be set if the value of the Subject field matches the keys :

Email : 255,0,0
Phone call : 0,128,128
Meeting : 0,127,255

Disable/Enable Salesforce Event Creation from MyDay

pulsar.event.enableCreatesFromMyDay

TRUE / FALSE

TRUE

Additional control on SF event creation.

Default Event Length

pulsar.calendar.defaultEventLength

An integer number of minutes between 15 and 240. Anything outside this range will be corrected to the min or max value

When left unset, this value is considered to be 60 minutes.

This value defines the default length of a new Salesforce event object when created through Pulsar. The value is an integer and defines the length in minutes of the meeting.

SFDC Link Button Action

pulsar.buttonActions.SObject.Your Title

Custom PSL. For example :

DEFAULT{
Action=SetVar;
VarName=ObjId;
VarValue=Id;
|
Action=sLink;
Values=https://[SalesforceApiServer].my.salesforce.com/apex/PulsarSettingsManager?accId=%%ObjId%%&sfdc.tabName=01r50000000VWXz;
OpenInExternalBrowser=False;
}

A Button Action icon will appear in the bottom toolbar for the given SObject detail page. When clicked, you will be able to choose Your Title from a popup menu which will trigger the sLink PSL and open an SFDC page in an embedded web browser.

Multiple button actions for same SObject is supported. See Also : OpenURL PSL Action.

Android Web View Acceleration

pulsar.webViewAcceleration.android

TRUE / FALSE

TRUE

By default, Pulsar will use hardware acceleration (if supported by the device) to render embedded web views.  If this is causing problems with your embedded HTML pages, you may choose to set this to FALSE at the cost of slower web view rendering.

Location Services Timeout

pulsar.location.timeout

number of seconds to wait for location

5

Pulsar v12 +

Maximum amount of seconds to wait for location services on the device to return a response.

Location Services Cache Frequency

pulsar.location.updateFrequencySeconds

number of seconds to wait between actual queries of device location

0

Pulsar v12 +

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.

Custom Database Indexes

pulsar.customIndexes

Pulsar v12 +

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):
<object-name> ; <indexed-column> [, ...]

indexed-column:
<column-name>[:[<collation>][:<ordering>]]

collation options: binary (default), nocase, rtrim

ordering options: asc (default), desc

Examples:

Creating three custom indexes with varying number of fields and options:

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.

Additional FTS Searchable Fields

pulsar.search.<sobject type>.searchableFields

Comma or New Line separated list of field api names

Pulsar v14 +

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
Value:  FTS_search_field__c