Get a code enforcement status

get

/fscmRestApi/resources/11.13.18.05/publicSectorCodeEnforcementStatuses/{publicSectorCodeEnforcementStatusesUniqID}

Request

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

    For example: publicSectorCodeEnforcementStatuses?q=AgencyId=<value1>;Classification=<value2>;Status=<value3>
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 : publicSectorCodeEnforcementStatuses-item-response
Type: object
Show Source
  • The unique identifier for an agency.
  • Maximum Length: 15
    The unique identifier of the code enforcement object classification that indicates if an object is a case, incident, or inspection.
  • Read Only: true
    Maximum Length: 64
    The user who created the code enforcement status.
  • Read Only: true
    The date and time that the code enforcement status was created.
  • Maximum Length: 1
    Indicates whether the record is deleted.
  • Title: Enabled
    Maximum Length: 1
    Indicates whether the record is enabled.
  • Read Only: true
    The date and time that the code enforcement status was last updated.
  • Read Only: true
    Maximum Length: 64
    The user who last updated the code enforcement status.
  • Read Only: true
    Maximum Length: 32
    The session login associated with the user who last updated the code enforcement status.
  • Links
  • Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
  • Default Value: 0
    Indicates whether the row is seed data. Valid values are 0 for data that is customer data, 1 for seed data that cannot be modified, and 2 for seed data that can be modified.
  • Title: Status
    Maximum Length: 15
    The unique identifier of the code enforcement status code.
  • Title: Description
    Maximum Length: 30
    The description of the code enforcement status code.
  • Title: System Status
    Maximum Length: 15
    The delivered value of a code enforcement status.
  • Maximum Length: 1
    Indicates whether workflow integration is active. When workflow integration is active, the workflow system makes all status changes, and users are not permitted to manually update the status.
Back to Top