Hi TRish sharma,

https://medium.com/@joshuasalema/event-driven-architecture-in-outsystems-using-celigo-integrations-platform-27a731105777

The above links provide a detailed information hope it helps.

Thanks,
Vignesh Prakash.

Hello,

Please refer to the links.

https://www.outsystems.com/evaluation-guide/does-outsystems-support-event-driven-architecture/

https://www.outsystems.com/forge/component-overview/4665/event-based-architecture-o11

Hope that helps.

Regards,

Anees

Hi,

Event driven is found in many in OS, especially when u jump to BPT (Business Process Technology). There are many callbacks that are called when some event raised. like OnReady, OnOPen, OnClose, etc.

regards

Hi TRish sharma,

Event-driven architecture in OutSystems is a designed pattern that focuses on responding to actions (events) to trigger subsequent processes. 

For instance, if you have any web block within a web screen (or web block), and the user modifies any value on this web block, you should call an event to notify and handle this change in the parent screen. 

You will be able to create an action on this screen to handle it, update the relevant variables and  trigger any subsequent processes needed there.

Please, read this article, it will give a better idea of how to deal with events in Outsystems:

https://success.outsystems.com/documentation/11/reference/outsystems_language/interfaces/navigating_in_the_application/event/

https://success.outsystems.com/documentation/11/developing_an_application/design_ui/reuse_ui/use_events_to_propagate_changes_from_a_block_to_the_parent/

Regards,

Tami

Hi Trish Sharma,

Event is a generic term and mainly used in all the technologies, framework and in basic it the part of design pattern. If we generally talk at UI Level - There may be Click Event on button click, Item Change Event of selection and there are number of examples. 

Above mentioned events are part of UI Framework and Similarly, Outsystem provides and handles the framework logic with the usage of CREATE, READY, RRENDER, DESTROY events at the block or screen level in order the initialize, render and destroying the UI. 

Similarly there are data fetches  events (ON AFTER FETCH) when Aggregate or Data Action fetch the data. Also, there is a mechanism to monitor the database events, so that Outsystem can trigger the asynchronous process. 

Events are just raised and notified to its subscriber if some actions should be taken. If we have provided some callback to handle the events, it would be handled and action should be taken in the handler logic.

Regards,

Vikas