REST Objects Asset
ServiceDispatch
When ServiceDispatch is the primary sub-system for a Work Item object, then the structure of any associated Asset objects in ServiceBroker is as defined below.
Asset Object Format
Asset Object Properties
Property | Type | Required? | Description | Field Mappings |
---|---|---|---|---|
ServiceDispatch | ||||
Flexforms | string | No | An optional collection of FlexForm IDs. Each form specified in the collection will be available for the identified task. See: FlexForm Object | N/A |
Flexview | string | No | The optional See: Flex Views Object | N/A |
InServiceDate | Datetime | No | The date/time that the asset came into service. | ProductInfo: InstallDate |
Mfg | string | No | A description of the manufacturer of the asset. | ProductInfo: BrandDesc |
Model | string | No | The asset's model number. | ProductInfo: ModelNo |
ProdLine | string | No | A description of the asset. | ProductInfo: ProductDesc |
SerialNum | string | No | The asset's serial number. | ProductInfo: SerialNo |
ServiceCodes | string | No | An optional collection of service code IDs. The first service code ID specified in the collection is the top level service code, the second service code ID specified in the collection corresponds with the second level service code, etc. There may be a maximum of 7 levels of service codes defined. See: Service Code Object | N/A |
ServiceMobility
When ServiceMobility is the primary sub-system for a Work Item object, then the structure of any associated Asset objects in ServiceBroker is not be defined at the ServiceBroker level.
Instead, the Asset object will be a pass-through object in Broker - that is, the Asset 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 Asset object in the relevant version of ServiceMobility: