• v3.2
    • Versions
    • v3.2

 

  • Install Akeneo PIM
    • Install Akeneo PIM with Docker
    • Install Akeneo PIM manually
      • System Requirements
      • System installation on Debian 9 (Stretch)
      • System installation on Ubuntu 16.04 (Xenial Xerus)
      • Installing Akeneo PIM Community Edition (CE) with the Archive
      • Installing Akeneo PIM Enterprise Edition (EE) with the Archive
      • Setting up the job queue daemon
    • How to customize the Dataset
    • How to Add Translation Packs
  • Migrate Akeneo PIM projects
    • How to apply a patch?
      • How to apply a patch - Community Edition
      • How to apply a patch - Enterprise Edition - Flexibility Cloud offer
      • How to apply a patch - Enterprise Edition - On Premise offer
    • Where is the Changelog?
    • How to upgrade to a minor version?
    • How to upgrade to a major version?
  • Import and Export data
    • How import works
    • Understanding the Product Import
    • Understanding the Product Export
    • Formats
      • Localized labels
      • Scopable labels
      • Association types data structure
      • Attribute data structure
      • Category data structure
      • Family data structure
      • Family variant data structure
      • Group data structure
      • Options data structure
      • Product data structure
      • Product model data structure
    • Akeneo Connectors
    • How to Customize Import / Export
      • How to create a new Connector
      • How to import Products from a XML file
      • How to clean a CSV file during a Product import
      • How to automate imports/exports
  • Manipulate the Akeneo PIM data
    • How to Customize Mass Edit Operations
      • How to register a new bulk action
      • How to Register a New Mass Edit Action on Products
      • How to Avoid Rules Execution on Mass Edit Actions
    • How to Manipulate Products
      • How to Query Products
      • How to Create Products
      • How to Update Products
      • How to Validate Products
      • How to Save Products
      • How to Remove Products
    • How to Manipulate Non-Product Objects
      • How to Query Non-Product Objects
      • How to Create Non-Product Objects
      • How to Update Non-Product Objects
      • How to Validate Non-Product Objects
      • How to Save Non-Product Objects
      • How to Remove Non-Product Objects
    • How to add a custom action rule
      • General information about rule format
      • How to add a custom action in the rule engine
    • How to Define Access Control List
    • How to Customize the Catalog Structure
      • How to Create a Reference Data
      • How to add a custom unit of measure
      • How to Add New Properties to a Category
    • How to Customize Product Assets
      • How to Add a New Transformation
      • How to Add a Default Thumbnail For Unknown File Types
      • How to connect to an external server for storage
      • How to change the validation rule to match a reference file to an asset
      • How to Mass Import Assets
    • How To Customize Teamwork Assistant (Enterprise Edition)
      • Customize notifications
      • Add a calculation step
      • How to log calculation step
      • Remove projects impacted by a custom catalog update
  • Design the user interfaces
    • How to customize any frontend part of the application
    • How to add an action button or meta data to the product edit form
    • How to add a tab to a form
    • How to add a new tab in System / Configuration
    • How to add custom information to a field
    • How to add a new field type
    • Create a custom product export builder filter
    • How to create the UI to manage a Reference Data
    • How to add a new page
    • How to customize the main menu
    • Styleguide
  • Maintain Akeneo PIM projects
    • First aid kit
    • Bug qualification
    • Common issues
    • Scalability Guide
      • Audit with 3 Representative Catalogs
      • More than 10k attributes?
      • More than 10k families?
      • More than 10k categories?
      • More than 500 attributes usable in the product grids?
      • More than 100k products to export?
      • More than 1GB of product media to export?
    • How to purge history
      • How to Purge jobs executions
      • How to adapt the version purger to your needs
  • Contribute to Akeneo PIM
    • How to report an issue?
    • How to translate the user interface?
    • How to enhance the documentation?
    • How to contribute to a Connector?
    • How to submit a patch to the PIM?
    • How to contribute to the frontend part of the application
    • How behavior tests are architectured in the PIM?
      • Establishing Decorator Pattern
      • Using Spin In Behat
  • Use SSO authentication locally
  • Reference Entities (beta)
    • Configure Entity Limits
    • Create a new Reference Entity Attribute type
    • Enrich Records with a new Reference Entity Attribute type
    • Add a Custom Property to Your Custom Attribute Type
    • Refresh records completeness
  • Technical overview
    • Product Information
    • Teamwork Assistant (Enterprise Edition)
      • Project creation
      • Project completeness
      • Project Completeness widget
      • Catalog update impact
      • Scalability guide
      • Users permission summary for Behat tests
    • Collaborative workflow
      • Simple workflow
      • Partial workflow
  • Technical architecture
    • Best Practices
      • Create a project
      • Create a reusable bundle
      • Setup Behat
      • Code Conventions
      • Coding Standards
    • How to implement your business logic using the event system
    • Events
      • Storage events
      • Workflow events (Enterprise Edition only)
    • How to Localize your data
      • How to change the PIM locale
      • How to Use Localizers
      • How to use Presenters
    • How to Add a Notification
    • Performances Guide
      • Memory usage of rules execution (Enterprise Edition)
      • Memory leak fix in Rules Engine (ORM)
      • More than 100 WYSIWYG editors in a page
      • PHP7 and HHVM Compatibility?
      • Job product batch size
    • How to Use the Web REST API
    • Standard format
      • Products
      • Other entities
      • Usage
    • Application Technical Information
      • Application Technical Dependencies
      • Server side set up for hosting
      • System Requirements
      • Recommended configuration
      • Client side configuration and compatibilities
      • Operation processes
      • Flow Matrix
  • Akeneo Cloud Edition
    • Flexibility Mode
      • Overview
      • Partners Starterkit
      • Environments Access
      • Composer settings
      • Periodic tasks / Crontab settings
      • PIM Application
      • PIM Updates and Migrations
      • File Transfer (SFTP)
      • Backups management
      • Partners
      • Queue management
      • System Components
      • Disk Usage
      • Ensure the Onboarder worker is always running
    • Serenity Mode
      • Overview
      • PIM Updates and Migrations
  • Akeneo Onboarder
    • Prerequisites
    • Installation
    • Migrate Akeneo Onboarder projects
      • How to apply a patch?
        • How to apply an Onboarder patch - Enterprise Edition - Flexibility Cloud offer
        • How to apply an Onboarder patch - Enterprise Edition - On Premise offer
      • How to upgrade to a minor version?
      • How to upgrade to a major version?
    • Synchronization
    • Troubleshooting
    • Environment variables
      • Using the DotEnv file
      • Using environment variables

