Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »



 
 
NameMain Background Color

Key

pulsar.layout.mainBackgroundColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

This setting defines the background color used for object lists and object detail screens. 
Notes/Comments




 
 
NameMain Text Color

Key

pulsar.layout.mainTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

The primary color used for text used in object lists and object detail screens. 
Notes/Comments




 
 
NameLabel Text Color

Key

pulsar.layout.labelTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

The color used for labels used in object lists and object detail screens. 
Notes/Comments




 
 
NameNavigation Title Text Color

Key

pulsar.navigation.linkTextColor

Value

The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56)

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

The color used for the text displayed on the title of the navigation bar
Notes/Comments




 
 
NameDefault To Related Lists

Key

pulsar.layout.defaultShowRelated

Value

Comma or new line separated API names of the objects for which you would like this behavior.

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

Use this option to view Related List as opposed to the Details of the object. Sometimes the parent object is just a place holder for all the related items. So this makes the navigation easier. 
Notes/Comments



 
 
NameActivity List Setting

Key

pulsar.layout.activityListItems

Value

Comma or new line separated activity items.

Default Value (if any)

Note, Attachment, Task, Event, Calendar
Compatibility
  • iOS
  • Windows
  • Android

Description

Use this option to specify what shows up under + and 'eye/view' icon
Notes/Comments



 
 
NameHide Add Activity Button

Key

pulsar.layout.hideAddActivityButton

Value

Comma or newline separated <object API name>:<RecordTypeDeveloperName> list

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

For whatever reason, if the admin wants to deny this capability. They can enable this setting.. 
Notes/Comments

ObjectAPIName1:RecordTypeName1,ObjectAPIName2:RecordTypeName2,ObjectAPIName3:RecordTypeName3

Use the word "Default" to denote that the setting applies to all of that object's record types not explicitly specified.



 
 
NameHide View Activity Button

Key

pulsar.layout.hideViewActivityButton

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

Hide view activity button.
Notes/Comments


 
 
NameHide Additional Checkbox Fields in the Layout for Case, Lead, Task and Event

Key

pulsar.layout.hiddenFields

Value

<Object API Name> : <Record Type Developer Name> : <CuriumAutoAssigned or CuriumEmailSent>

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

Just like the Salesforce.com backend, Pulsar displays the 'Use Assignment Rules' and 'Send Notification Email' checkboxes on objects that require it, i.e: CASE, LEAD, TASK, and EVENT. If the organization doesn't need to see these fields, you can hide them using this setting.  NOTE: To hide the Auto Assignment checkbox, use the field identifier 'CuriumAutoAssigned' and to hide the Send Notification Email checkbox, use the field identifier 'CuriumEmailSent'.
Notes/CommentsLead:Default:CuriumAutoAssigned
Task:Default:CuriumEmailSent

 
 
NameEnable Signature Capture

Key

pulsar.layout.enableSignatureCapture

Value

 List of Object API Name:Record Type Name

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

This will display a signature icon on the object layout that can be used to capture a quick signature.
Notes/Comments

Account:Default

Opportunity:Default


 
 
NameEnable Camera Uploads/ Enhanced Attachment Mode

Key

pulsar.attachment.enableEnhancedMode

Value

TRUE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

This will let the user take pictures right from within the app that can be attached to records as well as let them add multiple pictures from the album at the same time.
Notes/CommentsThis setting is deprecated and only works with legacy iOS Pulsar version 2.x

 
 
NameAttachment Max Side Pixels

Key

pulsar.attachment.ImageQuality

Value

Integer numeric value (between 0 - 100)

Default Value (if any)

100
Compatibility
  • iOS
  • Windows
  • Android

Description

This setting will reduce image quality in order to reduce image size. 100 would be full quality (no compression) and 0 would be full compression.

Notes/Comments

 
 
NameAttachment Max Side Pixels

Key

pulsar.attachment.maxSidePixels

Value

Integer numeric value

Default Value (if any)

1024
Compatibility
  • iOS
  • Windows
  • Android

Description

This setting will shrink image attachments along the maximum side (width in landscape or height in portrait) to the given pixel value, preserving the aspect ratio of the image.  Images with both dimensions less than the setting value will not be altered.

Notes/CommentsTo disable scaling attachments, set the value of this setting to zero (0).  Please note that unscaled image attachments can represent significant cost in terms of both storage and network sync time.

 
 
NameAttachment Thumbnail Max Side Pixels

Key

pulsar.attachment.thumbnailMaxSidePixels

Value

Integer numeric value

Default Value (if any)

50
Compatibility
  • iOS
  • Windows
  • Android

Description

Attachment thumbnail images will be generated/scaled to this value along the maximum side (width in landscape or height in portrait), preserving the aspect ratio of the image.  Thumbnails are only used within the Pulsar app for image attachments.

Notes/CommentsRange for this setting is 32 - 512 pixels

 
 
NameEnable Opportunity Product Chaining

Key

pulsar.opportunity.enableProductChaining

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

When creating an opportunity, upon pressing the Save button, Salesforce (if setup to do so) automatically navigates the user to a screen where they are prompted to add Products that are relevant to this Opportunity.
Notes/Comments

 
 
NameEnable Temporary Population of the Auto Number Name field for an object

Key

pulsar.layout.autoNumberNameFields.enableTempData

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  • iOS
  • Windows
  • Android

Description

