Create a business plan SWOT
post
/crmRestApi/resources/11.13.18.05/businessPlans/{BusinessPlanId}/child/Swot
Request
Path Parameters
-
BusinessPlanId(required): integer(int64)
The unique identifier of the business plan.
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
-
BusinessPlanId: integer
(int64)
Title:
Business Plan ID
The unique identifier of the business plan. -
BusinessPlanNumber: string
Title:
Business Plan Number
Maximum Length:64
Parent puid. -
Description: string
Title:
Description
Maximum Length:2000
The description of the SWOT. -
SWOTId: integer
(int64)
Title:
SWOT ID
The unique identifier of the business plan SWOT. -
SWOTNumber: string
Title:
Number
Maximum Length:64
The alternate key identifier for the business plan SWOT. -
SWOTTypeCode: string
Title:
Type Code
Maximum Length:30
The code indicating the type of business plan SWOT. A list of valid values is defined in the lookup ORA_ZCA_BUS_PLAN_SWOT. Possible values are Opportunity, Strength, Threat, or Weakmess.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
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.
Root Schema : businessPlans-Swot-item-response
Type:
Show Source
object
-
BusinessPlanId: integer
(int64)
Title:
Business Plan ID
The unique identifier of the business plan. -
BusinessPlanNumber: string
Title:
Business Plan Number
Maximum Length:64
Parent puid. -
CreatedBy: string
Title:
Created By
Read Only:true
Maximum Length:64
The user who created the record. -
CreationDate: string
(date-time)
Title:
Creation Date
Read Only:true
The date when the record was created. -
Description: string
Title:
Description
Maximum Length:2000
The description of the SWOT. -
LastUpdateDate: string
(date-time)
Title:
Last Updated Date
Read Only:true
The date when the record was last updated. -
LastUpdatedBy: string
Title:
Last Updated By
Read Only:true
Maximum Length:64
The user who last updated the record. -
LastUpdateLogin: string
Title:
Last Update Login
Read Only:true
Maximum Length:32
The login of the user who last updated the record. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
SWOTId: integer
(int64)
Title:
SWOT ID
The unique identifier of the business plan SWOT. -
SWOTNumber: string
Title:
Number
Maximum Length:64
The alternate key identifier for the business plan SWOT. -
SWOTTypeCode: string
Title:
Type Code
Maximum Length:30
The code indicating the type of business plan SWOT. A list of valid values is defined in the lookup ORA_ZCA_BUS_PLAN_SWOT. Possible values are Opportunity, Strength, Threat, or Weakmess.
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
The following example shows how to create a business plan SWOT by submitting a POST request on the REST resource using cURL.
cURL Command
- curl -u <username:password> \ -X http://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/businessPlans/300100091979253/child/Swot
Example of Request Body
The following shows an example of the request body in JSON format..
{ "SWOTTypeCode":"THREAT", "Description":"New Threat" }
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "BusinessPlanId": 300100091979253, "SWOTId": 300100091979257, "CreatedBy": "MHoope", "CreationDate": "2016-12-12T03:32:28-08:00", "LastUpdateDate": "2016-12-12T03:32:28-08:00", "LastUpdateLogin": "4373F6AF02325539E05364C0F20A8DA6", "LastUpdatedBy": "MHoope", "Description": "New Threat", "SWOTTypeCode": "THREAT", "SWOTNumber": "CDRM_1001", ... }