Get a fee line

get

/fscmRestApi/resources/11.13.18.05/publicSectorFeeSchedules/{publicSectorFeeSchedulesUniqID}/child/FeeLine/{FeeLineUniqID}

Request

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

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

    For example: publicSectorFeeSchedules?q=AgencyId=<value1>;FeeScheduleId=<value2>;EffectiveStartDate=<value3>;EffectiveEndDate=<value4>
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 : publicSectorFeeSchedules-FeeLine-item-response
Type: object
Show Source
  • Title: Agency ID
    Default Value: 1
    The identifier for the public sector agency to which this fee schedule belongs.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the fee line.
  • Title: Creation Date
    Read Only: true
    The date when the fee line was created.
  • Title: Currency
    Maximum Length: 3
    The default currency code from the COM_AGENCY table. For now, this field is display-only.
  • Title: Model Name
    Maximum Length: 1000
    The fee decision model name.
  • Title: Service Name
    Maximum Length: 1000
    The OIC REST service name for the deployed model.
  • Title: Space ID
    Maximum Length: 1000
    The internal ID for the Oracle Autonomous Integration Cloud (OIC) space. This is the workflow space that OIC actually uses to reference the decision model; however, it is not exposed to the user.
  • Title: Space Name
    Maximum Length: 1000
    The user-friendly OIC space name. This field relates to the DMN_SPACE_ID field.
  • Title: Version
    Maximum Length: 1000
    The OIC tag is the version number for the deployed fee decision model.
  • Title: Effective End Date
    The end date of the fee schedule.
  • Title: Effective Start Date
    The start date of the fee schedule.
  • Title: Fee Schedule
    Maximum Length: 20
    A unique name that identifies a fee schedule.
  • Title: Fee Items
    The line number for the current fee schedule. When the user adds a new line, it is incremented up to the maximum number of fee schedule lines.
  • Fee Schedule Map Data
    Title: Fee Schedule Map Data
    The fee schedule map data resource is used to view, create, delete, or modify the data. The fee mapping is to store the mapping data and to calculate the DMN fee outside of the form design.
  • Title: Last Updated Date
    Read Only: true
    The date when the fee line was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the fee line.
  • Links
  • Title: Map Fee Amount
    Maximum Length: 50
    The output resource name for fee amount to be stored.
  • Title: Map Fee Item
    Maximum Length: 50
    The output resource name for the fee item to be stored.
  • Title: Map Fee Reference
    Maximum Length: 50
    The identifier of the map fee reference for the decision model.
  • Title: Mapping Source
    Maximum Length: 10
    The source transaction that requires field mapping to calculate fees.
  • Title: Pay Now
    Maximum Length: 1
    Indicates whether the fee item is payable upon submission of the application or not. The default value is no.
  • Maximum Length: 1
    Indicates whether this fee line is used for amended fees. This field is for future use. There is no default value.
  • Maximum Length: 1
    Indicates whether this fee line is used for the original fees. The default value is yes.
  • Maximum Length: 1
    Indicates whether this fee line is used for renewal fees. This field is for future use. There is no default value.
Nested Schema : Fee Schedule Map Data
Type: array
Title: Fee Schedule Map Data
The fee schedule map data resource is used to view, create, delete, or modify the data. The fee mapping is to store the mapping data and to calculate the DMN fee outside of the form design.
Show Source
Nested Schema : publicSectorFeeSchedules-FeeLine-FeeScheduleMapD-item-response
Type: object
Show Source
Back to Top