While offline, Pulsar cannot automatically fill in an auto number field since these fields are best left sequenced by the server in a multi-user environment. However, if you have specified an auto number field for an object's name field, Pulsar will enter in some placeholder text by default. The placeholder text has this format: <object type> + " - Offline - " + <datetime object was created>  (e.g., "Account - Offline - Aug 20, 2015 11:00 AM").  This is done so that this record can be readily identified while offline.
Notes/CommentsFor example, a parent object might only display that object's name field in the related list.  After a sync, the placeholder text is replaced with a real value from the server.

 
 
NameEnable Call Logging

Key

pulsar.enableCallLogging

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

When enabled, any call initiated from within Pulsar, upon ending, will ask the user if they wish to log the previous call. Opting to do so will create a new completed Task object with the corresponding information.
Notes/Comments





NameSingle Object Lookup Shortcut

Key

pulsar.<object API Name>.enableReferenceLookupShortcut

Value

TRUE or FALSE

Default Value (if any)

None
Compatibility
  • iOS
  • Windows
  • Android

Description

When enabled for a specific object, any lookup field that references that object will skip the selection list if there is only one object available to fill. This shortcut takes into account the configured filters and where clauses for a particular object, but not any default List View filters for the object.




NameEnable barcode scan for lookup object - Match Fields

Key

pulsar.<object API Name>.barcodeLookupFields

Value

List of field API names to match with the barcode scan

Default Value (if any)

None
Compatibility
  • iOS
  • Windows
  • Android

Description

When enabled for a specific object, any lookup field that references that object will provide the option to scan a barcode when edited in Pulsar. For example for the setting with key pulsar.Account.barcodeLookupFields and value "AccountNumber, Name", Pulsar will then search the database for Accounts that have either the AccountNumber or the Name fields that exactly match the scanned barcode.



NameEnable barcode scan for lookup object - Where Clause

Key

pulsar.<object API Name>.barcodeLookupWhereClause

Value

PulsarSettings Language (PSL) to generate a valid SQL where clause

Default Value (if any)

None
Compatibility
  • iOS
  • Windows
  • Android

Description

When enabled for a specific object, any lookup field that references that object will provide the option to scan a barcode when edited in Pulsar. Once scanned, the barcode value will be available in the PSL code using the @@CurrentScanCode  special variable. The expected result of the PSL is a SQL where clause, returned using the SetResult action.



Name Skip the barcode "Next" button

Key

pulsar.<object API Name>.barcodeScanSkipNextButton

pulsar.<object API Name>.barcodeScanSkipNextButton.android

pulsar.<object API Name>.barcodeScanSkipNextButton.windows

Value

True or False

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

When enabled for a specific object, the barcode scanner will skip the 'Next' button press, and will proceed with the first valid barcode scanned.



NameBarcode Valid Formats/Symbologies for Scanning

Key

pulsar.<object API Name>.barcodeValidFormats

pulsar.<object API Name>.barcodeValidFormats.android

pulsar.<object API Name>.barcodeValidFormats.windows

Value

Any number of the following terms separated by commas, semicolons, and/or newlines.

upca , upce , ean13 , code39 , code39mod43 , ean8 , code93 , code128 , pdf417 , qr , aztec

Default Value (if any)

None – uses the default formats/symbologies native to the platform
Compatibility
  • iOS
  • Windows
  • Android

Description

NOTE:

  • upca is the same as ean13 in iOS Pulsar
  • These and additional barcode formats may or may not be supported on Windows UWP and Android depending on the scanner device.  Leaving this value as an empty string will use the default formats on UWP and Android platforms.



NameShow Hidden Layout Section Headers

Key

pulsar.layout.showHiddenSections

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  • iOS
  • Windows
  • Android

Description

By default, Pulsar honors the visibility set via SFDC for section headers defined on an object's layout. Specify this setting and assign it a TRUE value in order to override and show all hidden section headers. 
Notes/CommentsFeature as of Pulsar version 2.5.9 (101).





NameOverride an object's name field

Key

pulsar.<object API name>.nameField

Value

<field API name>

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

An object's name field is the field displayed for reference fields on another (related) object's layout. For example, on the Contact object layout, the Account field is a reference field that displays the text from the Account Name field. Specify this setting with a valid field to change what Pulsar will use as the display text for reference fields.
Notes/Comments

Feature as of Pulsar version 2.5.9 (100).

For most objects, the name field is literally the 'Name' field, but for some standard objects it is something different (e.g., Subject for Task/Event). Please note that for the Case object, Pulsar uses the Subject field by default instead of the CaseNumber field. To change this to mimic Salesforce, create this setting:

key: pulsar.Case.nameField
value: CaseNumber




NameDefine the currency locale for a single currency org

Key

pulsar.singleCurrencyOrg.locale

Value

<a locale identifier>

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

The locale identifier is expected to be in the form of: a 2 character language descriptor (ISO 639-1), followed by an underscore, followed by a 2 character region descriptor (ISO 3166-1). For example, the locale identifier for the continental United States is: en_US
Notes/Comments

Salesforce does not provide an API to determine what the currency locale is for a single currency org. If this setting is not specified, the locale for currency will instead be based on the user's locale as defined in Salesforce.





NameLoad Objects as HTML document

Key

pulsar.layout.loadAsHTML.objects

Value

Comma, semicolon, or newline separated list of <sobjectType>:<contentDocumentId>

Default Value (if any)


Compatibility
  • iOS
  • Windows
  • Android

Description

From the specified Object List Page, this will load the specified HTML/JS content library document.
Notes/Comments

For example:

Account:06950000002zmNNAAY;
Some_Custom_Object__c:06950000002PSGMAA4;


  • No labels