When you create a Oneflow contract from Salesforce using the Oneflow widget, you can choose among available potential participants of the contract. The Oneflow Participants flow defines the participant list from the flow shipped with Oneflow for Salesforce.
You can find this flow at Setup > Flow > Oneflow Participants.
The default flow is based on the Opportunity, Account, and Contact objects, i.e., it supports logic for participant mapping for Opportunity, Account, and Contact. The flow queries the contract roles of the provided record ID. These records are then converted into the OFapp__PotentialParticipant datatype.
The result of the flow is a collection of OFapp__PotentialParticipant items. The OFapp__PotentialParticipant data type has these attributes:
| Attribute | Required | Description | Example Value |
|---|---|---|---|
| Identifier | Yes | The participant identifier. Needs to be unique for all participants (often a record ID). | 0032o00000k3l4bAAA |
| FirstName | No | The first name of the participant. | Jane |
| LastName | Yes | The last name of the participant. | Doe |
| No | The participant’s email. May be required depending on template settings. | jane.doe@example.com | |
| Phone | No | The participant’s phone number. May be required depending on template settings. | +46701234567 |
| Date of Birth | No | The participant’s date of birth. | 1990-01-01 |
| Country | No | The country of residence of the participant (ISO Code). | SE (for Sweden) |
| Role | No | The Salesforce role of the participant. | Decision Maker |
| Oneflow Role | No | The Oneflow role of the participant. Defaults to Signatory. | signatory |
| PartyIdentifier | No | The identifier of the party (e.g., organisation no.). Used to group participants into the same company. | 556000-1234 |
| PartyName | No | The name of the party this participant belongs to. | Acme Corp |
NOTE A participant is always added as an individual if no party identifier is provided. If specified, they are added as a member of their company by default. The selection screen still allows adding the user as an individual. |
Customize data mapping for Party data from Salesforce to Oneflow
When creating a contract from Opportunity, Account, or Contact, Oneflow provides default mapping for:
- PartyName (Account Name)
- PartyIdentifier (Organization number)
- FirstName, LastName
- Phone
- Date of Birth
- Identifier
You can adjust default mappings or add fields such as participant title or company country.
Set organization number and country data for counterparties
To set a country for a counterparty, modify the Oneflow Participants flow. In this example, we will use the Opportunity path. Update the flow logic to map Salesforce attributes (e.g., Account.Country) into participant attributes.
You can also assign account-related info in the Assignment element that maps Account fields to participant variables. Map the Salesforce contact attribute to the participant’s country.
Example Configuration: To map the Billing Country from the Account associated with an Opportunity, configure the assignment variable as follows:
|
Similarly, configure partyidentifier to pull the organisation number from Salesforce.
NOTE If an Opportunity uses both Opportunity Contact Roles and an Account, apply the same mapping changes in the Assignment element for both paths. |
NOTE Oneflow expects country data in ISO format (e.g., SE, not “Sweden”). Non-ISO values cause an error during contract creation. Valid vs. Invalid Examples:
|
Map participant title with Salesforce data
You can also map participant titles. Modify the Assignment element within the Opportunity Contact Roles loop to add a Salesforce field like Title.
Example Configuration: To map the job title from a Contact record to the Oneflow participant:
|
NOTE If the Opportunity pulls participants both from contact roles and the associated Account, update both flows to include the title mapping. |