Remote Action for Integration Procedures (Managed Package)

For the managed package runtime, the Remote Action element calls the specified Apex class and method or the specified invocable action. You can also pass in invocation options and data. The Apex class must implement the VlocityOpenInterface2 or Callable interface.

This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

If the data that a remote action returns isn't in Map<String, Object> format, sometimes an Integration Procedure or Omnistudio Data Mapper can’t process it. Because the returned data isn’t an sObject, you can't use it to update Product2 objects without reserializing. You can convert the data in one of these ways:

• In the remote action, under Remote Options, add a Key named reserialize with a Value of true.

• In a subsequent Set Values step, use the RESERIALIZE function on the remote action's output.

  For information about related functions such as DESERIALIZE and SERIALIZE, see the Function Reference (Managed Package). For information on reserializing map objects as inputs, see Workflow for Remote Action Apex Class Example (Managed Package).

An error message that begins with Invalid conversion from runtime type String often indicates a need to reserialize data.

If you receive an error that says the Apex class can’t be loaded, add the Apex class namespace in the Remote Class field in the remote action like this: {yournamespace}.ApexClassName. For example, omnistudio.PrefillOrders where omnistudio is the namespace and PrefillOrders is the Apex class.

To ensure that a Remote Action error causes a rollback if Rollback on Error is checked in the Procedure Configuration, set the errorCode in the class output map.

Note Community Plus users must log in before they can use an Integration Procedure Remote Action that sends emails.

• Remote Action Properties for Integration Procedures (Managed Package)
  For the managed package runtime, these properties are unique to or function in a unique manner in Remote Actions. A Remote Action calls the specified Apex class and method or the specified Invocable Action. You can also pass in invocation options and data.
• Create a Remote Action for an Invocable Action (Managed Package)
  For the managed package runtime, an Integration Procedure uses a Remote Action to call the emailSimple Invocable Action, which is present in every Salesforce org. Inputs to the Invocable Action are specified in the Integration Procedure as Additional Input.
• Create a Remote Action for an Invocable Action with an Input Key (Managed Package)
  For the managed package runtime, an Integration Procedure uses a Remote Action to call the emailSimple Invocable Action, which is present in every Salesforce org. Inputs to the Invocable Action are specified in the Integration Procedure in a Remote Option named InvocableInputKey.
• Workflow for Remote Action Apex Class Example (Managed Package)
  For the managed package runtime, an Integration Procedure uses a Remote Action to call an Apex class and demonstrate how to reserialize data.