12.50 Work Order Fetch Service (GET/PUT/POST)
Below mentioned are the custom fields. These fields will be part of both request/response.
Table 12-44 Work Order Fetch Service
Element name | Sub element | Data type |
---|---|---|
StringData | KeyName | String |
KeyValue | String | |
NumberData | KeyName | String |
KeyValue | Number (Decimal) | |
DateData | KeyName | String |
KeyValue | Date(YYYY-MM-DDTHH:MM:SS) |
Sample
XML
<Custom>
<StringData>
<KeyName>OrgName</KeyName>
<KeyValue>Oracle</KeyValue>
</StringData>
<NumberData>
<KeyName>BusinessPhoneNumber</KeyName>
<KeyValue>1234.01</KeyValue>
</NumberData>
<DateData>
<KeyName>CreationDate</KeyName>
<KeyValue>2017-12-18T00:00:00</KeyValue>
</DateData>
</Custom>
Sample
JSON
"Custom": {
"StringData": [
{
"KeyName": "OrgName",
"KeyValue": "Oracle"
}
],
"NumberData": [
{
"KeyName": "BusinessPhoneNumber",
"KeyValue": 1234.01
}
],
"DateData": [
{
"KeyName": "CreationDate",
"KeyValue": "2017-12-18T00:00:00"
}
]
}
}
Table 12-45 Package Details
Service name | Wrapper Package | Main Package | Exit Point Packages | ||
---|---|---|---|---|---|
Before | Replace | After | |||
Work Order Service (GET) |
|
|
|
||
|
|
|
|||
|
|
||||
|
|
|
|||
Work Order Service (PUT) |
|
|
|
||
|
|
|
|||
|
|
||||
|
|
|
|||
Work Order Service (POST) |
|
|
|
||
|
|
|
|||
|
|
||||
|
|
|
Parent topic: RESTful Web Services Extensibility