Update a mobile offline unit of work record

patch

/fscmRestApi/resources/11.13.18.05/publicSectorMobileOfflineUows/{publicSectorMobileOfflineUowsUniqID}/child/OfflineUowRecord/{OfflineUowRecordUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- MobileApplication, UowId and UowMovedDate ---for the Mobile Offline Unit of Work Records resource and used to uniquely identify an instance of Mobile Offline Unit of Work Records. The client should not generate the hash key value. Instead, the client should query on the Mobile Offline Unit of Work Records collection resource with a filter on the primary key values in order to navigate to a specific instance of Mobile Offline Unit of Work Records.

    For example: OfflineUowRecord?q=MobileApplication=<value1>;UowId=<value2>;UowMovedDate=<value3>
  • This is the hash key of the attributes which make up the composite key--- MobileApplication and UowId ---for the Mobile Offline Work Units resource and used to uniquely identify an instance of Mobile Offline Work Units. The client should not generate the hash key value. Instead, the client should query on the Mobile Offline Work Units collection resource with a filter on the primary key values in order to navigate to a specific instance of Mobile Offline Work Units.

    For example: publicSectorMobileOfflineUows?q=MobileApplication=<value1>;UowId=<value2>
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorMobileOfflineUows-OfflineUowRecord-item-response
Type: object
Show Source
Back to Top