Real-time Scenarios activated with the Use in Flow option enabled can be used in Flow. The features available for each Real-time Scenario depend on the backend system the Scenario is targeting. For example, a Scenario targeting an SAP table can only perform a query operation, whereas a RDMS table can perform CRUD operations.
Category: Overcast Real-time Scenarios
Name: apex-<scenario name>
Flow Interview GUID (required)
The unique identifier for the Flow. Specify {!$Flow.interviewGuid} .
Request Query (required/optional)
The query to send to the backend system. If Operation is available, Operation should be Query and this should be set.
Request Data (optional)
The data to send to the backend system. Used when Operation is Insert, Update or Delete.
Operation (required)
Specify the operation to perform with the text, Query, Insert, Update, or Delete.
Logger (optional)
A separate Monitoring record is created for each Real-time Scenario run. Specify the Apex-defined type, overcast.Logger, from a previous Real-time Scenario action to write the logs to the same Monitoring record.
Do not Commit Logs (optional)
Prevent the logs to be saved to the database. Use this to run subsequent Real-time Scenarios or make a web callout in the same transaction.
New Run ID
The ID for the new Run record.
Response Data
The response data from the backend system. The data type is the Scenario Apex class.
Logger
The Overcast Logger used for logging the Scenario. Can be used in the Write Logs Action for deferring the saving of the log records to a later time in the flow.