DEST-1616 Update docs to reflect current Salesforce Actions #498
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mericsson
changed the title
mericsson
commented
Jan 7, 2020
|
|
||
| ## Custom Actions | ||
| If you need to manually configure how your Segment events interact with SFDC resources, you can do so using the [Actions](#actions) setting. This setting allows you to trigger standard CRUD operation (Create, Read, Update/Upsert, Delete) on your internal SFDC resources in response to your Segment events. You can configure as many of these actions as you would like. Each action must be associated with either a specific `track` event or **all** `identify` events. Actions can be further configured to map event properties to SFDC fields. Here's an example action configuration that will create a new Case in Salesforce in response to an **Issue Submitted** `track` event: | ||
| If you need to manually configure how your Segment events interact with Salesforce resources, you can do so using the [Actions](#actions) setting. This setting allows you to trigger standard CRUD operation (Create, Read, Update/Upsert, Delete) on your internal SFDC resources in response to your Segment events. You can configure as many of these actions as you would like. Each action must be associated with either a specific `track` event or **all** `identify` events. Actions can be further configured to map event properties to SFDC fields. Here's an example action configuration that will create a new Case in Salesforce in response to an **Issue Submitted** `track` event: |
Contributor
Author
There was a problem hiding this comment.
replaced SFDC with Salesforce to be consistent with rest of file.
mericsson
commented
Jan 7, 2020
|
|
||
| ### Upsert Actions | ||
| Upsert actions will either create or update a resource in SFDC. In order for these to work, you must provide an External Id Field in in your action configuration that we can use to determine if the resource exists or not. You must also map an event property to this field as a Field Mapping. Here's an example: | ||
| Upsert actions will either create or update a resource in Salesforce. In order for these to work, you must provide Upsert Rules in in your action configuration that we can use to determine if there is an existing object to update. If an object is not found, a new object in SFDC is created. For a successful upsert Action, you must also map an event property to this field as a Field Mapping. Here's an example: |
Contributor
Author
There was a problem hiding this comment.
Updated to match current functionality.
ccnixon
approved these changes
Jan 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update docs to reflect current Salesforce Action functionality and UI. We changed it in September and forgot to update docs. :(
Related issues (optional)