Create a data security privilege

post

/fscmRestApi/resources/11.13.18.05/publicSectorPrivileges

Request

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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 128
    The names of the attributes that need to be redacted.
  • Maximum Length: 80
    The name of the entityobject associated with the viewobject.
  • Maximum Length: 80
    The name of the data security object.
  • Maximum Length: 400
    The name of the data security privilege.
  • Maximum Length: 20
    Indicates the type of the data security privilege. A privilege can be of these types: standard, custom, column authorization, or redaction.
  • Maximum Length: 20
    The format of the redacted attributes. Redaction format can be of multiple formats. For example, redact all digits, redact the last 3 digits, redact the last 4 digits, redact the complete string, redact the email address, and so on.
  • Maximum Length: 80
    The name of the viewobject associated with data security 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 : publicSectorPrivileges-item-response
Type: object
Show Source
Back to Top