BWC is still under active development. We welcome community feedback, and encourage contributions. Here’s what we see as our top priorities:

Multi-node deployments: Provide platform support for content deployment to multiple worker nodes, with better integration with git/GitHub. Simplify development and deployment of “automation as code” at scale.

Multi target configurations for integration packs: For a given integration pack, define and manage multiple targets. This should allow the user to choose which one of a set of configurations to use for a given action.

History and Audit service: History view with advanced search over years worth of execution records, over multiple versions of continuously upgraded BWC.

Projects and Uber-flow: Introduce projects to group and manage rules and workflows. Handle versions and dependencies. “Productize” flow-rule-flow-rule chain pattern, aka “uber-flow”. Manage large number of automations across users and teams, on a single BWC deployment at enterprise scale.

Action Output Structure Definition: Enable optional definition of action payload, so that it can be inspected and used when passing data between actions in workflows.

RBACv2:

Filters: Tag and property based filters, more refined and convenient access control.

Permissions: Permissions on key value objects, arbitrary triggers, support for a default role to be assigned to new users.

WebUI: UI for RBAC configuration.

ChatOps: Allow users to authenticate with BWC via bot on chat. Check permissions of the user who triggered an action / ran a command. Introduce a special set of permission types for ChatOps.

More integration packs: push more content to the community to help work with most common and widely used tools. Tell us if there is a tool you love and think we should integrate with, or better yet write a pack!

Is there some other feature you’re desperately missing? Submit an issue!