Get a role definition

get

/fscmRestApi/resources/11.13.18.05/publicSectorRoleDefinitions/{publicSectorRoleDefinitionsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Role Definitions resource and used to uniquely identify an instance of Role Definitions. The client should not generate the hash key value. Instead, the client should query on the Role Definitions collection resource in order to navigate to a specific instance of Role Definitions to get the hash key.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : publicSectorRoleDefinitions-item-response
Type: object
Show Source
  • Title: Abstract Role
    Read Only: true
    Maximum Length: 30
    Indicates if the role is of the type abstract.
  • Title: Status
    Read Only: true
    Maximum Length: 30
    Indicates if the role is available to be used in assignments.
  • Title: Data Role
    Read Only: true
    Maximum Length: 30
    Indicates if the role is of the type role.
  • Title: Delegation Allowed
    Read Only: true
    Maximum Length: 30
    Indicates if the role can be assigned through delegation.
  • Title: Description
    Read Only: true
    Maximum Length: 240
    The description of the role.
  • Read Only: true
    Maximum Length: 30
    Indicates if the role is of the type duty.
  • Read Only: true
    Maximum Length: 64
    The identifier of the external role.
  • Read Only: true
    Maximum Length: 30
    Indicates if the role is of the type external.
  • Title: Job Role
    Read Only: true
    Maximum Length: 30
    Indicates if the role is of the type job.
  • Links
  • Read Only: true
    The identifier of the optimistic lock. The value is incremented each time the row is updated. The values at the beginning and at the end of the transaction are compared to determine if a session updated the row since it was queried.
  • Title: Role Code
    Read Only: true
    Maximum Length: 240
    The unique identifier of the role.
  • Title: Role Distinguished Name
    Read Only: true
    Maximum Length: 4000
    The distinguished name defined within the LDAP. It contains the relevant group information to provide a unique name.
  • Title: Role Globally Unique ID
    Read Only: true
    Maximum Length: 64
    The unique global identifier of the role.
  • Read Only: true
    The unique identifier of the role.
  • Title: Role Name
    Read Only: true
    Maximum Length: 240
    The name for the role.
Back to Top