Differences

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

adminhelp:productadministration:products:rulesadmin [2018/11/29 08:18]
mnikolic
adminhelp:productadministration:products:rulesadmin [2019/04/25 08:35] (current)
bdjordje
Line 2: Line 2:
 ====== Rules Admin ====== ====== Rules Admin ======
  
-Rules allow creating limitations for the configuration of the product.  This ensures that the user is only able to create an accurate and valid configuration of the product.  Though not quite as user friendly as what Attribute Dependencies offers, the Rules section allows creating complex rules through the use of SAP CPQ tags.  It is not prerequisite to be an expert in CPQ tags, the Code Builder, which can be accessed during the creation of every rule, can help in creating these rules in a user friendly way. \\  +Rules allow creating limitations for the configuration of the product.  This ensures that the user is only able to create an accurate and valid configuration of the product.  Though not quite as user friendly as what Attribute Dependencies offers, the Rules section allows creating complex rules through the use of SAP CPQ tags.  It is not prerequisite to be an expert in SAP CPQ tags, the Code Builder, which can be accessed during the creation of every rule, can help in creating these rules in a user friendly way. \\  
-Each rule is created with a **Condition**, which determines whether or not the action will run, and an **Action**, which tells the system what to do when the condition is true.  Each rule is in essence an **IF **statement.  IF the condition is true, THEN the anything in the action field will run.  There are CPQ tags used especially for rules (and triggers, which are discussed in the [[adminhelp:productadministration:products:triggers|]] section) to create the condition and the action statements. To access the Rules section use the manual method of product definition and select the **Rules **link under the **Current Product** drop down. This brings up the **Rules Administration** screen shown in Figure A. \\ +Each rule is created with a **Condition**, which determines whether or not the action will run, and an **Action**, which tells the system what to do when the condition is true.  Each rule is in essence an **IF **statement.  IF the condition is true, THEN the anything in the action field will run.  There are SAP CPQ tags used especially for rules (and triggers, which are discussed in the [[adminhelp:productadministration:products:triggers|]] section) to create the condition and the action statements. To access the Rules section use the manual method of product definition and select the **Rules **link under the **Current Product** drop down. This brings up the **Rules Administration** screen shown in Figure A. \\ 
  
 {{ productadministration:products:rulesadminsmb2.jpg }} \\  {{ productadministration:products:rulesadminsmb2.jpg }} \\ 
Line 45: Line 45:
 ===== Simple product rules ===== ===== Simple product rules =====
  
-In CPQ Setup-> Products, when products are edited under tab ‘Rules’ , new table will be displayed called ‘Simple Rules’. This will be a different representation of current “Attribute Dependencies” (entry “Attribute Dependencies will not be removed from legacy editor). Regular rules will be displayed in widget called ‘Scripted Rules’. \\+In SAP CPQ Setup-> Products, when products are edited under tab ‘Rules’ , new table will be displayed called ‘Simple Rules’. This will be a different representation of current “Attribute Dependencies” (entry “Attribute Dependencies will not be removed from legacy editor). Regular rules will be displayed in widget called ‘Scripted Rules’. \\
 {{ :adminhelp:productadministration:products:adminrules.png }} {{ :adminhelp:productadministration:products:adminrules.png }}
 ;#;//Product rules//;#;  ;#;//Product rules//;#; 
Line 72: Line 72:
 **End Date**- This field is not required. It corresponds to second date in Effective Dates for Attribute Dependencies. **End Date**- This field is not required. It corresponds to second date in Effective Dates for Attribute Dependencies.
  
-**IF**- Admin will be able to look up attributes that are defined for this product through this field. When admin is adding new rule, there will be a text ‘type attribute name or value’ written in grey letters in this field. As soon as admin starts typing attribute name or value, CPQ will start looking for attribute names and value codes that have text that is entered within attributes defined for this product. Text that admin has entered will be displayed in bold. Maximum of 20 results will be displayed. Admin will be able to delete selected attribute name/value code by clicking on x sign. This field is required. It corresponds to conditioning attributes and their values in ‘Attribute Dependencies’+**IF**- Admin will be able to look up attributes that are defined for this product through this field. When admin is adding new rule, there will be a text ‘type attribute name or value’ written in grey letters in this field. As soon as admin starts typing attribute name or value, SAP CPQ will start looking for attribute names and value codes that have text that is entered within attributes defined for this product. Text that admin has entered will be displayed in bold. Maximum of 20 results will be displayed. Admin will be able to delete selected attribute name/value code by clicking on x sign. This field is required. It corresponds to conditioning attributes and their values in ‘Attribute Dependencies’
  
 **THEN**- Drop down will contain 3 entries : **THEN**- Drop down will contain 3 entries :
Line 80: Line 80:
 If application parameter ‘Show Allow Option for Simple product rules’ is set to TRUE, option Allow will also be displayed in the drop down (as the last option) If application parameter ‘Show Allow Option for Simple product rules’ is set to TRUE, option Allow will also be displayed in the drop down (as the last option)
  
