We are pleased to announce the release of Gravity Flow 2.9. A major release, 2.9 sees an important addition that we know many of our Gravity Flow customers are going to enjoy – Editable Fields for all step types!

For anyone with an active license, Gravity Flow 2.9.2 is now available to update from within your WordPress Admin, or download from your Account area. Update today to get the most out of Gravity Flow!

Ready to find out more about Gravity Flow 2.9 and the Editable Fields setting? Let’s jump in…

Gravity Flow 2.9: Editable Fields

A much requested feature, with Gravity Flow 2.9 you can now define or select Editable Fields on all step types, streamlining your workflows and allowing assigned users to easily edit specific fields.

The Approval Step

The majority of us will see a big improvement in workflow design when using the Editable Field setting in an Approval step.

Anywhere that you might currently use a combination of Approval Step with the Revert setting connected to a User Input step for the same assignee to make modifications can now be handled as a single Approval step.

Within the Approval step under Editable Fields, simply define which of the fields you’d like to make editable, clicking to move fields from left to (editable) right – just as you would when applying Editable Fields to a User Step.

It is worth noting that if a step has lots of fields or a few very large paragraph fields, converting to an Approval step may not be ideal as it does not have the Save Progress setting which User Input steps provide. If you do not expect an assignee to complete writing or reviewing essays or large applications, the save progress setting which bypasses required field validation is essential. It is only when they select to submit the step – to indicate they are done – that validation occurs.

Check out the Gravity Flow documentation on Configuring the Approval Process for more information on using the Editable Field setting with the Approval step.

Custom Steps

Our custom workflow step framework is designed to give you as much flexibility as your use cases or integrated business environments might require, while ensuring all entries and workflows run smoothly with Gravity Flow coordinating across the different step types.

With 2.9, any custom steps you have created can incorporate the Editable Fields setting by:

• Defining a trait at the start of the class via use Editable_Fields;
• Ensuring your get_settings function includes the standard assignee type, list and routing calls.

public function get_settings() {
	return array(
		'title'  =>; 'My Custom Step',
		'fields' => array(
			$settings_api->get_setting_assignee_type(),
			$settings_api->get_setting_assignees(),
			$settings_api->get_setting_assignee_routing(),
		),
	);
}

 

That will connect all the relevant functions and UI elements to allow editable fields to be defined and handled on your custom step.

For more information on adding the Editable Fields setting to custom steps, check out the Gravity Flow custom workflow step framework documentation.

Have Your Say on Gravity Flow!

Being able to define or select Editable Fields for all step types has been one of our most requested features to date, so we are delighted to release it in 2.9.

If you’d like to have your say on future versions of Gravity Flow, head on over to our Roadmap and vote for your favorite features!

Gravity Flow 2.9 Changelog

• All step types can now define ‘use Editable_Fields;’ as part of their step class to have the editable fields step setting / functionality added to the step.
• Updated Approval step type to include editable fields setting.
• Updated User Input step type to include editable fields setting.
• Updated step settings screens to reduce page reloads required to create/update a step.
• Fixed an issue that causes Nested Form fields on a User Input Workflow Step to produce a fatal error on submission.
• Fixed an issue with outgoing webhook steps displaying an error if a GET request includes no request field values.
• Fixed an issue with inbox settings flyout where the component’s icon is missing.
• Fixed an issue with editable fields which causes the setting to use the wrong UI.

Gravity Flow 2.9.1 Changelog

• API: Added filter gravityflow_step_notification_assignees to allow customization of notification assignees with syntax matching the gravityflow_step_assignees filter.
• API: Added support for gravityflow_editable_fields_[step_type] filter which any step type that supports editable fields will perform.
• API: Fixed support for gravityflow_editable_fields_user_input filter to perform after gravityflow_editable_fields filter.

Gravity Flow 2.9.2 Changelog

• Fixed an error where conditional routing settings cannot be saved on the notification step.

 

Not yet a Gravity Flow customer? Head on over to our Pricing page to check out the licenses and make a purchase today!