Automation

Overview

Apache Solr provides a feature that goes by the name of "best bets", "sponsored searches", or "editorial boosting" depending on the technology you are used to using. Simply put, administrators can configure which documents are explicitly promoted to the top of the search results or excluded from the result set based on the keywords entered by the user. Common use cases are featured product pages in e-commerce applications or a sponsored article that should always be returned first for certain queries.

This module provides an interface for users to configure which content is a "best bet" for various search terms. On the technical side of things, Solr Best Bets generates a valid elevate.xml configuration file that can be deployed to a Solr server. This module does not automatically deploy the configuration file to Apache Solr, as there is currently no mecanism native to Solr that supports this. Users must create their own method for deploying the file constructed by this module.

Rules Mail Edit adds rules actions to allow rules to send emails to single users or users of a role using Mail Edit templates. It does support rules tokens.

Provides Views directly as Rules actions and loops to seamlessly use view result data.

This module provides two rules conditions based on URL arguments:

This module provides a framework for integration between the entity metadata API and Drupal variables.

Settings API is useful for situations where you want to use client-defined values in Rules but you do not want to package those values in Rules definitions. A good example of this is tokenized templates. This module lets you treat these as content rather than configuration and avoid having to package them with your feature.

Use-case 1: You want to use this module to track email template content outside of your feature. There is a submodule called "Settings API Mail" to handle this.

1. hook_settings_api_mail_mail_types() to define your mail template
2. Set up a "send email" rules action and point the "body" and "subject" data selectors to the respective metadata properties provided by Settings API

Use-case 2: You want to expose Drupal variables as entity metadata.

• Use hook_settings_api_variable_properties() to define your variables to the entity metadata framework. They will now be accessible in rules off whatever entity type you specified for "attach."

This module integrates Supscriptions with Rules.
Features:
- Subscribe user to node
- Unsubscribe user from node
- Subscribe user to node type