How to Avoid Rules Execution on Mass Edit Actions¶

The Akeneo PIM comes with a number of mass edit actions.
By default in Enterprise Edition, after each of those actions, rules are applied for updated products.
Please follow this cookbook if you don’t want rules to apply for some reason.

Quick Overview¶

Note

This cookbook is about a feature only provided in the Enterprise Edition.

This cookbook assumes that you already created a new bundle to add your custom rule. Let’s assume its namespace is Acme\CustomBundle.

One Service to Override¶

For this cookbook let say we don’t want to apply rules after a Mass Edit Common Attributes operation.
Currently, this operation is defined as follows:
# src/PimEnterprise/Bundle/EnrichBundle/Resources/config/mass_actions.yml

pim_enrich.mass_edit_action.edit_common_attributes:
    public: false
    class: %pim_enrich.mass_edit_action.edit_common_attributes.class%
    arguments:
        - '@pim_catalog.builder.product'
        - '@pim_user.context.user'
        - '@pim_catalog.repository.attribute'
        - '@pim_catalog.updater.product'
        - '@pim_catalog.validator.product'
        - '@pim_internal_api_serializer'
        - '@pim_catalog.localization.localizer.converter'
        - '@pim_catalog.localization.localizer.registry'
        - '@pim_enrich.filter.product_values_edit_data'
        - '%tmp_storage_dir%'
        - 'edit_common_attributes_with_permission_and_rules'        # <<<< The batch job code that will run in background
    tags:
        -
            name: pim_enrich.mass_edit_action
            alias: edit-common-attributes
            acl: pim_enrich_product_edit_attributes
            datagrid: product-grid
As you can see in the service declaration above, by default in Enterprise Edition, the job used to Edit Common Attributes is edit_common_attributes_with_permission_and_rules.
This job has multiple steps, including the rule execution step.
All you have to do is to redefine this service and inject another existing job code: edit_common_attributes_with_permission.
This job is part of the minimal data fixtures and is already in database. Here is what it looks like:
# src/Acme/Bundle/CustomBundle/Resources/config/mass_actions.yml

pim_enrich.mass_edit_action.edit_common_attributes:
    public: false
    class: %pim_enrich.mass_edit_action.edit_common_attributes.class%
    arguments:
        - '@pim_catalog.builder.product'
        - '@pim_user.context.user'
        - '@pim_catalog.repository.attribute'
        - '@pim_catalog.updater.product'
        - '@pim_catalog.validator.product'
        - '@pim_internal_api_serializer'
        - '@pim_catalog.localization.localizer.converter'
        - '@pim_catalog.localization.localizer.registry'
        - '@pim_enrich.filter.product_values_edit_data'
        - '%tmp_storage_dir%'
        - 'edit_common_attributes_with_permission'        # <<<< Notice we do not use rules anymore with this job code
    tags:
        -
            name: pim_enrich.mass_edit_action
            alias: edit-common-attributes
            acl: pim_enrich_product_edit_attributes
            datagrid: product-grid

Available Mass Edit Operation Jobs Without Rules¶

The previous example was for the Mass Edit Common Attributes operation. If you want to customize another operation, please proceed the exact same way but by using one of these jobs.
Here are the mass edit jobs that can be ran without rules execution:

Classify, Add to Groups:

  • add_product_value: Add product value (CE default)
  • add_product_value_with_permission: Add product value with EE permission check (EE Only)
  • add_product_value_with_permission_and_rules: Add product value with EE permission check & rules application (EE Only, EE default)

Change Status, Change Family:

  • update_product_value: Update product value (CE default)
  • update_product_value_with_permission: Update product value with EE permission check (EE Only)
  • update_product_value_with_permission_and_rules: Update product value with EE permission check & rules application (EE Only, EE default)

Edit Common Attributes:

  • edit_common_attributes: Edit common attributes (CE Default)
  • edit_common_attributes_with_permission: Edit common attributes with EE permission check (EE Only)
  • edit_common_attributes_with_permission_and_rules: Edit common attributes with EE permission check & rules application (EE Only, EE Default)

Note

All mass edit operation jobs are in the minimal data fixtures and declared in src/PimEnterprise/Bundle/InstallerBundle/Resources/fixtures/minimal/jobs.yml


Found a typo or a hole in the documentation and feel like contributing?
Join us on Github!