-Admin will be able to look up attributes that are defined for this product through the lookup field. When admin is adding new rule, there will be a text ‘type attribute name or value’ written in grey letters in this field. As soon as admin starts typing attribute name or value, CPQ will start looking for attribute names and value codes that have text that is entered within attributes defined for this product. Text that admin has entered will be displayed in bold. Maximum of 20 results will be displayed. If admin has already added one attribute, when she wants to add another field, she will be able to add it only from the list of remaining attribute values of the same attribute. Those values will be displayed as soon as admin clicks in the next field. Admin won’t be able to add values from different attributes in THEN section. When admin starts typing something in the box, CPQ will look only for attribute values of the same attribute. Admin will be able to delete selected attribute name/value code by clicking on x sign. This field is required. It corresponds to dependent attributes and their values in ‘Attribute Dependencies’\\+Admin will be able to look up attributes that are defined for this product through the lookup field. When admin is adding new rule, there will be a text ‘type attribute name or value’ written in grey letters in this field. As soon as admin starts typing attribute name or value, SAP CPQ will start looking for attribute names and value codes that have text that is entered within attributes defined for this product. Text that admin has entered will be displayed in bold. Maximum of 20 results will be displayed. If admin has already added one attribute, when she wants to add another field, she will be able to add it only from the list of remaining attribute values of the same attribute. Those values will be displayed as soon as admin clicks in the next field. Admin won’t be able to add values from different attributes in THEN section. When admin starts typing something in the box, SAP CPQ will look only for attribute values of the same attribute. Admin will be able to delete selected attribute name/value code by clicking on x sign. This field is required. It corresponds to dependent attributes and their values in ‘Attribute Dependencies’\\
 {{ :adminhelp:productadministration:products:simplerule.png }} {{ :adminhelp:productadministration:products:simplerule.png }}
 ;#;//Product rules//;#; ;#;//Product rules//;#;
Line 86: Line 86:
 Page for adding/editing scripted rules will be changed so that condition and action are displayed in the similar way as for simple rules. Instead of ‘Condition’ there will be an IF field, and instead of ‘Action’ field there will be a THEN field. Everything else will rename as it is. Page for adding/editing scripted rules will be changed so that condition and action are displayed in the similar way as for simple rules. Instead of ‘Condition’ there will be an IF field, and instead of ‘Action’ field there will be a THEN field. Everything else will rename as it is.
  
-There will be 2 new application parameters added to CPQ Setup -> General -> Application Parameters -> General:+There will be 2 new application parameters added to SAP CPQ Setup -> General -> Application Parameters -> General:
 '//Display table for simple product rules'//(Default value:FALSE) and '//Show Allow Option for Simple product rules//'(Default value:FALSE) '//Display table for simple product rules'//(Default value:FALSE) and '//Show Allow Option for Simple product rules//'(Default value:FALSE)
  
Line 94: Line 94:
 Enovia is a Product Lifecycle Management (PLM) tool whose purpose is to act as a master data system for setting up products.  Enovia is a Product Lifecycle Management (PLM) tool whose purpose is to act as a master data system for setting up products. 
  
-CPQ supports Enovia Rules and can be enabled for users on request (email support).+SAP CPQ supports Enovia Rules and can be enabled for users on request (email support).
  
-In order to import Enovia Rules into CPQ, an admin user should develop a custom API Interface that will process the data and import it into CPQ. +In order to import Enovia Rules into SAP CPQ, an admin user should develop a custom API Interface that will process the data and import it into SAP CPQ. 
  
 {{:adminhelp:productadministration:products:eno_fin.png|}} {{:adminhelp:productadministration:products:eno_fin.png|}}
Line 103: Line 103:
  
      * Export message dictionary keys from the custom table RuleMessages_Translation      * Export message dictionary keys from the custom table RuleMessages_Translation
-     * Translate them out of CPQ+     * Translate them out of SAP CPQ
      * Import translation to this table      * Import translation to this table
  
Line 121: Line 121:
 All Enovia rule messages will be displayed in English language. All Enovia rule messages will be displayed in English language.
 \\  \\ 
-Product rule messages in CPQ will be translated to the user's language. +Product rule messages in SAP CPQ will be translated to the user's language. 
 \\ \\
-Translation will be managed in CPQ by the CPQ admin user. +Translation will be managed in SAP CPQ by the SAP CPQ admin user. 
 \\ \\
 If a certain rule message is not translated, that rule message will be displayed in the way it has arrived from Enovia.  If a certain rule message is not translated, that rule message will be displayed in the way it has arrived from Enovia. 
Line 135: Line 135:
 Messages will be translated to the user’s language.   Messages will be translated to the user’s language.  
  
