Administration

INTRODUCTION

The Filter Form Values module is a developer module that adds in pre-filtering of form values on forms.

This can be useful when you are doing some form level field access (as opposed to entity level field access and validation) and you want to filter out some fields so that their values don't affect the entity on save.

REQUIREMENTS

This module is a developer module and as such is specified as a requirement by other modules.

INTRODUCTION

The Entity Draft module adds an 'is_draft' base field to bundle enabled entities and enables saving drafts of entities. It adds a "Save Draft" (text is configurable) button to entity edit forms. Unlike node's "save unpublished", entities with fields that are set to required can be saved by using the Controlled Fields module which does it's own management of the required field setting. As an entity can be in a draft state but not actually valid with respect to filled in required fields, site manager's will have to manage the draft status e.g.

We’ve always had a challenge synchronizing content across Drupal environments.

We’ve seen significant progress in the management of system configuration; however, we lack an effective way to deploy content in a similar fashion.

As a result, we’ve spent a lot of time synchronizing content either through migration scripting, import and export files, or “good old fashion” copy and paste.

Configuration Management can get complex when evaluating configuration across different targets. A target is defined in settings.php and has an associated directory.

Some targets may contain a full config export, while others only have partial configuration sets. Partial configuration is perfect for maintaining a small subset of configuration that can be maintained for specific conditions. Such conditions may include multisite, environment-specific config, or development specific config.

INTRODUCTION

The Controlled Fields module adds in rudimentary control of field visibility on form displays whilst also handling whether a field is required or not. It currently only supports the field of type 'list_string' for the controlling field.

Field visibility is set on the form display using the field settings form and is achieved by setting the 'Parent conditional controlling field' and a corresponding 'Parent conditional controlling field value'.

INTRODUCTION

The Field Group Access module adds permissions for editing and viewing fields inside field groups.

At present this is only done for fields on forms and for the default form display.

REQUIREMENTS

No special requirements besides the field_group module.

INSTALLATION

Install as you would normally install a contributed Drupal module. See: https://www.drupal.org/documentation/install/modules-themes/modules-8

INTRODUCTION

The Workflow Field Groups module allows you to control which field groups may be accessed depending on the current workflow state. Control can be specified by role. Currently this only applies to form displays and not view displays. Different settings can also be set per form display mode.

REQUIREMENTS

Field Group module
Workflow module

The objective of this project is to build a field-based composite data type.

What is a composite data type? It's basically a field comprised of other fields.

The benefit of a field type is a more direct correlation to the entity it belongs to. This approach aligns composite functionality with standard field-based functionality.

Similar Solutions

This is the server module for Remote Reports. This module will return module and status reports when a connection is made with a correct API key.

Get update and status reports from multiple sites remotely. This module doesn't need AES.