Get a pre-application meeting attribute

get

/fscmRestApi/resources/11.13.18.05/publicSectorPreappMeetingCommunications/{publicSectorPreappMeetingCommunicationsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Pre-application Meeting Communications resource and used to uniquely identify an instance of Pre-application Meeting Communications. The client should not generate the hash key value. Instead, the client should query on the Pre-application Meeting Communications collection resource in order to navigate to a specific instance of Pre-application Meeting Communications to get the hash key.
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
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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 : publicSectorPreappMeetingCommunications-item-response
Type: object
Show Source
  • Title: Address Line 1
    Read Only: true
    Maximum Length: 240
    The address of the Pre-Application.
  • Title: Address Line 2
    Read Only: true
    Maximum Length: 240
    The additional address of the Pre-Application.
  • Title: Address Line 3
    Read Only: true
    Maximum Length: 240
    The additional address of the Pre-Application.
  • Title: Address Line 4
    Read Only: true
    Maximum Length: 240
    The additional address of the Pre-Application.
  • Title: Agency ID
    Read Only: true
    The unique identifier of the public sector agency.
  • Title: Applicant ID
    Read Only: true
    The identifier of the applicant of the Pre-Application.
  • Title: Applicant User ID
    Read Only: true
    The user ID of the applicant as set up in the system.
  • Title: Preapplication or Consultation Status
    Read Only: true
    Maximum Length: 15
    The status of the application.
  • Read Only: true
    The identifier of the date and time when a planner was assigned to Pre-Application.
  • Title: Planner or Specialist ID
    Read Only: true
    The unique identifier of the assigned planner.
  • Title: City
    Read Only: true
    Maximum Length: 60
    The city of the Pre-Application.
  • Title: Classification
    Read Only: true
    Maximum Length: 3
    The unique identifier of the type of application.
  • Title: Record Type ID
    Read Only: true
    Maximum Length: 30
    The unique identifier of the type of record.
  • Title: Country
    Read Only: true
    Maximum Length: 3
    The country of the Pre-Application.
  • Title: County
    Read Only: true
    Maximum Length: 60
    The county of the Pre-Application.
  • Title: Preapplication or Consultation Description
    Read Only: true
    Maximum Length: 1000
    The additional information about the Pre-Application.
  • Title: Planner or Specialist Name
    Read Only: true
    Maximum Length: 240
    The name of the planner.
  • Title: Planner or Specialist Email
    Read Only: true
    Maximum Length: 240
    The email of the planner.
  • Title: Applicant Primary Email
    Read Only: true
    Maximum Length: 320
    The email of the applicant.
  • Title: Applicant Secondary Email
    Read Only: true
    Maximum Length: 320
    The additional email of the applicant.
  • Links
  • Title: Preapplication or Consultation ID
    Read Only: true
    Maximum Length: 50
    The unique identifier of the Pre-Application.
  • Title: Application ID
    Read Only: true
    The unique identifier of the Pre-Application.
  • Title: Meeting Agenda
    Read Only: true
    The text of the meeting agenda.
  • Title: Invitees
    Read Only: true
    Maximum Length: 4000
    The list of additional attendees for the meeting.
  • Title: Meeting Duration in Hours
    Read Only: true
    The unique identifier of the duration of the meeting.
  • Title: Meeting End Time
    Read Only: true
    The unique identifier of the end date and time for the meeting.
  • Title: End Date and Time in Agency Format
    Read Only: true
    The end date and time of the meeting shown in the agency date and time format.
  • Title: Meeting ID
    Read Only: true
    The unique identifier of the meeting.
  • Title: Meeting Start Time
    Read Only: true
    The unique identifier of the start date and time for the meeting.
  • Title: Start Date and Time in Agency Format
    Read Only: true
    The start date and time of the meeting shown in the agency date and time format.
  • Title: Subject
    Read Only: true
    Maximum Length: 4000
    The subject of the meeting.
  • Title: Meeting Location
    Read Only: true
    Maximum Length: 2000
    The identifier of the location of the meeting.
  • Title: Applicant Name
    Read Only: true
    Maximum Length: 450
    The name of the applicant.
  • Title: Planner or Specialist User ID
    Read Only: true
    The user ID of the planner assigned to the application.
  • Title: Postal Code
    Read Only: true
    Maximum Length: 60
    The postal code of the Pre-Application.
  • Title: Province
    Read Only: true
    Maximum Length: 60
    The province of the Pre-Application.
  • Title: Record Type
    Read Only: true
    Maximum Length: 20
    The unique identifier of the Pre-Application.
  • Read Only: true
    Maximum Length: 30
    The record ID of the parent application for which the meeting is scheduled.
  • Title: State
    Read Only: true
    Maximum Length: 60
    The state of the Pre-Application.
  • Title: Meeting Status
    Read Only: true
    Maximum Length: 10
    The identifier of the status of the meeting.
  • Title: Subclassification
    Read Only: true
    Maximum Length: 20
    The identifier of the type of application based on classification.
  • Title: Time Zone
    Read Only: true
    Maximum Length: 64
    The identifier of the time zone.
Back to Top