Create user statuses

post

/fscmRestApi/resources/11.13.18.05/channelUserStatuses

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
    Default Value: false
    Contains one of the following values: true or false. If true, then the user status is enabled for the buy-side flows. If false, then the user status is not enabled for the buy-side flows. This attribute does not have a default value.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then for the given system status and user status for combination, the selected user status will be set as default for the buy side. If false, then do not set the user status as the default status. This attribute does not have a default value.
  • Maximum Length: 1000
    Description of the channel user status.
  • Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then the user status is enabled for the system status. If false, then the user status is not enabled. This attribute does not have a default value.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the status is predefined. If false, then the status is not predefined. This attribute does not have a default value.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then for the given system status and user status for combination, the selected user status will be set as default for the sell side. If false, then do not set the user status as the default status. This attribute does not have a default value.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the user status is enabled for the sell-side flows. If false, then the user status is not enabled for the sell-side flows. This attribute does not have a default value.
  • Name of the system status of the channel objects. Based on the value selected in UserStatusFor, values from the lookup type ORA_CJM_PROGRAM_TYPE_STATUS, ORA_CJM_PROGRAM_STATUS, or ORA_CJM_CLAIM_STATUS can be passed.
  • Maximum Length: 30
    Abbreviation that identifies the system status of the channel objects.
  • Maximum Length: 30
    Abbreviation that identifies the channel user status.
  • Name of the channel object type for which the user status is created. A list of accepted values is defined in the lookup type ORA_CJM_USER_STATUS_FOR.
  • Maximum Length: 30
    Abbreviation that identifies the channel object type for which the user status is created. A list of accepted values is defined in the lookup type ORA_CJM_USER_STATUS_FOR.
  • Maximum Length: 50
    Name of the channel user status.
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 : channelUserStatuses-item-response
Type: object
Show Source
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the user status is enabled for the buy-side flows. If false, then the user status is not enabled for the buy-side flows. This attribute does not have a default value.
  • Read Only: true
    Maximum Length: 64
    User who created the record.
  • Read Only: true
    Date and time when the user created the record.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then for the given system status and user status for combination, the selected user status will be set as default for the buy side. If false, then do not set the user status as the default status. This attribute does not have a default value.
  • Maximum Length: 1000
    Description of the channel user status.
  • Maximum Length: 1
    Default Value: true
    Contains one of the following values: true or false. If true, then the user status is enabled for the system status. If false, then the user status is not enabled. This attribute does not have a default value.
  • Read Only: true
    Date and time when the user most recently updated the record.
  • Read Only: true
    Maximum Length: 64
    User who most recently updated the record.
  • Links
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the status is predefined. If false, then the status is not predefined. This attribute does not have a default value.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then for the given system status and user status for combination, the selected user status will be set as default for the sell side. If false, then do not set the user status as the default status. This attribute does not have a default value.
  • Maximum Length: 1
    Default Value: false
    Contains one of the following values: true or false. If true, then the user status is enabled for the sell-side flows. If false, then the user status is not enabled for the sell-side flows. This attribute does not have a default value.
  • Name of the system status of the channel objects. Based on the value selected in UserStatusFor, values from the lookup type ORA_CJM_PROGRAM_TYPE_STATUS, ORA_CJM_PROGRAM_STATUS, or ORA_CJM_CLAIM_STATUS can be passed.
  • Maximum Length: 30
    Abbreviation that identifies the system status of the channel objects.
  • Maximum Length: 30
    Abbreviation that identifies the channel user status.
  • Name of the channel object type for which the user status is created. A list of accepted values is defined in the lookup type ORA_CJM_USER_STATUS_FOR.
  • Maximum Length: 30
    Abbreviation that identifies the channel object type for which the user status is created. A list of accepted values is defined in the lookup type ORA_CJM_USER_STATUS_FOR.
  • Read Only: true
    Value that uniquely identifies the channel user status. It is a primary key that the application generates when it creates the user status.
  • Maximum Length: 50
    Name of the channel user status.
Back to Top

Examples

This example describes how to create user statuses.

Example cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/channelUserStatuses"

Example Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates.

{
	"UserStatusFor": "Program",
	"SystemStatus": "Draft",
	"UserStatusName": "Pending Manager Review",
	"UserStatusCode": "PENDING_MANAGER_REVIEW",
	"Description": "Pending Manager Review"
}

Example Response Body

The following example includes the contents of the response body in JSON format:

{
	"UserStatusId": 300100185773815,
	"UserStatusForCode": "PROGRAM",
	"UserStatusFor": "Program",
	"SystemStatusCode": "DRAFT",
	"SystemStatus": "Draft",
	"UserStatusCode": "PENDING_MANAGER_REVIEW",
	"UserStatusName": "Pending Manager Review",
	"Description": "Pending Manager Review",
	"DefaultFlag": null,
	"SeededFlag": false,
	"StartDate": null,
	"EndDate": null,
	"CreatedBy": "channel_user",
	"CreationDate": "2020-06-03T02:46:57+00:00",
	"LastUpdatedBy": "channel_user",
	"LastUpdateDate": "2020-06-03T02:46:57.082+00:00",
	"links": [
	{
		"rel": "self",
		"href": "https://servername/fscmRestApi/resources/version/channelUserStatuses/300100185773815",
		"name": "channelUserStatuses",
		"kind": "item",
		"properties": {
			"changeIndicator": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178"
		}
	},
	{
		"rel": "canonical",
		"href": "https://servername/fscmRestApi/resources/version/channelUserStatuses/300100185773815",
		"name": "channelUserStatuses",
		"kind": "item"
	}
	]
}
Back to Top