Update a data security instance

patch

/fscmRestApi/resources/11.13.18.05/publicSectorInstances/{publicSectorInstancesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- Viewobjectname, Instancesetname and Entityobjectname ---for the Instances resource and used to uniquely identify an instance of Instances. The client should not generate the hash key value. Instead, the client should query on the Instances collection resource with a filter on the primary key values in order to navigate to a specific instance of Instances.

    For example: publicSectorInstances?q=Viewobjectname=<value1>;Instancesetname=<value2>;Entityobjectname=<value3>
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
  • Maximum Length: 80
    The name of the entity object associated with the view object.
  • Maximum Length: 30
    The name of the instance set, which uniquely identifies a row (or rows) of the secure object, represented by a SQL predicate.
  • Maximum Length: 80
    The name of the data security object.
  • Maximum Length: 4000
    The SQL predicate that uniquely identifies a row (or rows) of the secured object.
  • Maximum Length: 80
    The name of the view object associated with the data security object.
  • Maximum Length: 4000
    The transformed SQL predicate that uniquely identifies a row (or rows) of the secured object.
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 : publicSectorInstances-item-response
Type: object
Show Source
Back to Top