Create a team member
post
/fscmRestApi/resources/11.13.18.05/ideas/{IdeaId}/child/IdeaTeam
Request
Path Parameters
-
IdeaId(required): integer(int64)
Value that uniquely identifies an idea.
Header Parameters
-
Effective-Of:
This header accepts a string value. The string is a semi-colon separated list of
= . It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers. -
Metadata-Context:
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".
-
REST-Framework-Version:
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.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
UserId: integer
(int64)
Value that uniquely identifies the user, who is a team member.
-
UserName: string
Name of the user, who is a team member.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context(required):
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".
-
REST-Framework-Version(required):
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.
Root Schema : ideas-IdeaTeam-item-response
Type:
Show Source
object
-
CreatedBy: string
Read Only:
true
Maximum Length:64
User who created the team member. -
CreationDate: string
(date-time)
Read Only:
true
Date and time when the user created the team member. -
LastUpdateDate: string
(date-time)
Read Only:
true
Date and time when the user most recently updated the team member. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
User who most recently updated the team member. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
UserId: integer
(int64)
Value that uniquely identifies the user, who is a team member.
-
UserName: string
Name of the user, who is a team member.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Examples
This example describes how to create a team member.
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/ideas/IdeaId/child/IdeaTeam"
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.
{ "UserName": "plm_auto" }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "UserId": 100100013798698, "UserName": "PLM_AUTO", "CreatedBy": "PRODUCT_MANAGER", "CreationDate": "2020-12-11T09:09:10+00:00", "LastUpdatedBy": "PRODUCT_MANAGER", "LastUpdateDate": "2020-12-11T09:09:12.015+00:00", "links": [ { "rel": "self", "href": "https://servername/fscmRestApi/resources/version/ideas/300100240921318/child/IdeaTeam/300100240934107", "name": "IdeaTeam", "kind": "item", "properties": { "changeIndicator": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178" } }, { "rel": "canonical", "href": "https://servername/fscmRestApi/resources/version/ideas/300100240921318/child/IdeaTeam/300100240934107", "name": "IdeaTeam", "kind": "item" }, { "rel": "parent", "href": "https://servername/fscmRestApi/resources/version/ideas/300100240921318", "name": "ideas", "kind": "item" } ] }