-Enovia messages will appear in English. The translation of these messages will be managed in CPQ by the central admin. Product managers have the responsibility to detect when new translations are needed, and will request form the central admin to export appropriate translations files. Product managers will then organize correct translations of missing texts. After that, the translated file will be sent to the central admin who will import it into CPQ.+Enovia messages will appear in English. The translation of these messages will be managed in SAP CPQ by the central admin. Product managers have the responsibility to detect when new translations are needed, and will request form the central admin to export appropriate translations files. Product managers will then organize correct translations of missing texts. After that, the translated file will be sent to the central admin who will import it into SAP CPQ.
  
-=== Rules Execution Time in CPQ ===+=== Rules Execution Time in SAP CPQ ===
 \\ \\
 Product rules are executed at run time, that is at the moment the user runs product configuration, which includes the following:  Product rules are executed at run time, that is at the moment the user runs product configuration, which includes the following: 
Line 149: Line 149:
      * Disallow\\      * Disallow\\
  
-=== CPQ Rule Execution Failure ===+=== SAP CPQ Rule Execution Failure ===
 \\ \\
-If during rule execution CPQ cannot perform a rule action for any reason, it means one of the following:+If during rule execution SAP CPQ cannot perform a rule action for any reason, it means one of the following:
  
      * Attribute listed in a rule  cannot be found in loaded product configuration      * Attribute listed in a rule  cannot be found in loaded product configuration
Line 162: Line 162:
 A rule execution error in a product will be solved the following way:  A rule execution error in a product will be solved the following way: 
  
-  - The user will contact the CPQ admin user  +  - The user will contact the SAP CPQ admin user  
-  - The admin user will send the following message to Enovia from CPQ: "This product will be demoted in Enovia." +  - The admin user will send the following message to Enovia from SAP CPQ: "This product will be demoted in Enovia." 
-  - The CPQ admin can deactivate the product in CPQ if necessary  +  - The SAP CPQ admin can deactivate the product in SAP CPQ if necessary  
-  - If a certain product is deactivated, the user won’t be able to find this configuration in CPQ anymore +  - If a certain product is deactivated, the user won’t be able to find this configuration in SAP CPQ anymore 
  
 When a product has been deactivated, its configurations saved in the Favorite section will become invisible to end users.  When a product has been deactivated, its configurations saved in the Favorite section will become invisible to end users. 
Line 171: Line 171:
 When a product has been deactivated, the user will be able to access quoted configurations and edit them.  When a product has been deactivated, the user will be able to access quoted configurations and edit them. 
 \\ \\
-The message will be translated to the user’s language, except the part related to the name of the rule. The name will not be translated in CPQ, meaning that the system will take the original name of the rule in English.+The message will be translated to the user’s language, except the part related to the name of the rule. The name will not be translated in SAP CPQ, meaning that the system will take the original name of the rule in English.
 \\  \\ 
 All product rules will be loaded in Developer Console so the admin user will be able to debug any of them in case of error.  All product rules will be loaded in Developer Console so the admin user will be able to debug any of them in case of error. 
Line 177: Line 177:
 === Obsolete Features === === Obsolete Features ===
 \\ \\
-Attributes in CPQ won’t have effective dates.+Attributes in SAP  CPQ won’t have effective dates.
 \\ \\
 As a result, the rule engine does not need to consider effective dates in rule execution. As a result, the rule engine does not need to consider effective dates in rule execution.
Line 185: Line 185:
 **Syntax error** **Syntax error**
  
-The rule syntax is checked at the moment of product import. Each product rule will be checked before rules and the entire product are saved in CPQ.+The rule syntax is checked at the moment of product import. Each product rule will be checked before rules and the entire product are saved in SAP  CPQ.
 \\ \\
-The product will be saved in CPQ only when all product rules are syntactically correct.+The product will be saved in SAP  CPQ only when all product rules are syntactically correct.
 \\ \\
 Due to the syntax check of each rule, importing the product will not be instant and can take some time, depending on the size of the product data sent.  Due to the syntax check of each rule, importing the product will not be instant and can take some time, depending on the size of the product data sent. 
 \\ \\
-If there is at least one rule with the syntax error, CPQ will return a message about the error found and the product won’t be saved. +If there is at least one rule with the syntax error, SAP CPQ will return a message about the error found and the product won’t be saved. 
 \\ \\
-All product rules will be traced in CPQ Developer Console. +All product rules will be traced in SAP CPQ Developer Console. 
  
 {{:adminhelp:productadministration:products:dev_console.png|}} {{:adminhelp:productadministration:products:dev_console.png|}}
  
-The CPQ Admin user will be able to follow up on all product rules and debug rule execution directly in CPQ. +The SAP CPQ administrator will be able to follow up on all product rules and debug rule execution directly in SAP CPQ. 
  
 === Forbidden Characters === === Forbidden Characters ===
You are here: SAP Sales Cloud CPQ Online HelpAdmin Page HelpProduct AdministrationProductsRules Admin