REST Objects FlexView
ServiceMobility
When ServiceMobility is the primary sub-system for a Work Item object, then the structure of any associated FlexView objects in ServiceBroker is not defined at the ServiceBroker level.
Instead, the FlexView object will be a pass-through object in ServiceBroker - that is, the FlexView object will have the object structure as defined by the version of ServiceMobility which is the primary sub-system.
Accordingly, please see the appropriate documentation for the FlexView object in the relevant version of ServiceMobility:
ServiceScheduling
When ServiceScheduling is the primary sub-system for a Work Item object, then the structure of any associated FlexView objects in ServiceBroker is as defined below.
- The ServiceBroker Work Item Object
FlexView
field is only mapped to the ServiceSchedulingmoreNotes
field when:- the
moreNotes
content is XML (see the REST Objects Work Item's Notes field for when themoreNotes
field contains plain text); and - the
UseMoreNotesForJobInfo
configuration setting isfalse
.
- the
When ServiceScheduling is the primary sub-system for a Work Item object, and the above requirements are met (i.e. the moreNotes
field of the Work Item in ServiceScheduling in XML, and the UseMoreNotesForJobInfo
configuration setting is false
), then there are two different ways that ServiceBroker will parse the moreNotes
XML into FlexView objects, depending on the XML content provided by ServiceScheduling:
Basic More Notes Format
When the ServiceScheduling moreNotes
XML is a simple list of one or more name/value pairs, representing simple additional notes in XML format, then ServiceBroker will parse this into a single FlexView object, with a Title
value of "More Notes", and the name/value pairs being translated into corresponding Label
/Value
entries in the Items
array.
For example, a moreNotes
XML value in ServiceScheduling of:
will be translated into a FlexView object of format:
Extended More Notes Format
In addition to supporting a simple list of name/value pairs in XML format, ServiceScheduling also supports a specific "extended" XML format, which allows specific Work Item asset, job description and customer details to be stored.
When the ServiceScheduling moreNotes
XML is in this extended format, then ServiceBroker will parse this into a number of FlexView objects, with Title
values based on the specific ServiceScheduling sections, with appropriate corresponding Label
/Value
entries in the Items
array for each.
For example, a moreNotes
XML value in ServiceScheduling of:
will be translated into three FlexView objects of format:
FlexView Object Format
FlexView Object Properties
Property | Type | Required? | Description | Field Mappings | |
---|---|---|---|---|---|
ServiceScheduling | |||||
Title | string | Yes | A title, describing a "group" of FlexView item(s). | moreNotes | |
Items | |||||
Label | string | Yes | A label, describing the specific FlexView item in the "group". |
| |
Value | string | Yes | The value for the associated "label" in the "group" | moreNotes |