Create an autonumber rule

post

/fscmRestApi/resources/11.13.18.05/publicSectorAutoNumbers

Request

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
  • Default Value: 1
    The unique identifier for an agency that is associated with a autonumber rule.
  • Maximum Length: 1000
    The autonumber rule stored in JSON format.
  • Title: Description
    Maximum Length: 50
    The description of the autonumber rule.
  • Title: Maximum Size
    The maximum length of the number that is generated by an autonumber rule.
  • Title: Number Type
    Maximum Length: 10
    A code for the transaction or object that uses the autonumber rule. Examples include codes for invoices, permits, and inspections.
  • Title: Rule Name
    Maximum Length: 20
    The unique identifier for an autonumber rule.
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 : publicSectorAutoNumbers-item-response
Type: object
Show Source
Back to Top