Automation

The idea of this module is to provide structured information about a commerce store that will integrate with rules and context.

This project is integration taskbar activity with rules module.

Entity Rules provides a page for selecting and creating Rules components that will be executed when different operations happen to an Entity of a particular bundle. This provides an alternative method of triggering Rules. Instead of adding entity related events to Reaction Rules you are able to select which Rules will fire from the bundle management page.

Currently the operations supported are create, update, delete, validation and form access. You are also able to pass different arguments to the Rules per bundle.

This module allows users you don't have access to the Rules UI to select Rules to be triggered for bundles that they can manage. This can be useful for module such as Entityforms, Entity Registration, and Entity Construction Kit.

Video Intro

For example usage see the Entity Rules Node Limits sandbox project. This creates 4 Form Access rules.

Want to help?

Adds conditions to field formatters. Configuration happens on the "Manage Display" screens of every entity type on a per field basis when clicking on the cogwheel on the right.

Supports

• Rules
• Field API fields
• Display Suite fields (only branch 2)

Simple conditions and actions

• Hide source field when target field is empty.
• Hide source field when target field is not empty.
• Hide source field when current user has specific roles.
• Hide source field on specific pages.
• Hide source field when target field contains a specific string.
• Hide source field when target field doesn't contain a specific string.
• Hide link field if title is empty.
• Hide date field if from/to has expired.

Rules actions

• Hide a field.
• Change image style.

Rules should always be a 'A field is rendered' event before they can be selected in the conditions dropdown on the "Manage Display" screens per field.

Dependencies

Field formatter settings

Comparison with Conditional Fields

• CF uses a complete separate interface.

It is not called god particle, it's the god damned particle

This module tries to explain the weight of modules by introduce the higgs field to drupal.

Maestro gives a great workflow module. One of the short coming is the inability to choose different flow templates in production.