Create a relationship
post
/fscmRestApi/resources/11.13.18.05/productConcepts/{ConceptId}/child/Relationships
Request
Path Parameters
-
ConceptId(required): integer(int64)
Value that uniquely identifies the concept.
Header Parameters
-
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.
-
Upsert-Mode:
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
- application/json
Root Schema : schema
Type:
Show Source
object
-
Description: string
Description of the related object.
-
DestObjId: integer
(int64)
Value that uniquely identifies the destination object.
-
DestObjType: string
Maximum Length:
30
Type of the destination object. -
LatestFlag: boolean
Contains one of the following values: true or false. If true, then the related object is the latest. If false, then the related object is not the latest. This attribute does not have a default value.
-
Name: string
Name of the related object.
-
RelationshipType: string
Title:
Relationship Type
Maximum Length:30
Type of relationship. -
Revision: string
Maximum Length:
255
Value that indicates the version or revision of the referenced object. -
SrcObjId: integer
(int64)
Value that uniquely identifies the source object.
-
SrcObjType: string
Maximum Length:
30
Type of the source object. -
Status: string
Status of the related object.
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 : productConcepts-Relationships-item-response
Type:
Show Source
object
-
CreatedBy: string
Read Only:
true
Maximum Length:64
User who created the relationship. -
CreationDate: string
(date-time)
Read Only:
true
Date when the user created the relationship. -
Description: string
Description of the related object.
-
DestObjId: integer
(int64)
Value that uniquely identifies the destination object.
-
DestObjType: string
Maximum Length:
30
Type of the destination object. -
LastUpdateDate: string
(date-time)
Read Only:
true
Date when the user most recently updated the relationship. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
User who most recently updated the relationship. -
LatestFlag: boolean
Contains one of the following values: true or false. If true, then the related object is the latest. If false, then the related object is not the latest. This attribute does not have a default value.
-
LatestFlagName: string
Read Only:
true
Name of the latest flag. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
Name: string
Name of the related object.
-
RelationshipId: integer
(int64)
Read Only:
true
Value that uniquely identifies the relationship. -
RelationshipType: string
Title:
Relationship Type
Maximum Length:30
Type of relationship. -
Revision: string
Maximum Length:
255
Value that indicates the version or revision of the referenced object. -
SrcObjId: integer
(int64)
Value that uniquely identifies the source object.
-
SrcObjType: string
Maximum Length:
30
Type of the source object. -
Status: string
Status of the related object.
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 relationship.
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/productConcepts/ConceptId/child/Relationships"
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.
{ "DestObjType" : "CHANGE", "DestObjId" : 300100238393092 }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "RelationshipId" : 300100238394770, "RelationshipType" : null, "CreatedBy" : "PLM_AUTO", "CreationDate" : "2020-03-05T12:26:01+00:00", "LastUpdateDate" : "2020-03-05T12:26:03.750+00:00", "LastUpdatedBy" : "PLM_AUTO", "DestObjType" : "CHANGE", "DestObjId" : 300100238393092, "SrcObjType" : "CONCEPT", "SrcObjId" : 300100171077730, "Name" : "ECO23456", "Description" : "Design changes based on failure analysis findings", "Status" : "Draft", "LatestFlag" : "true", "LatestFlagName" : "Yes", "RelationshipTypeName" : null, "DestObjTypeName" : "Changes", ... }