Create a set of job functions

post

/fscmRestApi/resources/11.13.18.05/publicSectorJobFunctions

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
  • Maximum Length: 1
    Indicates whether the job function is logically deleted (Y or N). Valid values are Y for a deleted record, and N for an active record. The default value is N.
  • Title: Job Function ID
    Maximum Length: 50
    The unique identifier for the job function.
  • Title: Description
    Maximum Length: 100
    The description of the job function.
  • Indicates whether the row is seed data. Valid values are 0 for customer data, 1 for seed data that cannot be modified, and a value more than 1indicates that the seed data that can be modified.
  • Title: Valid From
    The date from which the job function is available for use.
  • Title: Valid To
    The date until which the job function is available for use.
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 : publicSectorJobFunctions-item-response
Type: object
Show Source
Back to Top