Work with multiple enterprise systems from a single controlled input.
FlowBridge lets one controlled input file contain work for multiple licensed DDF connectors, so a single workflow can coordinate operations across systems such as Planview, ServiceNow and Jira.
Multiple connectors can run independently without FlowBridge. Add FlowBridge when one approved workflow needs to work with more than one licensed system, including where those system-specific operations are supplied together in a single input file.
One input. Multiple licensed systems. Controlled connector execution.
FlowBridge coordinates work across connector boundaries inside the customer environment. A single input can describe operations for more than one licensed system, while each connector remains responsible for the supported operations against its own target system.
- ✓ Supports a single controlled input containing operations for multiple licensed DDF connectors
- ✓ Uses DDF Plus capabilities such as QueryLocal, CalcLocal and SmartSync where the workflow requires them
- ✓ Keeps connector-specific operations within their supported scope
- ✓ Retains run evidence across the coordinated workflow
- ✓ Executes locally inside the customer environment
One workflow can span multiple systems without splitting the input by platform.
A customer can license FoliosFlow and ServiceFlow, or any other supported connector combination, and run them independently. FlowBridge becomes relevant when one business workflow needs to address more than one licensed system, including where those operations are defined together in a single input file.
Licensed connectors
Each connector performs supported operations against its own platform.
- FoliosFlow for Planview
- ServiceFlow for ServiceNow
- JiraFlow for Jira
- Other licensed connectors as they become available
DDF Plus
Adds shared local data intelligence and preparation capabilities across licensed connectors.
- QueryLocal
- CalcLocal
- SmartSync
- Enhanced reconciliation and delta processing
FlowBridge
Coordinates one approved workflow across two or more licensed systems.
- Accepts one controlled input spanning multiple licensed systems
- Coordinates the relevant connector stages
- Coordinates supported workflow outputs between defined stages where required
- Preserves connector boundaries
- Retains cross-workflow run evidence
Cross-system work often fails at the handoffs.
The difficult part is often not reading from one system or updating another. It is avoiding separate files, scripts and handoffs for each platform while still preserving clear control over which connector performs which operation.
Manual handoffs
Teams often split one business process into separate files or scripts for each platform, then manage the handoffs manually.
Hidden dependencies
One step can depend on the outcome of another without a clear control point between them.
Different identifiers and structures
The same business object may be represented differently across systems and need local preparation or mapping.
Fragmented evidence
Separate scripts and manual steps make it harder to reconstruct the end-to-end run later.
One approved workflow, coordinated across systems
FlowBridge coordinates the sequence. Connector-specific reads, creates, updates or other supported operations remain the responsibility of the relevant licensed connector.
1. Provide one controlled input
The workflow input can contain agreed operations for more than one licensed system rather than requiring a separate file for each platform.
2. Prepare and interpret the workflow locally
DDF Plus capabilities can prepare, calculate, compare or reconcile the data where required, while the workflow keeps the system-specific operations distinct.
3. Coordinate the relevant connectors
FlowBridge coordinates the connector-specific stages so each licensed connector handles the operations intended for its own target system.
4. Retain run evidence
Inputs, outputs, failures and stage evidence are retained by the surrounding workflow, with reconciliation where required.
Example: one input file, more than one system
A FlowBridge workflow can take one controlled input that includes operations for multiple licensed systems. The workflow keeps those operations together as one business process while the relevant connectors perform the supported system-specific work.
The value is not simply that DDF supports more than one system. It is that one controlled workflow can carry multi-system intent in one input while preserving the execution boundaries of each licensed connector.
FlowBridge requires DDF Plus
FlowBridge is licensed for customers that already have DDF Plus and at least two licensed connectors. Plus provides the shared local data capability that supports cross-system preparation, comparison and reconciliation.
QueryLocal
Prepare, join and filter local workflow datasets before the next connector stage.
CalcLocal
Apply configured business calculations where the workflow requires derived values.
SmartSync
Identify the meaningful delta where configured comparison rules are part of the workflow.
Reconciliation
Compare intended and actual state where the workflow requires controlled verification.
FlowBridge coordinates. Connectors execute.
The distinction matters. FlowBridge is not a universal API layer and does not make unsupported operations available.
FlowBridge does
- Accept one controlled input spanning multiple licensed systems
- Coordinate the order of supported connector steps
- Coordinate supported workflow outputs between defined stages where required
- Use Plus capabilities where required
- Support end-to-end workflow evidence
- Keep the workflow inside the customer environment
FlowBridge does not
- Replace FoliosFlow, ServiceFlow, JiraFlow or another licensed connector
- Turn unsupported connector operations into supported ones
- Act as a general-purpose cloud integration platform
- Guarantee atomic cross-system transactions, automatic rollback or identical behaviour across external systems
- Require every multi-connector customer to license FlowBridge
- Route workflow processing through a DDF-hosted execution service
Each connector remains subject to its target system’s API responses, permissions and configuration. Where verification is required, the agreed workflow retains stage evidence and can use defined readback, comparison and reconciliation controls.
Built around licensed DDF connectors
FlowBridge is used only with connector combinations and operations that are within the agreed supported scope.
FoliosFlow
Supported Planview Portfolios operations, with dedicated Planview Logbook capability where licensed.
ServiceFlow
Supported ServiceNow data operations within the agreed workflow scope.
JiraFlow
Jira, within the documented supported scope
SalesFlow
Salesforce Opportunity-focused connector in validation.
Add FlowBridge only when the workflow crosses systems
FlowBridge is separately licensed because it adds coordinated cross-system workflow control, including the ability to work with multiple licensed systems from one controlled input. It is not required simply because a customer owns more than one DDF connector.
FlowBridge requires DDF Plus and at least two licensed connectors. It is added only where one approved workflow needs coordinated steps across those systems.
Which workflow currently breaks at the system boundary?
Show us the handoff between two enterprise systems. We can assess whether the existing connectors, DDF Plus and FlowBridge can turn it into one controlled, repeatable workflow.