Get all self-service role history

get

/crmRestApi/resources/11.13.18.05/customerSelfServiceUsers/{UserId}/child/SelfServiceRolesHistory

Request

Path Parameters
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
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey: Finds the role history of a self-service user with the specified primary key.
      Finder Variables:
      • HistoryId; string; The unique identifier of the role history record.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AccountPartyId; integer; The unique identifier of the account of the self-service user associated with the role history.
    • AccountPartyName; string; The name of the account of the self-service user associated with the role history.
    • ActionDate; string; The date when the role history was updated.
    • ActionUserId; string; The unique identifier of the administrator who updated the role history.
    • ActionUserName; string; The name of the administrator who updated the role history.
    • ContactPartyId; integer; The unique identifier of the contact record of the self-service user associated with the role history.
    • ContactPartyName; string; The name of the contact record of the self-service user associated with the role history.
    • HistoryId; string; The unique identifier of the role history.
    • RelationshipType; string; The description of the role type.
    • RelationshipTypeCd; string; The code indicating the type of role. The list of accepted values is defined in the lookup type ORA_SVC_CSS_REL_TYPE_CD.
    • RoleStatus; string; The status of the role history. The status can be Granted or Revoked.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : customerSelfServiceUsers-SelfServiceRolesHistory
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : customerSelfServiceUsers-SelfServiceRolesHistory-item-response
Type: object
Show Source
  • Title: Account ID
    Read Only: true
    The unique identifier of the account of the self-service user associated with the role history.
  • Title: Account Name
    Read Only: true
    Maximum Length: 360
    The name of the account of the self-service user associated with the role history.
  • Title: Date
    Read Only: true
    The date when the role history was updated.
  • Title: Administrator Login
    Read Only: true
    Maximum Length: 64
    The unique identifier of the administrator who updated the role history.
  • Title: Administrator
    Read Only: true
    Maximum Length: 255
    The name of the administrator who updated the role history.
  • Title: Contact ID
    Read Only: true
    The unique identifier of the contact record of the self-service user associated with the role history.
  • Title: Contact Name
    Read Only: true
    Maximum Length: 360
    The name of the contact record of the self-service user associated with the role history.
  • Title: History ID
    Read Only: true
    Maximum Length: 41
    The unique identifier of the role history.
  • Links
  • Title: Relationship Type
    Read Only: true
    Maximum Length: 80
    The description of the role type.
  • Title: Relationship Type Code
    Read Only: true
    Maximum Length: 320
    The code indicating the type of role. The list of accepted values is defined in the lookup type ORA_SVC_CSS_REL_TYPE_CD.
  • Title: Status
    Read Only: true
    The status of the role history. The status can be Granted or Revoked.
Back to Top