omnistudio-callable-apex-generate

Define your action names and input/output contract, then implement System.Callable with a thin call() method that dispatches via switch on action to private methods. Return a consistent envelope with success, data, and errors keys, and throw a typed exception for unsupported actions.

Preserve methodName values as action strings, pass inputMap and options as keys in the args map, and return a response envelope instead of mutating outputMap. Keep call() thin by delegating to the same internal methods, and update callers to read the return value instead of outputMap.

VlocityOpenInterface2 uses invokeMethod(methodName, inputMap, outputMap, options) and writes results into outputMap by reference, returning a Boolean. System.Callable uses call(action, args) and returns the result directly, making it the modern standard interface without a managed package namespace dependency.

System.Callable is a standard Salesforce interface and requires no namespace prefix. However, omnistudio.VlocityOpenInterface2 uses the managed omnistudio namespace and must always be qualified, and custom classes deployed into a namespaced package need the prefix applied.

The failure happens when code expects an inputMap key but the caller passes flat args. Guard defensively by checking whether args contains the inputMap key, and if absent, treat args itself as the input map with an empty options map.

Avoid callables for generic Apex classes or triggers without an Industries extension point, and for long-running work that belongs in asynchronous processing. Use dedicated skills for building Integration Procedures, OmniScripts, or DataRaptors instead of hand-coding those artifacts.