Create a record type plan reviewer department

post

/fscmRestApi/resources/11.13.18.05/publicSectorRecordTypes/{RecordTypeId}/child/RecordTypePlanReviewerDepartment

Request

Path Parameters
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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • The identifier for the public sector agency associated with the record type plan reviewer departments.
  • Title: Plan Reviewer Department
    Maximum Length: 30
    The identifier for record type plan reviewer departments.
  • Maximum Length: 20
    The unique alphanumeric code or short name for the record type associated with the record type plan reviewer departments.
  • Maximum Length: 30
    The identifier for the record type associated with the record type plan reviewer departments.
  • Title: Required Department
    Maximum Length: 1
    Indicates whether the department is required to review the documents.
  • Maximum Length: 50
    The time rule identifier that is used to calculate the due date.
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 : publicSectorRecordTypes-RecordTypePlanReviewerDepartment-item-response
Type: object
Show Source
  • The identifier for the public sector agency associated with the record type plan reviewer departments.
  • Read Only: true
    Maximum Length: 25
    The short description of the plan reviewer department identifier.
  • Read Only: true
    Maximum Length: 1
    Indicates whether the plan reviewer department is enabled.
  • Title: Plan Reviewer Department
    Maximum Length: 30
    The identifier for record type plan reviewer departments.
  • Links
  • Maximum Length: 20
    The unique alphanumeric code or short name for the record type associated with the record type plan reviewer departments.
  • Maximum Length: 30
    The identifier for the record type associated with the record type plan reviewer departments.
  • Title: Required Department
    Maximum Length: 1
    Indicates whether the department is required to review the documents.
  • Read Only: true
    Maximum Length: 256
    The time rule description.
  • Maximum Length: 50
    The time rule identifier that is used to calculate the due date.
Back to Top