Get a planning application plan review department due date item

get

/fscmRestApi/resources/11.13.18.05/publicSectorPlanningDepartmentDueDatePlanReviews/{publicSectorPlanningDepartmentDueDatePlanReviewsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- LnpRecordKey, DepartmentId and ReviewerId ---for the Planning Department Due Date Plan Reviews resource and used to uniquely identify an instance of Planning Department Due Date Plan Reviews. The client should not generate the hash key value. Instead, the client should query on the Planning Department Due Date Plan Reviews collection resource with a filter on the primary key values in order to navigate to a specific instance of Planning Department Due Date Plan Reviews.

    For example: publicSectorPlanningDepartmentDueDatePlanReviews?q=LnpRecordKey=<value1>;DepartmentId=<value2>;ReviewerId=<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 : publicSectorPlanningDepartmentDueDatePlanReviews-item-response
Type: object
Show Source
  • Title: Address Line 1
    Read Only: true
    Maximum Length: 240
    The first or main address.
  • Title: Address Line 2
    Read Only: true
    Maximum Length: 240
    The second address, if present.
  • Title: Assigned Planner Email
    Read Only: true
    Maximum Length: 240
    The user ID of the planner assigned to the planning application or pre-application.
  • Title: Assigned Planner Name
    Read Only: true
    Maximum Length: 240
    The display name of the planner assigned to the planning application or pre-application.
  • Title: Assigned Planner User ID
    Read Only: true
    Maximum Length: 64
    The email of the planner assigned to the planning application or pre-application.
  • Title: City
    Read Only: true
    Maximum Length: 60
    The city in the parcel address.
  • Title: Country
    Read Only: true
    Maximum Length: 3
    The country in the address.
  • Title: County
    Read Only: true
    Maximum Length: 60
    The county in the parcel address.
  • Title: Plan Check Coordinator Name
    Read Only: true
    The display name of the user who created the plan review cycle.
  • Title: Plan Check Coordinator Email
    Read Only: true
    The email address of the user who created the plan review cycle.
  • Title: Plan Check Coordinator User ID
    Read Only: true
    Maximum Length: 64
    The user who created the plan review cycle.
  • Title: Plan Review Cycle
    Read Only: true
    The number specifying each plan review cycle.
  • Title: Plan Review Cycle Days
    Read Only: true
    The number of days that the plan review cycle was open or in progress.
  • Title: Plan Review Cycle Due Date
    Read Only: true
    The date by which the plan review cycle must be completed.
  • Title: Plan Review Cycle Status
    Read Only: true
    Maximum Length: 30
    The review status for the plan review cycle.
  • Read Only: true
    Maximum Length: 15
    The review status code for the plan review cycle.
  • Read Only: true
    Maximum Length: 15
    The decision status code for the plan review cycle.
  • Read Only: true
    Maximum Length: 30
    The unique identifier for the department associated with the plan review.
  • Title: Plan Reviewer Department
    Read Only: true
    Maximum Length: 25
    The display name of the department associated with the plan review.
  • Read Only: true
    Maximum Length: 1
    The upload status of the document attachment associated with the plan review.
  • Title: Electronic Review
    Read Only: true
    Maximum Length: 1
    Indicates whether the plan review has been performed for a document attachment. The default value is N for no.
  • Links
  • Title: Record ID
    Read Only: true
    Maximum Length: 50
    The planning application identifier.
  • Read Only: true
    The unique identifier for a planning application record.
  • Title: Application Description
    Read Only: true
    Maximum Length: 1000
    The record description.
  • Title: Application Status
    Read Only: true
    Maximum Length: 15
    The record status.
  • Title: Applicant Name
    Read Only: true
    Maximum Length: 450
    The name of the applicant.
  • Title: Plan Review Cycle Decision
    Read Only: true
    Maximum Length: 35
    The decision status for the plan review cycle.
  • Title: Plan Reviewer Name
    Read Only: true
    The display name of the department-level plan reviewer.
  • Title: Plan Reviewer Email
    Read Only: true
    The email of the department-level plan reviewer.
  • Title: Plan Reviewer User ID
    Read Only: true
    The user ID of the department-level plan reviewer.
  • Title: Plan Review Key
    Read Only: true
    The unique identifier for a plan review cycle.
  • Title: Plan Review Name
    Read Only: true
    Maximum Length: 100
    The name of the plan review.
  • Title: Plan Review Type
    Read Only: true
    Maximum Length: 11
    The type of plan review. For example, a plan review type for the first cycle is O for original or R for resubmittal.
  • Title: Postal Code
    Read Only: true
    Maximum Length: 60
    The postal code in the parcel address.
  • Title: Province
    Read Only: true
    Maximum Length: 60
    The province in the parcel address.
  • Title: Record Type
    Read Only: true
    Maximum Length: 100
    The type of planning application.
  • Title: Plan Review Closed Date
    Read Only: true
    The date when the plan review cycle was closed.
  • Title: Plan Reviewer Due Date
    Read Only: true
    The date by which the assigned plan reviewer must complete the department-level plan review.
  • Read Only: true
    The unique identifier for the plan reviewer associated with the plan review department.
  • Title: Plan Reviewer Review Status
    Read Only: true
    Maximum Length: 30
    The review status of a department-level plan review.
  • Read Only: true
    Maximum Length: 15
    The review status code of a department-level plan review.
  • Title: Plan Review Open Date
    Read Only: true
    The date when the plan review cycle was opened.
  • Title: State
    Read Only: true
    Maximum Length: 60
    The state in the parcel address.
  • Title: Subclassification
    Read Only: true
    Maximum Length: 10
    The subclassification of a planning record.
Back to Top