Update a flexfield

patch

/fscmRestApi/resources/11.13.18.05/advancedControls/{Id}/child/incidents/{Id4}/child/additionalInformations/{Id5}

Request

Path Parameters
  • The unique identifier of the advanced control.
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
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
  • Title: Context Segment
    Maximum Length: 150
    The context value that prompts a context-sensitive segment to appear in a flexfield associated to the advanced control.
  • Title: Context Segment
    The segment that appears in a flexfield associated to the advanced control only in a defined context.
  • Maximum Length: 255
    The unique identifier of a flexfield associated to the advanced control.
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 : advancedControls-incidents-additionalInformations-item-response
Type: object
Show Source
  • Title: Context Segment
    Maximum Length: 150
    The context value that prompts a context-sensitive segment to appear in a flexfield associated to the advanced control.
  • Title: Context Segment
    The segment that appears in a flexfield associated to the advanced control only in a defined context.
  • Maximum Length: 255
    The unique identifier of a flexfield associated to the advanced control.
  • Links
Back to Top

Examples

The following example shows how to update a flexfield for an incident by submitting a PATCH request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "Content-Type: application/json" -X PATCH -d <payload> https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/advancedControls/10011/child /incidents/10011%3A20/child/additionalInformations/10011%3A20

Example Request Payload

The following example shows the contents of the request body in JSON format:

{
	"aacupg181010c": "test1000"
}

Example Response Body

The following example shows the contents of the response body in JSON format:

{  
	"Id": "10011:20",
	"aacupg181010c": "test1000",
	"aacupg181015n": null,
	"aacupg1810D": null,
	"__FLEX_Context": null,
	"__FLEX_Context_DisplayValue": null,
	"links": [
	...
	] 
}
Back to Top