Sample Deal Version Creation Request and Response in the JSON Format

Using the below example, you can create deal version for the deal 6287907587.

Sample Deal Version Creation Request in the JSON Format

{
    "C1-DealCreationUpdateIWS":
    {
        "actionFlag" :"ADD",
        "dealOperation"
        {
            "operationFlag" :"CRDV",
            "dealId" :"6287907587",
            "modelId" :"5765155419",
            "dealVersionDescription" :"Version 2",
            "dealVersionCreationFlag" :"FLHR",
         }
    }
}

Note: If you do not want to enter the data in the list attributes (i.e. attributes where the type is set to list), you should not include them in the request. Adding empty list attributes will give erroneous results.

Sample Deal Version Creation Response in the JSON Format

{
    "C1-DealCreationUpdateIWS":
    {
        "actionFlag" :"ADD",
        "dealResponse"
        {
        message" :"Deal Version created successfully.",
        }
        "dealOperation"
        {
            "operationFlag" :"CRDV",
            "dealIdentifier" :"",
            "dealId" :"6287907587",
            "modelId" :"5765155419",
            "dealVersionDescription" :"Version 2",
            "dealVersionCreationFlag" :"FLHR",
        }
        "dealDetails"
        {
            "dealId" :"9953437478",
            "modelId" :"8149209383",
            "dealEntityType" :"",
            "customerSegment" :"",
            "customerTier" :"",
            "division" :"",
            "accessGrp" :"",
            "dealEntityId" :"",
            "contractedDealFlag" :"false",
            "currency" :"",
            "dealTypeCode" :"",
            "startDate" :"",
            "endDate" :"",
            "simulationTypeFlag" :"false",
            "reviewFrequency" :"",
            "dealDescription" :"",
            "longDescription" :"",
            "dealVersionDescription" :"",
            "dealFrequency" :"",
            "skipReferenceFlag" :"",
            "priceSelectionDate" :"",
            "usagePeriod" :"",
            "includeHierarchyFlag" :"false",
            "status" :"",
            "dealVersionStatus" :"PSML",
            "templateFlag" :"false",
            "createdDate" :"",
            "acceptanceDate" :"",
            "finalizedDate" :"",
            "effectiveStartDate" :"",
            "effectiveEndDate" :"",
            "reviewedDate" :"",
        }
        "templateReferenceDetails"
        {
            "templateDealId" :"",
            "templateDealIdentifier" :"",
            "templateModelId" :"",
            "copyBasicDetailsFlag" :"false",
            "copyPricingFlag" :"false",
            "copyUsageFlag" :"false",
        }
        "referenceDetails"
        {
            "referenceTypeFlg" :"",
            "refPersonIdentifierType" :"",
            "refPersonIdentifier" :"",
            "referPersonId" :"",
            "refAccountIdentifierType" :"",
            "refAccountIdentifier" :"",
            "referAccountId" :"",
            "referDealIdentifier" :"",
            "referenceDealId" :"",
            "referenceModelId" :"",
            "referUsageSw" :"false",
            "referPriceSw" :"false",
            "includeChildHierarchy" :"false",
            "division" :"",
        }
    }
}

Note: We have given the above request and response samples to illustrate how the attribute value pairs should be structured while sending a deal version creation request from the external system. However, you should not seamlessly use this request sample in your environment because the required pre-requisite data may not be available in your environment. In such case, the system will give erroneous results.

Related Topics

For more information on...	See...
Deal update request and response attribute/value pairs in the JSON format	Deal Update Request and Response - Attribute/Value Pairs in the JSON Format