Page Comparison

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

Replace all search layout fields with 3 other fields- field1, field2, field3

Replace all search layout fields with 3 fields, 2 having labels- field1;field 1 label, field2, field3;fieldlabel 3

Replace all search layout fields except the second and third one- field1, -, -, field4


Name	Top Level List View Filters
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/Comments	Example (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'


Name	Contains 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

Default Value (if any)


Name	Prevent 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

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


Name	Hide the Search Bar
Key	pulsar.<sobjectAPIName>.toplevellist.hideSearchbar
Value	TRUE / FALSE
Default Value (if any)	FALSE
Compatibility	iOS Windows Android
Description	Administrators use this setting to prevent free text search of particular list views, forcing the user to use the filters only.
Notes/Comments


Name	Filter records shown in the list views by a where clause
Key	pulsar.<sobjectAPIName>.toplevellist.whereClause
Value	SQLIte syntax for where clause
Default Value (if any)
Compatibility	iOS Windows Android
Description	Administrators use this setting, so their users only see the records filtered by additional criteria
Notes/Comments	(date('now') <= Survey_End_Date__c)

NameDefine a default sort order for an object's list view

Key

pulsar.<sobjectAPIName>.toplevellist.DefaultSortOrder

Value

SQLITE syntax for ORDER BY clauses.. for example:

Key: pulsar.task.toplevellist.defaultsortorder
Value: ActivityDate DESC, Subject ASC

Default Value (if any)

Compatibility

iOS
Windows
Android

Description

Administrators use this setting, so their users only see the records filtered by additional criteriaNotes/Comments

...

)

...

Key

...

Value

...

Default Value (if any)

...

iOS
Windows
Android

...

Description

...


Name	Always show the 'All' records listview
Key	pulsar.listviews.allRecordsView.alwaysEnabled
Value	TRUE / FALSE
Default Value (if any)	TRUE
Compatibility	iOS Windows Android
Description	By default, Pulsar includes an additional listview for every object list named 'All'. This listview shows all records downloaded for the object. You may specify this setting with a value of FALSE to hide this listview and only present the user with the listviews that are defined via SFDC.
Notes/Comments	Note that this listview will still be shown regardless of this setting for those objects where no defined listviews were found.

...


Name	Show 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/Comments	This listview represents records accessed from this device only and not any records accessed via the Salesforce website.

...

Name Reference 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 the data set). This Pulsar Setting allows 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, imagine a SomeCustomObj__c object with an AccountLookup__c reference field (referring to the Account object).

In this example, choosing a value for the AccountLookup__c reference field will be constrained accounts owned by the current user, with WHERE clause : Owner = '%%CurrUserId%%'

Paste code macro

title	pulsar.SomeCustomObj__c.AccountLookup__c.whereClause

DEFAULT
{
Action=SetVar;
VarName=CurrUserId;
VarValue=@@CurrentUserId;
|
Action=SetResult;
Result=Owner = '%%CurrUserId%%';
}

...

Versions Compared

Old Version 13

New Version 14

Key