We are happy to announce the release of Gravity Flow 3.1.
Version 3.1 continues the quality of life work we started in version 3.0, with two features designed to make workflow management faster and less repetitive.
There is a new choice routing step that automatically branches your workflows, based on the choice made by the issuer via a drop-down list or radio field. And you’ll find a new Send to Step bulk action that lets you move multiple entries into your workflow in one go. Plus a handful of minor improvements which we’ll detail below.
Read on to find out what’s new in Gravity Flow 3.1 and how to update today…
Gravity Flow 3.1 Overview
Gravity Flow 3.0 aimed to alleviate the day-to-day friction of creating and managing workflows – version 3.1 continues that momentum!
This version is smaller and more focused, but the two core features tackle two of Flow’s most repetitive tasks: setting up branching logic and moving inputs once a workflow is live.
Both save you clicks and scale better as your forms and workflows grow.
New Choice routing step: automatically branch your workflows
Gravity Flow could already create a branch in a workflow. The problem was that this usually involved a lot of conditional logic to set up and maintain.
This feedback from one of the first beta testers of version 3.1 summarizes just one of the many workarounds that our customers have already used…
“I’m looking forward to the new Choice Routing step! For years I’ve “simulated” this feature by using a dummy notification step that has no notifications selected. I make the dummy notification step conditional and set the next step to where I want the flow to go if the condition is met.”
Fortunately, the new Choice Routing step gives us an easier and more flexible way to configure routing logic in the future.
Using choice routing
With Gravity Flow 3.1, you can now send inputs at different stages based on the author’s selection in a drop-down list or radio field. When an entry reaches the step, Flow verifies the choice and sends it to the corresponding route, without any user interaction needed.
During setup, you can create as many routes as needed, and each route can send one or more choices to the same step.
It’s important to note that each choice can only belong to one route, so there is no overlap and your route remains easy to manage as the form evolves.
If an entry comes in with a choice that doesn’t match any of your routes, the default step-by-step route is there to catch it, so nothing slips through the cracks.
Gravity Flow also records every routing decision in the entry’s timeline, so you can always see which path an entry took and why.
A common example
For this example, an agency uses a single intake form for new client inquiries, and each project type must reach a certain team.
With conditional routing, you can:
– Route web design and branding requests to the creative team.
– Send SEO and paid ad requests to the marketing team.
– Direct support and maintenance selections to the support team.
– Anything that doesn’t match returns to a general review stage.
In the future, when a new project type is added to the form, only the route table will need to be updated – no new steps, no restructuring.
For more information about the Choice Routing step, see the documentation.
Bulk Actions: Send multiple inputs to a step at once
Manually moving entries through a workflow, one at a time, is good when you have a handful. On a large number of entries, this gets old quickly.
With Gravity Flow 3.1, you’ll discover a new Send to Step bulk action, allowing you to select multiple inputs and send them to a specific step in a single action.
If a batch of entries is stuck waiting for approval that has already been processed elsewhere, or if you need to return a group of submissions to a user input stage for further review, simply select them in bulk, choose the stage, and Flow moves them all at once.
The available Send to Step options depend on the form, since each form has its own set of steps. For this reason, this action is available when the Status screen is filtered to a single form.
You’ll also find the same Send To Step action in the Gravity Flow Status block, so you can manage inputs this way from the front-end, not just from the admin.
For more information about the new Send to Stage bulk action, see the Status page and the block documentation.
More in 3.1
In addition to the two flagship features, version 3.1 includes a few improvements that are worth highlighting.
- Support for background notifications – Flow now supports the background notifications feature introduced in Gravity Forms 2.10. Notifications can be processed in the background, so form submissions appear faster for your users.
- Block API v3 for workflow blocks – Gravity Flow blocks are now compatible with the WordPress Block API v3, following the same work in Gravity Forms 3.0. This means better compatibility with current themes and a smoother experience integrating your workflow blocks into the block editor.
- GravityView integration improvements – Flow’s workflow approval fields are now available in the GravityView field picker in the Single Entry and Multiple Entry configuration tabs, and we’ve removed some outdated filter warnings on the Workflow Details and Workflow Approval links. Thanks to the GravityKit team for their help here.
- Gravity Forms 3.0 compatibility – With the Gravity Forms 3.0 beta now open for testing, we’ve made sure that the Assign To and Date Picker components display correctly when you run Gravity Forms 3.0.0 and later.
Update to Gravity Flow 3.1
Gravity Flow 3.1 is now available to all customers with an active license.
If automatic updates are enabled, you’re all set. Otherwise, open your WordPress dashboard, navigate to your plugins page and click to update to version 3.1. You can also download the latest version from your Gravity Flow account.
Are you new to Gravity Flow? Head to our pricing page to get started or sign up for a personalized demo of Gravity Flow 3.1 to see it in action.
Questions about new features or updating? Our support team will be happy to help you.
Gravity Flow 3.1 Changelog
- Added Send to Step options to bulk actions in the Workflow Status screen. Accessible only when filtered to a specific form.
- Added a new step type, Choice Routing, which routes the workflow to different next steps based on the value of a selected form field (dropdown or radio).
- Added support for the background notifications feature available with Gravity Forms 2.10.0 and later.
- Updated workflow fields and entry detail/edit page to be compatible with changes to GF_Field::get_value_entry_detail() and GFCommon::get_lead_field_display() in Gravity Forms 2.9.29.
- Updated workflow blocks to be compatible with the WordPress Block API v3.
- Updated the GravityView integration to make Flow workflow approval fields available in the GravityView field picker on the Single Entry configuration tab as well as the Multiple Entry tab. Credit: GravityKit team.
- Updated GravityView integration to address outdated filter warnings for displaying workflow detail link and workflow approval links.
- Fixed an issue where the Request Field Values setting remained visible in the Outbound Webhook step when passing the request body to the raw request.
- Fixed some display issues with buttons in the admin entry details page for WordPress 7.0-beta.
- Fixed an issue where field-level conditional logic was not respected when using the “selected_fields” display option.
- Fixed an issue where blocks for Gravity Flow extensions did not appear in the block editor when viewing post.php.
- Fixed an issue where count_users() could run on every page load.
- Fixed an issue where deleted workflow entries could still be viewed or updated via direct links.
- Fixed an issue where the approval step could not be completed when AJAX submission was enabled.
- Fixed an issue where editing a step in the Update User workflow without sufficient permissions displayed the same error message twice.
- Fixed PHP fatal error when conditional logic evaluates date field conditions.
- Fixed an issue where the Assign To and Date Picker components were not displayed when using Gravity Forms 3.0.0 and later.
- API: Fixed V2 REST API sending to step endpoint rejecting inputs without an active workflow step (e.g. canceled or completed).
- API: added a new parameter type Dynamic_choice_map (Multiple to Single). A generic settings field that maps multiple “option” choices to a single “target” choice per row, with configurable column labels. Used by the Choice Routing step for routing rules.
Newsletter
If you want to stay up to date with what’s happening on the blog, sign up for the Gravity Forms newsletter!
“*” indicates required fields
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.
