Custom HTML documents enable you to create your own tables tabs and pages within the Pulsar FSL environment. These pages have full access to the Pulsar JSAPI bridge, enabling you to modify and display data as you see fit. You can add a custom document to the FSL tab bar, as a card that exists on a particular FSL object type, or that launches from the Lightning Bolt menu.
Custom Documents on the FSL Tab Bar
Adding a custom document to the tab bar is done through the pulsar.fsl.layout.tabs Pulsar setting. The values for this setting are separated by new lines and consist of a series of entries of either reserved words for standard FSL tabs or label : documentId pairs that will link to your custom documents.
| Warning |
|---|
You must add all tabs that you wish to see on the tab bar to this setting. Failure to add a tab will exclude it from the app. This includes the standard FSL tabs. |
| Note |
|---|
The keywords for the standard FSL tabs are: Schedule, Inventory, Notifications, and Profile. |
| Code Block |
|---|
Schedule
Inventory
Create Order:0696A000005Yr7i
Display Task:0696A000005Yw1V
Profile |
The above values would place the standard FSL schedule tab at the far left, the inventory tab to the right of that and a custom tab with the label text “Create Order” in the third location that would link to a custom document pointed at by the Id 0696A000005Yr7i. The fourth tab in Pulsar’s FSL application is always labeled More. Any items after the third will be placed in a modal pop-up that is launched when the More tab is tapped.
Custom Documents as Cards within an Object Type
Adding custom HTML as a card as part of the display of an FSL object is done through the pulsar.fsl.{objectType}.{optionalRecordTypeDeveloperName}.order Pulsar setting. When you create this Pulsar setting you are defining all of the cards that will display when viewing FSL objects that match the object type / record type pair that you define in the setting.
| Warning |
|---|
Failure to include a card in the value of the setting will result in it not being display. |
pulsar.fsl.workorder.order
| Code Block |
|---|
ServiceAppointment
Contact
Asset
Asset Work Items:0696A000005ijL3
Asset History:0696A000005ivUl
WorkOrderLineItem
KnowledgeArticle
ServiceReport |
The above value for the setting would display the cards listed from top to bottom on all WorkOrder objects. This would place two custom cards containing the HTML you defined in the files pointed to by the documents listed to the right of the colons. The text to the left of the colons will appear as the title of the card.
| Note |
|---|
Standard FSL cards are: ServiceAppointment, Contact, Asset, WorkOrderLineItem, KnowledgeArticle, ServiceReport, ProductRequestLineItem, ProductTransfer, Parent, and TimeSheetEntry. Many of these may not make sense depending on the context (FSL Object) from which these cards are displayed. If the object context does not contain a relation to the standard card object, it may display no data. |
Custom Documents from the Lightning Bolt Menu
Adding custom documents that launch from the FSL Lightning Bolt menu is done through the pulsar.fsl.layout.{objectType}.{optionalRecordTypeDeveloperName}.lightningbolt.listitems Pulsar setting. The value for this Pulsar setting should be valid 2-14. Pulsar Settings Language (PSL). The value’s logic should set a result of a string containing a list of lightning bolt menu items.
| Code Block |
|---|
DEFAULT{
Action=SetResult;
Result=parent : qa : FSL__NewEvent
flow : Action_Test
default
custom : Asset Hierarchy : 0696A000005YLUL
flow : Mobile_Survey
;
} |
The above value would be the simplest example and contains no actual logic. It simply defines the menu items to display.
Accessing the Bridge
The 3-2. Pulsar Platform - JS Bridge API is fully accessible from any custom document running in the Pulsar FSL environment.
...