Versions Compared

Old Version 7

changes.mady.by.user Fernando Rodriguez

Saved on

compared with

New Version Current

changes.mady.by.user Fernando Rodriguez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
 
 
NameTop Level List View Fields

Key

pulsar.objectAPIName.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     



     
     
    NameTop Level List View Filters

    Key

    		pulsar.
    objectAPIName
    <sobjectAPIName>.topLevelList.filters.whereClause

    Value

    Comma
    Newline separated
    API names
    values of
    the
    filter fields with optional where clauses
     
     
    NameTop Level List View Filters (Enhanced)

    Key

    		pulsar.objectAPIName.topLevelList.filters.whereClause

    Value

    		Newline separated values of filter fields with optional where clauses

    Default Value (if any)

    		FALSE

    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 

    Account
    ====
    Type

    Contact
    ====
    AccountId

    Opportunity
    ====
    AccountId, StageName

    Lead
    ====
    Company, Status

    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'



    Notes/Comments
     
     
    NameContains Search Fields

    Key

    		pulsar.objectAPIName<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)

    TRUECompatibility
    •  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.

    For performance reasons, Pulsar optimizes search for "prefix" terms. Pulsar breaks down text contained in record data based on alphanumeric and whitespace boundaries, and then further breaks apart individual terms focusing on the beginning of the term.

    For example: if you are searching for a record containing "Supremecourt-Exhibit-XYZ1234" you might be able to search for the following terms successfully: "sup", "supreme", "supremeCourt", "Ex", "exhib", "Exhibit", "XY", "xyz", "XYZ1234", "SUPREMECOURT-EX", etc.

    The following search terms (each contained within the target text) could NOT be used to find the record: "reme", "court", "hib", "Z12", "1234", or even "ourt-Exhibit-XYZ1234"

    This setting allows you to specify a set of fields on an object for which full "contains" search will work. 

    Notes/Comments

    This does not include searches for referenced objects on any specific record. The reason is that searches are limited to the table shown in the corresponding Listview. For example, the AccountId field on Contact records only contains text data that looks like the following: "001Abc000000deFGHI", and even though Pulsar will display the Name of the record this represents, the search engine only sees the actual text in the records.




     
     
    NameHide 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
    Enable business card scan feature
    Hide the Create Button

    Key

    		pulsar.<sobjectAPIName>.toplevellist.
    showCardScannerButton
    hideCreateButton

    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. 
    Administrators use this setting to override the user's permission so that they are unable to add records from the object's main list view.  Note that a setting of 'false' will not grant the user access to create records if they are currently unable to do so on the Salesforce Web UI.
    Notes/Comments


    ...



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


    ...


    ...

    Value

    ...


     
     
    Name

    ...

    Key

    ...

      NameAllow exporting list view data in Comma Separated Values (csv) format

    Key

    pulsar.enableExport.objects

    Value

    comma or newline separated SObject API names
    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
    titlepulsar.SomeCustomObj__c.AccountLookup__c.whereClause
    DEFAULT
{
Action=SetVar;
VarName=CurrUserId;
VarValue=@@CurrentUserId;
|
Action=SetResult;
Result=Owner = '%%CurrUserId%%';
}



    ...


    Notes/Comments  

     
     
    NameShow the ListView selector when selecting objects to fill lookup fields 

    Key

    pulsar.listViews.enableReferenceListViewSelector

    Value

    		TRUE / FALSE

    Default Value (if any)

    		FALSE
    Compatibility
    •  iOS (3.4.5+)
    •  Windows
    •  Android

    Description

    Administrators use this setting, so their users will be able to export list view data to Excel or other data viewing applications
    When enabled, this setting allows the user to use any of the available ListViews when selecting an object for a lookup field.
    Notes/CommentsThis listview represents records accessed from this device only and not any records accessed via the Salesforce website.


    ...




     
    Name
    Always show the 'All' records listview
    Enable the Option to Perform Online Searches in Object and Reference ListViews

    Key

    pulsar.

    listviews

    search.

    allRecordsView.alwaysEnabled

    enableOnlineSearchOption

    Value

    		TRUE / FALSE

    Default Value (if any)

    TRUENotes/CommentsNote that this listview will still be shown regardless of this setting for those objects where no defined listviews were found.  NameShow the 'Recent' records listview

    Key

    pulsar.listviews.recentView.enabled

    Value

    TRUE / FALSE
    FALSE
    Compatibility
    •  iOS (3.4.5+)
    •  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.
    New to version 5.0: This functionality adds the ability to fetch records that may not be synced on a user's device. When enabled, this option adds a button titled "Click here to search online" to the end of Object and Reference ListViews. If selected, any subsequent searches will be performed against SFDC's servers using a SOSL query. If any record is selected from an online search, that record will be integrated into the device's database using single-object sync (the same functionality that underlies pull-to-refresh). 
    Notes/CommentsAny queries made with online search currently disregard the currently selected PickList and any applied filters - all records are searched. Only 10 records are returned.  Salesforce Object Search Language (SOSL) is a search language that is used to perform text searches in records against any applicable text field. More information can be found here: https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_sosl_intro.htm


    ...




     
    NameReference List View Filter

    Key

    pulsar.<sobjectAPIName>.<recordTypeDevName>.<relationshipAPIName>.whereClause

    Value

    		PSL that returns a result string via SetResult action

    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

    This Pulsar Setting allows you to further filter records that are displayed in a specific related list. To implement this setting, you must specify valid PSL and it should end with a SetResult PSL Action that sets the related list criteria. The value returned by the SetResult should be in the form of an arbitrarily complex SQL WHERE clause (without the 'WHERE' keyword).

    The following example returns criteria to show only records owned by the current user that are in 'Active' status.

    Paste code macro
    titlepulsar.Account.default.Contacts.whereClause
    DEFAULT
{
Action=SetVar;
VarName=CurrUserId;
VarValue=@@CurrentUserId;
|
Action=SetResult;
Result=Owner = '%%CurrUserId%%' AND Status__c = 'Active';
}


    Notes/CommentsNote: You may specify default in the place of recordTypeDevName if there are no record types or if you want it apply to all record types for the object specified in sobjectAPIName. For example, using the key 'pulsar.Account.default.Contacts.whereClause' will apply this where clause criteria to the Contacts related list for all Account record types.