Name | Main 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 |
|
Description | This setting defines the background color used for object lists and object detail screens. |
Notes/Comments |
Name | Main 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 |
|
Description | The primary color used for text used in object lists and object detail screens. |
Notes/Comments |
Name | Label 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 |
|
Description | The color used for labels used in object lists and object detail screens. |
Notes/Comments |
Name | Navigation 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 |
|
Description | The color used for the text displayed on the title of the navigation bar |
Notes/Comments |
Name | Section list and related list selection screen text color |
---|---|
Key | pulsar.layout.splitMasterTextColor |
Value | The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56) |
Default Value (if any) | |
Compatibility |
|
Description | The color used for labels used in section and related list selection screens. |
Notes/Comments |
Name | Section list and related list selection screen background color |
---|---|
Key | pulsar.layout.splitMasterBackgroundColor |
Value | The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56) |
Default Value (if any) | |
Compatibility |
|
Description | The background color used in section and related list selection screens. |
Notes/Comments |
Name | Section list and related list selection screen highlighted text color |
---|---|
Key | pulsar.layout.splitMasterHighlightedTextColor |
Value | The RGB color code specified as 3 comma separated numbers. (e.g: 71,43,56) |
Default Value (if any) | |
Compatibility |
|
Description | The highlighted text color used in section and related list selection screens. |
Notes/Comments |
Name | Default 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 |
|
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 |
Name | Activity List Setting |
---|---|
Key | pulsar.layout.activityListItems |
Value | Comma or new line separated activity items. |
Default Value (if any) | Note, Attachment, Task, Event, Calendar |
Compatibility |
|
Description | Use this option to specify what shows up under + and 'eye/view' icon |
Notes/Comments |
Name | Hide Add Activity Button |
---|---|
Key | pulsar.layout.hideAddActivityButton |
Value | Comma or newline separated <object API name>:<RecordTypeDeveloperName> list |
Default Value (if any) | |
Compatibility |
|
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. |
Name | Hide View Activity Button |
---|---|
Key | pulsar.layout.hideViewActivityButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | Hide view activity button. |
Notes/Comments |
Name | Hide Social Buttons |
---|---|
Key | Pulsar.hideSocialIcons |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | If the admin wants to not display the LinkedIn, Twitter, Google and Map icons, we can skip them entirely |
Notes/Comments |
Name | Hide Lead Convert Button |
---|---|
Key | pulsar.layout.hideLeadConvertButtonhideConvertButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | For whatever reason, if the admin wants to deny this capability. They can enable this setting. |
Notes/Comments |
Name | Lead Convert Options |
---|---|
Key | pulsar.layout.leadConvertOptions |
Value | Any/All of the following three choices (Opportunity, Attach, Contact) |
Default Value (if any) | |
Compatibility |
|
Description | If the admin wants to only use one of the three default options, they can use this setting. |
Notes/Comments | Opportunity - Lets the user convert the lead to a new opportunity Attach - Lets the user attach the lead to an existing opportunity Contact - Lets the user convert the lead to a contact without creating an opportunity. |
Name | Lead Custom Field Mapping |
---|---|
Key | pulsar.layout.leadConvertMapping |
Value | <lead custom field api name> : <target object type> . <target field custom field api name> |
Default Value (if any) | |
Compatibility |
|
Description | Custom field mappings from the lead object to the Account, Contact, and Opportunity objects can be specified for the lead conversion process. |
Notes/Comments | Custom_Lead_Field_1__c:Account.Custom_Account_Field__c Custom_Lead_Field_3__c:Opportunity.Custom_Opportunity_Field__c |
Name | Hide OrgChart Button |
---|---|
Key | pulsar.layout.hideOrgChartButton |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | Hide org chart capability |
Notes/Comments |
Name | Hide 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 |
|
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/Comments | Lead:Default:CuriumAutoAssigned Task:Default:CuriumEmailSent |
Name | Enable Signature Capture |
---|---|
Key | pulsar.layout.enableSignatureCapture |
Value | List of Object API Name:Record Type Name |
Default Value (if any) | |
Compatibility |
|
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 |
Name | Enable Camera Uploads/ Enhanced Attachment Mode |
---|---|
Key | pulsar.attachment.enableEnhancedMode |
Value | TRUE |
Default Value (if any) | FALSE |
Compatibility |
|
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/Comments |
Name | Hide Objections Field in OrgChart View |
---|---|
Key | pulsar.layout.orgStruct.hideObjectionsField |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
Description | Hide org chart objections text view |
Notes/Comments |
Name | Enable Opportunity Product Chaining |
---|---|
Key | pulsar.opportunity.enableProductChaining |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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 |
Name | Enable 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 |
|
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/Comments | For 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. |
Name | Enable Call Logging |
---|---|
Key | pulsar.enableCallLogging |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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 |
Name | Enable barcode scan for lookup object |
---|---|
Key | pulsar.<object API Name>.barcodeLookupFields |
Value | List of field API names to match with the barcode scan |
Default Value (if any) | None |
Compatibility |
|
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 the search the database for Accounts that have either the AccountNumber or the Name fields that match the scanned barcode. |
Name | Show Hidden Layout Section Headers |
---|---|
Key | pulsar.layout.showHiddenSections |
Value | TRUE / FALSE |
Default Value (if any) | FALSE |
Compatibility |
|
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/Comments | Feature as of Pulsar version 2.5.9 (101). |
Name | Override an object's name field |
---|---|
Key | pulsar.<object API name>.nameField |
Value | <field API name> |
Default Value (if any) | |
Compatibility |
|
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 |