Miscellaneous Settings




 
 
NameDefault Email Signature

Key

pulsar.email.defaultsignature

Value

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

Default Value (if any)

Sent by Pulsar for Salesforce.<br>http://www.luminixinc.com"
Compatibility
  • iOS
  • Windows
  • Android

Description

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




 
 
NameHide Advanced Settings Button

Key

pulsar.settings.hideAdvancedSettings

Value

TRUE/FALSE

Default Value (if any)

 FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

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




 
 
NameEmail recipient(s) for Pulsar Logs

Key

pulsar.logs.email

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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




 
 
NameCC Email for Pulsar Logs

Key

pulsar.logs.email.cc

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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




 
 
NameRequire a password to use logs Button

Key

pulsar.password

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments




 
 
NameDisable device calendar events

Key

pulsar.calendar.disableDeviceCalendar

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

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




 
 
NameChange the color of Salesforce events

Key

pulsar.calendar.event.sfcolor

Value

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

Default Value (if any)


Compatibility

Pulsar v12 +

  • iOS
  • Windows
  • Android

Description

Change the default color of the Salesforce events displayed in your calendar
Notes/Comments

For example : 0,127,255

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



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

Key

pulsar.event.sfcolor.field

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

Changes the color of the Salesforce events displayed in your calendar based on the value of the field specified.
Notes/CommentsFor example : Subject




 
 
NameColors of Salesforce events keyed by Event object field values

Key

pulsar.event.sfcolor.valuesToColors

Value

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

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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

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




 
 
NameDisable/Enable Salesforce Event Creation from MyDay

Key

pulsar.event.enableCreatesFromMyDay

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

Additional control on SF event creation.
Notes/Comments

 
 
NameDefault Event Length

Key

pulsar.calendar.defaultEventLength

Value

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

Default Value (if any)

When left unset, this value is considered to be 60 minutes.
Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments


 

 
NameSFDC Link Button Action

Key

pulsar.buttonActions.SObject.Your Title

Value

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;

}

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/CommentsMultiple button actions for same SObject is supported. See Also : OpenURL PSL Action.


 
 
NameAndroid Web View Acceleration

Key

pulsar.webViewAcceleration.android

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

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.
Notes/Comments


 
 
NameLocation Services Timeout

Key

pulsar.location.timeout

Value

number of seconds to wait for location

Default Value (if any)

5
Compatibility

Pulsar v12 +

  • iOS
  • Windows
  • Android

Description

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




 
 
NameLocation 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 +

  • iOS
  • Windows
  • Android

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




 
 
NameCustom Database Indexes

Key

pulsar.customIndexes

Value


Default Value (if any)


Compatibility

Pulsar v12 +

  • iOS
  • Windows
  • Android

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):
<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:

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.