The purpose of this module is displaying a tooltip / popup / balloon when you hover over a day on a calendar block. This tooltip would contain a list of events occurring on that day.
The Drupal Portal Plus Authentication module provides authentication integration with the Portal Plus SOAP web service.
The module allows the user to login to Drupal via the normal Drupal user account or via the Portal Plus SOAP web service. If it's the first login using Portal Plus credentials then the user is created within Drupal in order to skip the SOAP request for future logins. Portal Plus is a service provided by www.TSG.com.
Drupal 7 version
The Drupal 7 version has additional features. These are:
Option to overwrite local password with PP password.
Option to only allow active (non-lapsed) Portal Plus members to log in.
Option to add a role to active Portal Plus members at login.
Option to remove same role from all but active Portal Plus members at login.
Dependencies
The core PHP SOAP library is used in the Drupal 7 version so there are no external dependencies.
This module offers a check box on the node form asking the author to allow the visitors of the node to send feedback/request for the node using the personal/site wide contact form.
This module provides an easy way for module/theme developers to assign class attribute values to the body element of all pages on a site based on the available user agent (web browser) viewport width.
The typical use for this is for using these class names in CSS selectors that determinine the number of columns in a flexible-width layout (eg. three columns on large viewports, two columns on smaller ones, a single column on low-resolution mobile devices); what's now known as responsive Web design. You might also want to adjust other properties such as margins, font size, etc.
The Maestro module is a workflow engine/solution that will facilitate simple and complex business process automation.
Maestro has a workflow engine that executes templates created using a visual workflow editor. The workflow engine runs in the backgound and executes the workflow tasks, testing the tasks execution results and branch the workflow if required. The workflow engine will run every x seconds and execute all tasks that are in the queue which have not yet completed. Once they execute and return a success status, the engine will archive them and step the workflow forward. Both these components have been developed to support any number of different task types.
Maestro has been built to be extended with new task types and now contains tasks that are aware of webforms, entityforms, content types, rules, triggers. Custom interactive functions and batch functions can be added for custom business logic or integration.
The following is a summary of the available task types that be used in a workflow template:
Content Type Task: Assign a task to a user to create a new content node - task definition allows you to select from available content types.