Rules

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.

Read more

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.
Therefore the module finds the spin of the particles by count_files / 2.

Based on this this bad judgement module sets the weight of modules.

Maestro gives a great workflow module. One of the short coming is the inability to choose different flow templates in production. If you have developed a workflow template and assigned it to a custom module, it's not possible to change the flow template without changing code. This module provides the capability to change flow templates in production.
Modules that need this capability can publish the 'events' on which workflow will be initiated by implementing the

. These events can be mapped to the flow template using the Manage Templates menu. For initiating the workflow, the modules can initiate the workflow using the

For more information see the README.txt

The dev version supports the Features module.

The PDF Archive module provides the ability to generate PDF archives of any entity triggered by Rules actions. Both the entity view mode and role of the simulated user used for rendering the entity can be set per rule.

An example feature is included to demonstrate the configuration of this module.

PDF Archive was initially developed for Lab4 Web Design by Realityloop.

 

Required modules

• Libraries API
• Rules

Read more

This module allows you to to do use your favorite hook_form_alter techniques using rules

Objective:
Provide site developers access to all the power of the hook_form_alter through rules so they can store business logic along side other rules.

Currently provides:

• An event rules_hook_alter
• A condition to check the form id (option for contains or exact match)
• An action to set a form element value using three parameters [name][key] = value
• An action to set a form element [name] = array(...)
• Works with commerce_stock: all actions are available from the add to cart validation event. Can be used to create additional form actions like 'download product image'

You can set multiple properties of a form elements using multiple actions like #markup, #weight & #default_value.

You can create new form elements or modify existing once

You can reference nested elements for fieldsets in the format of:
{fieldset}/{fieldset}/{form element}

Also check out Rules Forms Support for similar functionality.

Read more

Rules Panes allow embedding Rules components as content panes in Panels (or so).

By default any parameters for the component are entered manually by the end user, but they can also be pre-populated with CTools contexts on the page (which will also hide the form input).

Videos introducing this module can be found here: http://www.youtube.com/playlist?list=PL5sq4vtv3sTHUpeR_f6r7WwDEcxPbYtw4

A presentation from DrupalCamp Stockholm 2013 can be found here: http://drupal.org/node/1931906