Get a case attachment communication

get

/fscmRestApi/resources/11.13.18.05/publicSectorCaseAttachmentCommunications/{publicSectorCaseAttachmentCommunicationsUniqID}

Request

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

    For example: publicSectorCaseAttachmentCommunications?q=AttachmentId=<value1>;CaseKey=<value2>
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 : publicSectorCaseAttachmentCommunications-item-response
Type: object
Show Source
  • Read Only: true
    The identifier of the case attachment communication.
  • Read Only: true
    The unique identifier of the case attachment communication.
  • Read Only: true
    The unique identifier of the contact person associated with the case.
  • Read Only: true
    The identifier of the contact person associated with the case.
  • Title: First Name
    Read Only: true
    Maximum Length: 150
    The first name of the contact person associated with the case.
  • Title: Last Name
    Read Only: true
    Maximum Length: 150
    The last name of the contact person associated with the case.
  • Title: Case ID
    Read Only: true
    Maximum Length: 50
    The identifier of the case communication.
  • Read Only: true
    The unique identifier of the case communication.
  • Title: Code Officer Email
    Read Only: true
    Maximum Length: 240
    The email address of the code officer assigned to the case.
  • Title: Inspector Assigned
    Read Only: true
    Maximum Length: 100
    The unique identifier of the code officer assigned to the case.
  • Title: Code Officer Phone Number
    Read Only: true
    Maximum Length: 60
    The phone number of the code officer assigned to the case.
  • Title: Code Technician Email
    Read Only: true
    Maximum Length: 240
    The email address of the code technician assigned to the case.
  • Title: Technician Assigned
    Read Only: true
    Maximum Length: 100
    The unique identifier of the code technician assigned to the case.
  • Title: Code Technician Phone
    Read Only: true
    Maximum Length: 60
    The phone number of the code technician assigned to the case.
  • Title: Creation Date
    Read Only: true
    The date and time when the row was created.
  • Title: Category
    Read Only: true
    Maximum Length: 25
    The document category of the case attachment communication.
  • Title: Category ID
    Read Only: true
    Maximum Length: 30
    The document category code of the case attachment communication.
  • Title: Subcategory
    Read Only: true
    Maximum Length: 25
    The document subcategory of the case attachment communication.
  • Title: Subcategory ID
    Read Only: true
    Maximum Length: 30
    The document subcategory code of the case attachment communication.
  • Title: File Description
    Read Only: true
    Maximum Length: 100
    The description of the case attachment communication file.
  • Title: File Name
    Read Only: true
    Maximum Length: 255
    The name of the case attachment file communication.
  • Title: File Size
    Read Only: true
    File size of the case attachment communication.
  • Title: File Type
    Read Only: true
    Maximum Length: 100
    File type of the case attachment communication.
  • Title: Transaction Status
    Read Only: true
    Maximum Length: 15
    The user defined case status name that maps to a delivered system status.
  • Title: Issue Description
    Read Only: true
    Maximum Length: 1000
    The description of the case.
  • Title: Issue Subtype ID
    Read Only: true
    Maximum Length: 100
    The name of the issue subtype associated with the case.
  • Title: Issue Subtype Search Tags
    Read Only: true
    Maximum Length: 150
    The description of the issue subtype of the case.
  • Title: Issue Subtype Custom Id
    Read Only: true
    Maximum Length: 50
    The unique identifier of the issue subtype of the case.
  • Title: Issue Type
    Read Only: true
    Maximum Length: 100
    The name of the issue type associated with the case.
  • Title: Issue Type ID
    Read Only: true
    Maximum Length: 50
    The unique identifier of the issue type of the case.
  • Links
  • Title: Status
    Read Only: true
    Maximum Length: 15
    The status of the case.
  • Title: Status Description
    Read Only: true
    Maximum Length: 30
    The status name of the case.
Back to Top