Controlled Salesforce data operations and cross-system workflows.
Prepare, compare, execute and verify supported Salesforce operations - locally, in your own environment. Combine SalesFlow with DDF's other licensed connectors to turn data differences into controlled business actions.
SalesFlow uses DDF's reusable execution architecture for authenticated Salesforce record operations, structured data preparation and multi-system integration. Development testing has demonstrated Salesforce Account operations, Opportunity creation and updates, multi-record processing and Salesforce-to-Planview synchronisation.
Business-readable input. Controlled execution. Verifiable outcomes.
In a controlled test, SalesFlow, QueryLocal and FoliosFlow handled CREATE, UPDATE and SKIP decisions across three Salesforce Opportunities in one executable workflow. On repeat execution, no Planview writes were required.
Current status: Technically validated for the workflows described here in Salesforce developer and Planview sandbox environments. SalesFlow remains in controlled evaluation, not a generally available production deployment. Broader object compatibility and operational readiness require additional validation.
- OAuth-authenticated Salesforce API operations from a locally executed DDF runtime
- Account Create, Read, Update and Delete demonstrated in development
- Opportunity Create, Read and Update demonstrated, including links to Accounts
- Multiple Salesforce records retrieved during a single Flow execution
- QueryLocal joins, comparisons and conditional cross-system action selection
- Verified Salesforce-to-Planview Opportunity Hopper CREATE / UPDATE / SKIP workflow
Getting data into Salesforce is only part of the challenge.
Enterprise workflows depend on reliable business references, accurate relationships and confidence that Salesforce and downstream systems remain aligned as records change.
Business versus technical references
Source systems use business identifiers, while Salesforce and target applications may require their own record IDs.
Unmatched records
Missing or invalid references should be visible for review rather than passed silently into a write operation.
Systems drifting apart
Opportunities, projects and other business records change independently unless integration workflows detect and handle the differences.
Unnecessary or risky changes
Repeated scripts can write data that is already correct. Teams need repeatable decisions and evidence of what actually changed.
Prepare, validate, execute and verify
SalesFlow builds on the same structured DDF approach used across the supported connector family.
1. Prepare
Read Salesforce data and other approved sources. Use QueryLocal, where licensed, to join, transform and structure records.
2. Validate
Compare Salesforce and target-system data, identify unmatched records and determine whether a change is needed.
3. Execute
Run supported Salesforce and target-system API operations through customer-controlled executables and approved endpoints.
4. Verify
Capture execution results, read records back and rerun comparison logic to check the resulting business state.
Demonstrated example: a Salesforce-to-Planview Opportunity Hopper test read three Opportunities, compared them against Planview projects, created one project, updated another and skipped an unchanged record. A second run found all three aligned and performed zero Planview writes.
What's been demonstrated so far
These results come from controlled development and sandbox tests. They do not imply universal Salesforce object, field or production support.
Account record operations
Create, Read, Update and Delete tests against standard Accounts, including selected custom fields.
Opportunity operations
Created Opportunities with required fields and Account links; retrieved and updated Opportunity records through Salesforce REST APIs.
External ID addressing
Retrieved Accounts using a configured custom External ID field and used QueryLocal to resolve business references to Account IDs.
Multi-record processing
Read three Opportunities within one Flow run, using separate REST requests and shared in-memory data for comparison.
Cross-system decisions
Joined Salesforce and Planview results to generate CREATE, UPDATE and SKIP decisions using QueryLocal.
Repeat-run verification
Created and updated Planview projects with FoliosFlow, then confirmed a subsequent batch required no further writes.
One reusable architecture, many supported workflows
SalesFlow shares DDF's structured execution model with FoliosFlow, ServiceFlow and JiraFlow. In the demonstrated Opportunity Hopper workflow, QueryLocal supplied the data preparation and decision logic while the existing connectors executed the appropriate API operations - without developing a dedicated Salesforce-to-Planview synchronisation engine.
Consistent structured inputs
Configure supported data operations using familiar DDF Flow service patterns instead of maintaining a separate application-specific integration codebase.
Reusable data logic
QueryLocal can join records across connectors, compare values and produce rows for the specific supported operations that need to run.
Controlled reuse
Customer-specific executables can be copied for multiple authorised use cases within their configured endpoint and licence scope. No separate per-flow configuration engine is required.
Combine SalesFlow with DDF Plus
Local preparation and change-detection capabilities help turn retrieved business data into reviewable, controlled actions. Availability depends on the licensed connector combination and supported operations.
QueryLocal
Demonstrated with SalesFlow for Account reference resolution and, with FoliosFlow, for multi-record Salesforce-to-Planview CREATE / UPDATE / SKIP logic.
SmartSync
DDF Plus supports structured snapshot comparison and candidate delta identification. A Salesforce-specific end-to-end SmartSync workflow is not yet claimed.
Reconciliation
Selected Salesforce readback and repeat-run cross-system comparison have been demonstrated. Full production reconciliation and recovery patterns remain to be established.
Simulation
The DDF engine supports simulation for specified mutating methods. Exact SalesFlow method coverage and behaviour still require connector-specific verification.
Locally executed software. Your infrastructure. Your control.
SalesFlow operates through customer-deployed DDF executables, making authenticated requests directly to approved Salesforce endpoints. No DDF-hosted cloud runtime is required for the demonstrated workflow.
Customer-controlled execution
Run configured workflows within your approved environment. Each executable is built for its authorised scope, including allowed endpoints and licence expiry controls.
Salesforce authentication
OAuth Client Credentials authentication has been demonstrated using a configured Salesforce External Client App. Access remains subject to Salesforce permissions and deployment configuration.
Execution evidence
Capture API outcomes and reviewable data outputs, then verify business state through readback and comparison where the workflow requires it.
Reuse without a per-flow runtime: authorised customers can deploy separate copies and configurations of their licensed DDF executable across multiple supported workflows, subject to agreed endpoint, licence and support scope.
Technical validation - what's next?
Opportunity Create, Read and Update and the demonstrated Salesforce-to-Planview workflow have passed controlled tests. The following remain engineering and validation priorities, not generally available features.
Complete Opportunity CRUD coverage
Validate Opportunity Delete, negative cases and post-operation verification; extend coverage of object and field types.
Batch API efficiency
Investigate Salesforce REST Collections, mixed-success handling and higher-volume execution. Current multi-record tests used separate REST requests.
Upsert and recovery
Validate Salesforce Upsert by External ID and strengthen cross-system recovery when one step succeeds but a subsequent mapping step fails.
Production hardening
Expand field-level synchronisation, automate source selection and validate error handling, permissions, audit and customer deployment processes.
Scope note: Salesforce SOAP/WSDL web services are outside the current SalesFlow connector scope. Salesforce Bulk API 2.0 is an assessment item, not a demonstrated capability. Production-grade cross-system recovery, broader mappings and end-to-end operational controls are still to be validated.
FlowBridge connects Salesforce and Planview
SalesFlow + FoliosFlow + FlowBridge
FlowBridge brings supported DDF connectors together in a coordinated, locally executed workflow. In our Opportunity Hopper validation, SalesFlow retrieved Salesforce Opportunities, FoliosFlow read and changed Planview projects, and DDF Plus / QueryLocal compared records and determined which actions were needed. All operations ran through the shared DDF execution architecture.
CREATE
When an Opportunity has no matching mapped project, create a Planview project beneath the Opportunity Hopper and store its Salesforce identifier.
UPDATE
When a mapped project exists but its name differs, update the same Planview project without creating a replacement.
SKIP
When the compared values already match, generate no write payload and leave the existing project unchanged.
Validated Opportunity Hopper test: one configured FlowBridge workflow processed three Salesforce Opportunities in a single execution. It created one Planview project and set its identifying attribute, updated a second project, and left a third unchanged. A repeat execution returned three SKIP decisions and performed zero Planview writes.
This controlled developer and sandbox test used deterministic Planview external keys and a temporary attribute mapping. It demonstrates coordinated use of the existing DDF engines, not a separate specialised orchestration runtime. Production deployment requires approved record mappings, partial-failure recovery and operational controls. The comparison tested project names; additional field synchronisation remains under validation.
What Salesforce workflow would you like to make more controlled and repeatable?
Tell us about your Salesforce records, downstream systems and required business outcomes. We can discuss a focused demonstration or Proof of Value for an agreed, technically supported scope.
SalesFlow is in controlled technical validation. Availability, supported operations and production deployment scope are subject to confirmation.