Events

Sequence of Redux actions:

Once you have defined an operation with an action type in the config file, every time you dispatch this action, here is the sequence of actions dispatched to the store.

1. Action type defined in config file's operation property and dispatched

2. Action type_BEGIN dispatched.

3. QueueManager/ADD_TO_QUEUE/Action type dispatched with all options about the call

4. Action type_SUCCESS or FAILURE dispatched upon call resolution

5. QueueManager/REMOVE_FROM_QUEUE/Action type

The Action type you dispatch from the app will have the payload you pass to it.

Action type_BEGIN, Action type_SUCCESS, and Action type_FAILURE methods defined in the config file have access to the original payload passed, the store, the settings of the call, as well as the request answer payload or error message.

Browser Events Redux-optimum listens to:

Redux-optimum listens to the online and offline events from the browsers if implemented and queues the calls depending on this status.

Actions Redux-optimum listens to:

LoggedIn/LoggedOut

method called when retrieving a fresh token

ACTIONS TO INTERACT WITH THE QUEUE MANAGER

Action to retrigger the queue

Action to clear the queue