Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.




 
 
NameTop Level List View Fields

Key

pulsar.<sobjectAPIName>.topLevelList.fields

Value

Comma separated API names of the fields. Fields can be specified with labels, optionally, like this:    FieldAPIName;FieldLabel

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Changes the fields for the default list view which is normally based on the default SF search layout.  The format is a comma or newline separated API names of the fields, with optional field label specification using a semicolon (;). If this setting is specified, it will replace the search layout, but it is possible to only modify some of the fields in the search layout, leaving the others intact. The '-'  (dash) character can be used to indicate a placeholder for the original search layout field. See the examples below. 
Notes/Comments

  

  1. Replace all search layout fields with 3 other fields-                            field1, field2, field3
  2. Replace all search layout fields with 3 fields, 2 having labels-           field1;field 1 label, field2, field3;fieldlabel 3
  3. Replace all search layout fields except the second and third one-    field1, -, -, field4     




 
 
NameTop Level List View Filters

Key

pulsar.<sobjectAPIName>.topLevelList.filters

Value

Comma separated API names of the fields

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Changes the filter fields in the list view. You can setup up to two filters for each list view. Please see the enhanced version of this setting below. Please note that if that setting is specified, it overrides this one.
Notes/Comments Status__c, Pricebook2Id 




 
 
NameTop Level List View Filters (Enhanced)

Key

pulsar.<sobjectAPIName>.topLevelList.filters.whereClause

Value

Newline separated values of filter fields with optional where clauses

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Changes the filter fields in the list view. You can setup up to two filters for each list view. This enhanced version of the setting allows you to specify a where clause (if necessary) for a reference (lookup) field.  Each filter should be on its own line. The format of the filter line is as follows:  <Field API Name> : <SQL Where clause without the 'WHERE' keyword>.  Please note that if this setting is specified, it takes precedence over the non enhanced filter setting above.
Notes/CommentsExample (note each filter on its own line with the 2nd filter specifying that only active Pricebooks should be presented as filter selections):
Status__c
Pricebook2Id : IsActive = 'TRUE'




 
 
NameContains Search Fields

Key

pulsar.<sobjectAPIName>.topLevelList.containsSearchFields

Value

Comma separated API names of the fields

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

If the list view of a particular object contains a reference to another object, by default that field is not searchable (for DB performance reasons). You can use this setting to enable reference field search on the list view.

Notes/Comments




 
 
NamePrevent User from Deleting a Document (On Device Only)

Key

pulsar.docs.enableDeleteLocal

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

By default, a user may swipe a row to unhide the document delete button.  When the user presses the delete button, the document is only deleted from the device and does not have any effect on the server.  After deleting a document, a user may download the document again from the Document Updates screen.  This setting can disable the delete button from displaying when set to FALSE.
Notes/Comments




 
 
NameHide the Address Book button

Key

pulsar.toplevellist.hideAddressbookButton

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Some customers find the button really useful, so their users can import their personal contacts into Salesforce but some prefer not to display the icon. So we give you the choice to display the icon or not. .
Notes/Comments




 
 
NameEnable business card scan feature

Key

pulsar.toplevellist.showCardScannerButton

Value

TRUE / FALSE

Default Value (if any)

FALSE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

With the premium version of Pulsar, you will have the option to enable this feature. Once you have the setting, the scan icon would be displayed on Lead and Contact list views and users can use that to scan business cards and create leads or contacts. 
Notes/Comments



...


 

 
NameShow the 'Recent' records listview

Key

pulsar.listviews.recentView.enabled

Value

TRUE / FALSE

Default Value (if any)

TRUE
Compatibility
  •  iOS
  •  Windows
  •  Android

Description

By default, Pulsar includes an additional listview for every object named 'Recent'. This listview shows only records accessed from that device since the first sync. You may specify this setting with a value of FALSE to hide this listview.
Notes/CommentsThis listview represents records accessed from this device only and not any records accessed via the Salesforce website.

...


 

 
NameReference field filters for create/edit

Key

pulsar.<sobjectAPIName>.<sobjectFieldName>.whereClause

pulsar.<sobjectAPIName>.<recordTypeDevName>.<sobjectFieldName>.whereClause

...

Value

PSL that returns a result string via SetResult action

Default Value (if any)


Compatibility
  •  iOS
  •  Windows
  •  Android

Description

Choosing a value for a reference/lookup field when creating/editing an object may by default require the user to navigate a very large selection of choices (depending on the size of

your

the data set

for that referenced object

).  This Pulsar Setting allows

setting

running a specific PSL filter to constrain the user's choices.

The value returned by the final SetResult should be in the form of an arbitrarily complex SQL WHERE clause.

Notes/Comments

In the following example, the Bar__c reference field of the imagine a SomeCustomObj__c object is constrained by the value of the Foowith an AccountLookup__c field in SomeCustomObj__creference field (referring to the Account object).

In this example the filter is returned as "FooId, choosing a value for the AccountLookup__c reference field will be constrained accounts owned by the current user, with WHERE clause : Owner = '%%FooId%%'".  This assumes that the object referenced by Bar__c has itself a %%CurrUserId%%'


Paste code macro
titlepulsar.SomeCustomObj__c.BarAccountLookup__c.whereClause
DEFAULT
{
Action=SetVar;
VarName=FooIdCurrUserId;
VarValue=Foo__c@@CurrentUserId;
|
Action=SetResult;
Result=FooId__cOwner = '%%FooId%%%%CurrUserId%%';
}