In this guide, you’ll learn how to create rules in Shopware. Rules are created by the rule builder.
\nThis example will introduce a new rule, which checks if there’s currently a lunar eclipse or not. The shop owner is then able to react to a lunar eclipse with special prices or dispatch methods.<\/p>\n
To add your own custom rules for your plugin, you first need a plugin as a base. Therefore, you can refer to the Plugin Base Guide.
\n(https:\/\/developer.shopware.com\/docs\/guides\/plugins\/plugins\/plugin-base-guide)
\nYou also should be familiar with the Dependency Injection container as this is used to register your custom rule.<\/p>\n
To create a custom rule, we have to implement both backend (PHP) code and a user interface in the administration to manage it. Let’s start with the PHP part first, which handles the main logic of our rule.
\nFirst of all we need a new Rule class, in this example we will name it LunarEclipseRule. It will be placed in the directory \/src\/Core\/Rule. Our new class has to extend from the abstract class Shopware\\Core\\Framework\\Rule\\Rule. Below you can find an example implementation.<\/p>\n
\/src\/Core\/Rule\/LunarEclipseRule.php<\/p>\n
}<\/p>\n
public function getName(): string
\n{
\nreturn ‘lunar_eclipse’;
\n}<\/p>\n
public function match(RuleScope $scope): bool
\n{
\n\/\/ Not implemented in this example
\n$isCurrentlyLunarEclipse = $this->isCurrentlyLunarEclipse();<\/p>\n
\/\/ Checks if the shop owner set the rule to “Lunar eclipse => Yes”
\nif ($this->isLunarEclipse) {
\n\/\/ Shop administrator wants the rule to match if there’s currently a lunar eclipse.
\nreturn $isCurrentlyLunarEclipse;
\n}<\/p>\n
\/\/ Shop administrator wants the rule to match if there’s currently NOT a lunar eclipse.
\nreturn !$isCurrentlyLunarEclipse;
\n}<\/p>\n
public function getConstraints(): array
\n{
\nreturn [
\n‘isLunarEclipse’ => [ new Type(‘bool’) ]
\n];
\n}
\n}<\/p>\n<\/div>\n
As you can see, several methods are already implemented:<\/p>\n
After we’ve created our rule class, we have to register it in our services.xml and tag it as Shopware.rule.definition. Please keep in mind: The variables to be used in the rule have to be ‘protected’ and not ‘private’, otherwise, they won’t work properly.
\nNOTE : Never execute database queries or any other time consuming operations within the match() method of your rule, as it will drastically impact the performance of your store. Stick to the rule scope when evaluating whether your rule matches or not.<\/p>\n
You can access all active rules by using the getRuleIds method of the context.<\/p>\n
$context->getRuleIds();<\/span><\/p>\n Now we want to implement our new rule in the administration so that we can manage it. To achieve this, we have to call the addCondition method of the RuleConditionService, by decorating this service. The decoration of services in the administration will be covered in our Adding services guide. import ‘..\/core\/component\/swag-lunar-eclipse’;<\/p>\n Shopware.Application.addServiceProviderDecorator(‘ruleConditionDataProviderService’, (ruleConditionService) => { return ruleConditionService; As you can see, this is decorating the RuleConditionService by using its name ruleConditionDataProviderService. The decoration adds a new condition called lunar_eclipse. Make sure to match the name we’ve used in the getName method in PHP. Next, we define the component, in our case swag-lunar-eclipse, which is responsible for rendering the rule inside the administration. We will create this component in the next step. Furthermore, we defined a label, which will be displayed in the rule builder selection. The last option is the scope, which in our case is global, as we have not specified a specific one in our core class.<\/p>\n We also have to create a main.js file in our administration sources directory and import the decorator file we’ve created above. The main.js file is used as an entry point to load administration modules from Shopware plugins: import ‘.\/decorator\/rule-condition-service-decoration’;<\/span><\/p>\n Since we’ve registered our rule to the administration now, we’re still lacking the actual component swag-lunar-eclipse. As previously mentioned, we’ve already defined a path for it in our service decoration. So create the following directory: \/src\/Resources\/app\/administration\/src\/core\/component\/swag-lunar-eclipse. If you are not familiar with creating components in Shopware, take a look at our Add your own component guide.<\/p>\n Here’s an example of what this component could look like:<\/p>\n \/src\/Resources\/app\/administration\/src\/core\/component\/swag-lunar-eclipse\/index.js As you can see, our swag-lunar-eclipse has to extend from the sw-condition-base component and has to bring a custom template, which will be explained in the next step. Let’s have a look at each property and method. The first computed property is selectValues, which returns an array containing the values “true” and “false”. Those will be used in the template later on, as they will be the selectable options for the shop administrator. Do not get confused by the call this.$tc(‘global.sw-condition.condition.yes’), it’s just loading a translation by its name, in this case “Yes” and “No”.<\/p>\n Note: When dealing with boolean values, make sure to always return strings here!<\/p>\n The second and last computed property is isLunarEclipse, which uses a getter and setter to define the value of the condition.<\/p>\n The last step is, creating a template for our condition. We will create a new file called swag-lunar-eclipse.html.twig in the same directory as the component. In our template, we have to overwrite the block sw_condition_value_content. In this example we define a sw-single-select in this block.<\/p>\n plugin root>\/src\/Resources\/app\/administration\/src\/core\/component\/swag-lunar-eclipse\/swag-lunar-eclipse.html.twig<\/p>\n {% block sw_condition_value_content %}<\/p>\n {% endblock %}<\/p>\n<\/div>\n As you can see, our sw-single-select uses the previously created computed property selectValues as the options prop, and the value is saved into the variable isLunarEclipse. That’s it, your rule is now fully integrated.<\/p>\n We hope you’ve got a good set of answers to your questions from the above. For more professional consulting and development tasks do get in touch with iCreative technologies a Shopware business partner company, and upgrade your Shopware eCommerce Shop to the best in standard.<\/p>\n Know more about our Shopware Development Services<\/a>.<\/p>\nShowing rule in the administration<\/h2>\n
\n(https:\/\/developer.shopware.com\/docs\/guides\/plugins\/plugins\/administration\/add-custom-service)
\nCreate a new directory called \/src\/Resources\/app\/administration\/src\/decorator. In this directory we create a new file called rule-condition-service-decoration.js.
\n\/src\/Resources\/app\/administration\/src\/decorator\/rule-condition-service-decoration.js<\/p>\n
\nruleConditionService.addCondition(‘lunar_eclipse’, {
\ncomponent: ‘swag-lunar-eclipse’,
\nlabel: ‘Is lunar eclipse today’,
\nscopes: [‘global’]
\n});<\/p>\n
\n});<\/p>\n<\/div>\n
\n\/src\/Resources\/app\/administration\/src\/main.js<\/p>\nCustom rule component<\/h2>\n
\nimport template from ‘.\/swag-lunar-eclipse.html.twig’;<\/p>\n
\ntemplate,computed: {
\nselectValues() {
\nreturn [
\n{
\nlabel: this.$tc(‘global.sw-condition.condition.yes’),
\nvalue: true
\n},
\n{
\nlabel: this.$tc(‘global.sw-condition.condition.no’),
\nvalue: false
\n}
\n];
\n},isLunarEclipse: {
\nget() {
\nthis.ensureValueExist();if (this.condition.value.isLunarEclipse == null) {
\nthis.condition.value.isLunarEclipse = false;
\n}return this.condition.value.isLunarEclipse;
\n},
\nset(isLunarEclipse) {
\nthis.ensureValueExist();
\nthis.condition.value = { …this.condition.value, isLunarEclipse };
\n}
\n}
\n}
\n});<\/div>\nCustom rule component<\/h2>\n
To Conclude:<\/h4>\n