Utilities CRM-> EhP3-> Working with the BRFplus Editor
With CRM EhP3 we introduced the BRFplus rules framework into the Utilities solution. It is mainly used in the area of the product configuration based on the so called “Utilities simplified configuration”. IPC configuration is not supported. Also the complete PFC (product finder and configurator) which was delivered with CRM EhP3 is based on this rule framework.
We have had a lot of questions regarding integration of different fields from outside into the rules logic. One of these questions e.g. was how to make a decision of the BRFplus rule depended on the system user or the sales channel. Others asked for a possibility to read some information of the PoD in the background to use this also in a rule.
So we decided to deliver a functionality which automatically adds additional context parameters of fields in the results structure for the function to the BRFplus function or the top expression for the function. This is possible since CRM EhP3 SP03. In the meantime there is a huge range of attributes available. They are mainly structured into four different groups each with a lot of sub-attributes:
- Add Conditional Attribute from Current Product (You can add the product attributes for which the rule editor was started as inbound parameters for the BRFplus function.)
- Add Conditional Attribute from Main/Package Product (You can add all attributes for higher-level products (package product or main product in the structured document) as inbound parameters for the BRFplus function.)
- Add Conditional Attribute from PDO at Higher Level (You can add all attributes for higher-level products (package product or main product in the structured document) as inbound parameters for the BRFplus function.)
- Add Conditional Attribute from System Environment (You can generate condition columns for a decision table from system variables and general information for the context in which the BRFplus function is called. The system can for example evaluate the current user name or address data for the business partner identified in the call center environment)
Read more details in the available documentation of this functionality: