...
Certain items, like Work Plans, may not appear if there are no associated Work Plans with the object (for instance, a Work Order).
Starting with Pulsar 13.0, you may define object-level carousel items using the Pulsar Setting pulsar.fsl.layout.{objectType}.carouselItems
for more granular control. For example, you can define pulsar.fsl.layout.workorderlineitem.carouselItems
with different items compared to pulsar.fsl.layout.carouselItems
.
|
|
---|---|
Name | Customized Carousel Items |
Key | pulsar.fsl.layout{.objectType}.carouselItems |
Value | A list of valid values separated by commas or new lines. Valid strings are: work-plans |
Default Value (if any) | work-plans |
Description | Use this setting to customize the set of carousel items on an SObject page in SFS. |
Notes/Comments |
...
Providing specific object type for this setting is available in 13.0+ |
Hiding the Assign Contact Button
The SObject overview page contact component will by default display a button to assign a Contact to the Service Appointment. Use this setting to hide the button if desired by setting the value to false.
|
|
---|---|
Name | SFS: Show Assign Contact Button |
Key | pulsar.fsl.layout.showAssignContactButton |
Value | TRUE/FALSE |
Default Value (if any) | TRUE |
Description | Use this option to display/hide the assign contact button. |
Notes/Comments |
Hiding The Map on
...
Schedule Screen
Some customers have asked us if they can hide the map on the appointment overview schedule screen because it takes a significant amount of screen real estate on phones. You can do this by specifying a Pulsar Setting in your org.
|
|
---|---|
Name | Hide Map Component on Schedule Screen |
Key | pulsar.fsl.layout. |
schedule.displayMap | |
Value | TRUE/FALSE |
---|---|
Default Value (if any) | TRUE |
Description | Use this option to display/hide the map component on the |
schedule screen. |
Notes/Comments |
---|
Users can still get Driving Directions by clicking on the button in the section.
...
Hiding The Map on Service Appointment Overview Screen
This setting allows users to remove the Get Driving Directions button from the Service Appointment detail component on the overview page. It is important to note that this button is displayed by defaultSome customers have asked us if they can hide the map on the appointment overview screen because it takes a significant amount of screen real estate on phones. You can do this by specifying a Pulsar Setting in your org.
|
|
---|---|
Name | Hide |
Map Component | |
Key | pulsar.fsl.layout.serviceappointment. |
---|
displayMap | |
Value | TRUE/FALSE |
---|---|
Default Value (if any) | TRUE |
Description | Use this option to display/hide the |
Name
map component on the overview screen. |
Notes/Comments |
---|
Displaying Resource Absences in the Schedule
It may be useful to your users to see resource absences displayed in the Field Service Lightning schedule screen in Pulsar. You can achieve this through this setting. Resource absences will not display in the scrolling calendar navigation view as “dots” (implying the presence of a Service Appointment) but they will be shown in the list of events for a selected day and on the full calendar display.
Users can still get Driving Directions by clicking on the button in the section. |
Hiding Get Driving Directions Button on Service Appointment Overview Screen
This setting allows users to remove the Get Driving Directions button from the Service Appointment detail component on the overview page. It is important to note that this button is displayed by default.
|
|
---|---|
Name | Hide Get Directions Component |
Key | pulsar.fsl.layout. |
serviceappointment. |
displayDrivingDirectionsButton | |
Value | TRUE/FALSE |
---|---|
Default Value (if any) |
TRUE | |
Description | Use this option to display |
---|
/hide the get driving directions button on the |
overview screen. |
Notes/Comments |
---|
None.
Hiding the App Browser
...
...
...
Name
...
Display App Browser
...
Key
...
Displaying Resource Absences in the Schedule
It may be useful to your users to see resource absences displayed in the Field Service Lightning schedule screen in Pulsar. You can achieve this through this setting. Resource absences will not display in the scrolling calendar navigation view as “dots” (implying the presence of a Service Appointment) but they will be shown in the list of events for a selected day and on the full calendar display.
|
|
---|---|
Name | Display Resource Absences |
Key | pulsar.fsl.layout.schedule.showResourceAbsences |
Value | TRUE/FALSE |
Default Value (if any) | FALSE |
Description | Use this option to display resource absences on the schedule view. |
Notes/Comments | None. |
Hiding the App Browser
|
|
---|---|
Name | Display App Browser |
Key | pulsar.home.toolbar.enableappbrowser |
Value | TRUE/FALSE |
Default Value (if any) | TRUE |
Description | Use this option to display or hide the 9 squares icon on the bottom toolbar |
Notes/Comments | None. |
...
|
|
---|---|
Name | SFS: Enable Back Button in Flows |
Key | pulsar.fsl.enableFlowBackButton |
Value | TRUE/FALSE |
Default Value (if any) | FALSE |
Description | When set to TRUE, the Pulsar will enable display of the Back button where appropriate in a properly configured SFS Mobile Flow. |
Notes/Comments | For more information about SFS Mobile Flow behavior, see this documentation: Considerations for Using Flows in the Field Service Mobile App (salesforce.com) NOTE:
|
Customizing Additional Display Fields in the Pricebook Products List
|
|
---|---|
Name | SFS: Fields to Display in Pricebook Products List |
Key | pulsar.fsl.pricebookentry.displayfields |
Value | Comma or newline separated list of fields from the PricebookEntry object |
Default Value (if any) | |
Description | The Pricebook product list, by default, will show only the product name in the list. Specifying additional PricebookEntry fields in this setting will display these fields under the Product Name line and separated by the “•” (bullet character). Here is an example where this setting was specified with these fields: ProductCode, UnitPrice |
Notes/Comments |
Determining if the User Can or Cannot View an Object using beforeView (available in Pulsar 14.0+)
|
| |||||
---|---|---|---|---|---|---|
Name | Before View | |||||
Key | pulsar.beforeView.<Object API Name> (e.g. pulsar.beforeView.ServiceAppointment) | |||||
Value | This setting executes when a user tries to view a record. PSL can be used to implement business rule validations to determine if the current user can or cannot view an object
| |||||
Default Value (if any) | ||||||
Description | ||||||
Notes/Comments |