Triggers

Completed actions also cache write data. In situations where data is maintained bidirectionally, it is important to set the Event Origin to indicate where the data was changed. Select the name of the connector to indicate changes made directly to the data from the external system. Select Ryvit to indicate changes made to the data via an internal action from the App Xchange platform. This will prevent loops where you update one system and then immediately update the other system.

Filter

Add a filter to a cache-event trigger in the Filter section to further define the specific conditions under which the flow will trigger. This ensures that the flow runs only when relevant criteria are satisfied, reducing the number of costly flow runs. 

Please note that values entered will be compared as text strings. Filters cannot contain code, such as a reference to a flow config. 

See how to add a filter when you add a trigger.

Action Close Out Trigger

Action Close Out triggers a flow on the success or failure of an action.

It is common to want to send a close out to the source system on the success of an action or remediate the data so an action can be retried on failure.

On Demand Trigger

On Demand triggers can be scheduled to run at an interval of your choosing, or they may be defined as called flows and run from inside another flow.  They may have a custom input of data.

On Demand triggers and called flows can simplify flow writing and make flows more reusable.

For example, imagine an integration that sends many different types of data between two systems, and one of the systems requires each of these data types to respond with a message on success or failure.

In this scenario, writing one called flow would allow you to call that flow in each of the other data syncs. This would reduce the number of steps in each flow and allow you to manage any issues with that close out logic in one place.

Work Request Batch Ready Trigger

The Work Request Batch Ready trigger fires when a batch of work requests reaches a state where they are ready to be processed. This trigger is commonly used when writing flows that combine work request cache events into a single batch.

You can customize this trigger in several ways. You can define a certain type of work request to trigger the batch, the target status for these work requests, and set a batch size limit. You can also configure the timeout length after which the flow will automatically run.

This trigger outputs an array of work requests. See below for an example of a typical JavaScript output array.