1. REST API for Oracle Public Sector Licensing and Permitting
  2. Tasks
  3. Shared Services
  4. Theme Assignments
  5. User Theme Assignments
  6. Theme Assignment Attributes

Get all theme assignment plan attributes

get

/fscmRestApi/resources/11.13.18.05/publicSectorRegistryThemeAssignments/{publicSectorRegistryThemeAssignmentsUniqID}/child/UserThemeAssignments/{UserThemeAssignmentsUniqID}/child/Attributes

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- AgencyId, RegistryName, EffectiveStartDate, EffectiveEndDate and UserAssignmentId ---for the User Theme Assignments resource and used to uniquely identify an instance of User Theme Assignments. The client should not generate the hash key value. Instead, the client should query on the User Theme Assignments collection resource with a filter on the primary key values in order to navigate to a specific instance of User Theme Assignments.

    For example: UserThemeAssignments?q=AgencyId=<value1>;RegistryName=<value2>;EffectiveStartDate=<value3>;EffectiveEndDate=<value4>;UserAssignmentId=<value5>
  • This is the hash key of the attributes which make up the composite key--- AgencyId, RegistryName, EffectiveStartDate and EffectiveEndDate ---for the Theme Assignments resource and used to uniquely identify an instance of Theme Assignments. The client should not generate the hash key value. Instead, the client should query on the Theme Assignments collection resource with a filter on the primary key values in order to navigate to a specific instance of Theme Assignments.

    For example: publicSectorRegistryThemeAssignments?q=AgencyId=<value1>;RegistryName=<value2>;EffectiveStartDate=<value3>;EffectiveEndDate=<value4>
Query Parameters
  • This parameter specifies dependencies which are attributes that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The attributes 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 attributes 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 attributes. 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 attributes. Only the specified attributes are returned, which means that if no attributes are specified, no attributes 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 attributes. 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 theme assignment plan attribute that matches the primary key criteria specified. Finder Variables:
      • AgencyId; integer; The unique identifier of the agency that is associated with this theme assignment plan.
      • AttributeId; string; The unique identifier of the theme assignment plan attribute.
      • EffectiveEndDate; string; The end date when this theme assignment plan is in effect.
      • EffectiveStartDate; string; The start date when this theme assignment plan is in effect.
      • RegistryName; string; The unique identifier of the web application to which this theme assignment plan is applied.
      • UserAssignmentId; string; The unique identifier of the user level theme assignment plan.
  • 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.
  • 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 attributes. 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
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Body ()
Root Schema : publicSectorRegistryThemeAssignments-UserThemeAssignments-Attributes
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : publicSectorRegistryThemeAssignments-UserThemeAssignments-Attributes-item
Type: object
Show Source
Back to Top