Differences

This shows you the differences between two versions of the page.

appendixd:simple_product_administration:product_admin_webmethod_inputxml [2016/12/08 09:56]
fpasovic [Example No. 11 - Set responder template]
appendixd:simple_product_administration:product_admin_webmethod_inputxml [2018/11/30 03:26] (current)
bdjordje
Line 5: Line 5:
 The following XML enables the process of effective dates for product and attributes: //AttributeType, AttributeSystemId, Display Type for product and attributes, Rank// and //Value Code// for attributes. Supported values for the //Product Display Type// are: //Simple, Configurable, System, Collection// and //Parent/Child//.  The following XML enables the process of effective dates for product and attributes: //AttributeType, AttributeSystemId, Display Type for product and attributes, Rank// and //Value Code// for attributes. Supported values for the //Product Display Type// are: //Simple, Configurable, System, Collection// and //Parent/Child//. 
  
-Supported values for Attribute Display Type are as follows: //UserSelection, Date, String, Number, Att.Quantity, AttValue.Quantity, ExternalValue, Measurement, Container// (Attribute type container can be created over API call and the system will be able to add an attribute type container to a product if that attribute already exists within CPQ. When attribute type “Container” is created over API call, this container attribute will not have any other properties such as columns, properties, validation messages set up over API call).+Supported values for Attribute Display Type are as follows: //UserSelection, Date, String, Number, Att.Quantity, AttValue.Quantity, ExternalValue, Measurement, Container// (Attribute type container can be created over API call and the system will be able to add an attribute type container to a product if that attribute already exists within SAP CPQ. When attribute type “Container” is created over API call, this container attribute will not have any other properties such as columns, properties, validation messages set up over API call).
  
 <code xml> <code xml>
Line 56: Line 56:
 ===== Example No. 2 ===== ===== Example No. 2 =====
  
-The following XML is for a new attribute type - Measurement. You will need one more node,<UnitOfMeasurement>, for Measurement type. Supported values are as follows: Measurement types that have already been defined in CPQ. It is not possible to create a new Measurement type via API call.+The following XML is for a new attribute type - Measurement. You will need one more node,<UnitOfMeasurement>, for Measurement type. Supported values are as follows: Measurement types that have already been defined in SAP CPQ. It is not possible to create a new Measurement type via API call.
  
 <code xml> <code xml>
Line 104: Line 104:
 ===== Example No. 3 ===== ===== Example No. 3 =====
    
-The following XML enables you to create a Product with Attribute, which is //Line Item and Required//, and contains //Line Item Description//, //Rank within cart, Label, Hint,// and checkbox for //Spans across entire row, Show one time price// and //Show recurring price//. +The following XML enables you to create a Product with Attribute, which is //Line Item and Required//, and contains //Line Item Description//, //Rank within cart, Label, Hint,// and checkbox for //Spans across the entire row, Show one time price// and //Show recurring price//. 
  
 Supported values for checkbox include the following: 1 for Yes, 0 for No. You should send “0 “value to deselect this option.  Supported values for checkbox include the following: 1 for Yes, 0 for No. You should send “0 “value to deselect this option. 
Line 237: Line 237:
 ===== Example No. 5 ===== ===== Example No. 5 =====
  
-The following XML is for <Preselected> and <IsFirstValuePreselected>, when sending attributes. It enables the processing of attributes whose first value is always preselected, according to standard CPQ behavior. +The following XML is for <Preselected> and <IsFirstValuePreselected>, when sending attributes. It enables the processing of attributes whose first value is always preselected, according to standard SAP CPQ behavior. 
  
 Supported values are as follows: “1” for True, while “0" value is sent when this flag should be deselected. For the first value use <IsFirstValuePreselected>; for other values use preselected, same supported values. Supported values are as follows: “1” for True, while “0" value is sent when this flag should be deselected. For the first value use <IsFirstValuePreselected>; for other values use preselected, same supported values.
Line 308: Line 308:
 Supported values include the following: Supported values include the following:
  
-     * **LayoutTemplate** - string. This is tab configuration’s exact name. In order to set the tab layout template over  API call, that file must have been created in CPQ already; otherwise the tab won’t be added to the system.+     * **LayoutTemplate** - string. This is tab configuration’s exact name. In order to set the tab layout template over  API call, that file must have been created in SAP CPQ already; otherwisethe tab won’t be added to the system.
      * **VisibilityPermission** - 0 (Always displayed), 1 (Display only if it is not empty), 2 (define condition for visibility)      * **VisibilityPermission** - 0 (Always displayed), 1 (Display only if it is not empty), 2 (define condition for visibility)
      * **Show tab header in configuration** - “1” as True, while the “0" value is sent when this flag should be deselected.      * **Show tab header in configuration** - “1” as True, while the “0" value is sent when this flag should be deselected.
Line 443: Line 443:
 ===== Example No. 7 ===== ===== Example No. 7 =====
  
-The following XML is for setting the Global IPython script. To set the script add a new child node <GlobalScripts> to <Product> input XML node.  Parent GlobalScripts node has a child node, Script, and nodes within Script node are as follows: Name, Rank, Event.+The following XML is for setting the Global IPython script. To set the script add a new child node <GlobalScripts> to <Product> input XML node.  Parent GlobalScripts node has a child node, Script, and nodes within the Script node are as follows: Name, Rank, Event.
  
 For the Name node you must use the Exact Script Name; supported values for Events are as follows:   For the Name node you must use the Exact Script Name; supported values for Events are as follows:  
You are here: SAP Sales Cloud CPQ Online HelpSAP CPQ APISimple Product Administration Web MethodPRODUCT ADMINISTRATION - Input XML Examples