Configuring data field flows in Salesforce
Oneflow's Salesforce app offers a range of customization options for a tailor-made contracts approach to your organization. Salesforce uses "flows" to manage settings related to Oneflow and other APIs.
Accessing Salesforce Flows
To access Salesforce flows in your account:
- Go to Setup > Process automation > Flows
Data fields
Contracts in Oneflow can have data fields (i.e. contract variables) that can be linked to properties in Salesforce. The data field-related flows determine which data fields (properties) in Salesforce will be transferred to Oneflow upon contract creation. You may customize the data field mappings by editing the related flow.
Why modify existing flows?
Salesforce Flows represent a flowchart with different actions that are automated in a logical sequence. Modifying these flows can extend existing use cases to suit your organization’s needs or support additional use cases.
Mapping data fields from custom objects
If you want to map data fields from a custom object in Salesforce you will need to modify the existing flow.
| Attribute | Required? | Description |
|---|---|---|
| ObjectApiName | Yes | The Salesforce object (Opportunity, Account, Lead, or custom objects.) |
| RecordId | Yes | The record or instance of the object you are working on (an opportunity, an account, etc.) |
- In Salesforce, navigate to Setup > Process automation > Flows.
- Click on Oneflow Mapping: Data Fields.
- While hovering over the Decision object, select Edit Element.
Press the + button to add the object to the Decision branch. Alternatively, you can go directly to the object you are creating the contract from in Salesforce.
Add a label to describe the custom object (e.g. Lead, Project). The API name will be created based on the label name.
The objectAPIname of the custom object will match the name of the custom object in the value field (e.g. for the Opportunity object this would be “Opportunity”).
Resource: ObjectApiName
Operator: Equals
Value: [Object name] (e.g. Lead, Opportunity, Account).Add an action to get the records of the custom object. This will fetch all data about that custom object including its data fields. (You may also copy this action from an existing flow, paste it, and then edit the action to match the custom object).
Object: Select the object name (e.g. Lead).
Field: Id (this ID will match the RecordID).
Value: RecordId (this “record ID” refers to the specific instance of the object you are working on).(Optional) Add an action to fetch any other objects related to this custom object.
For instance, an Opportunity would have an Account associated with it. Likewise, a Contact will have an Account object associated with it, and the data fields of that account can be fetched by adding the object to the flow.
If you want to fetch data fields related to an account associated with a contact, then you can add the object to the flow.
Id field’s Value should include the primary object from the previous action followed by the object attribute you wish to retrieve.
Example: To get the Account associated with a Lead, click on the Value field > Lead from Get_Lead > Account__r > id.
Salesforce automatically converts this into an expression, e.g.{!Get_Lead.Account__r.Id}.Add an assignment action at the end of the flow. Ensure that the OutputRecordIDs are then added to the custom object’s ID (a variable created by the Oneflow app). This adds all fetched records into the output record ID variable.
Open the Oneflow app from the app launcher, go to the Oneflow Configuration tab, then select the Data Fields tab.
The data fields table on this page contains all fields fetched from the objects in your flow. Select which data fields you wish to make available in your Oneflow contracts.
You may also configure Two-way sync options for each data field:
- To OF: Transfers changes made to the data field in Salesforce to Oneflow.
- To SF: Transfers changes made to the data field in Oneflow to Salesforce.
NOTE If date fields are not updating correctly between Salesforce and Oneflow, it may be due to a mismatch in the date formats configured in the two systems. To ensure accurate synchronization, both Salesforce and Oneflow should use the same date format. While different separators (e.g., DD/MM/YYYY vs. DD-MM-YYYY) are typically supported, a difference in the format order (e.g., DD/MM/YYYY vs. MM/DD/YYYY) can cause incorrect data synchronization. |