Workflow Outbound Messages
Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rules. Establish a plan to migrate to Flows, and create any new automation using Flow Builder.
Outbound Messages are NOT part of the Workflow Rule deprecation plan- you can and should continue to configure and use Outbound Messages when appropriate. Flows can reference and execute these Outbound Messages
- An Outbound Message Name MUST Start with
OM, followed by a number corresponding to the number of outbound messages on the triggering Object. -
An Outbound Message Name COULD contain the Object name, or an abbreviation thereof, in the Field Update Name. This is to avoid different conventions for Workflow Actions in general.
-
An Outbound Message MUST be named after the Service that it send information to, and then information it sends in the most concise manner possible.
-
The Description of An Outbound Message SHOULD give precise information on why the Outbound Message is created.
-
Listing the fields sent by the Outbound Message is NOT RECOMMENDED.
Examples
| Object | EA Name | Description |
|---|---|---|
| Invoice | OM01_Inv_SendBasicInfo | Send the invoice header to the client software. |
| Invoice | OM02_Inv_SendStatusPaid | Sends a flag that the invoice was paid to the client software. |
| Contact | OM01_SendContactInfo | Sends most contact information to the internal Directory. |
No Comments