...
We have created a Pulsar Setting pulsar.fsl.layout.detailFieldCount to allow the user to control how many detail fields are displayed throughout the app in situations like the one shown below. Pulsar will try to show up to 4 fields by default unless overridden by this setting. The number of fields displayed is also determined by the associated layout. The details below are driven by the related list layout between the WOLIs and their parent WorkOrder. If the related list has only 3 total fields defined, then one will be used as the header and only two detail fields could possibly be shown. Remember, if the field is undefined on the object, it will not be shown (see the bottom most set of details, which appears to not have an AssetId property defined).
...
To determine where a set of details or a header is coming from, refer to Pulsar FSL Screens and the data that feeds them for more information.
|
|
|---|---|
Name | Number of Detail Fields |
Key | pulsar.fsl.layout.detailFieldCount |
Value | Number |
Default Value (if any) | 4 |
Description | Sets the maximum number of detail fields to be displayed. |
Notes/Comments |
...