Event based validation

1. A non-transitory computer readable medium comprising computer readable program code for performing event based validation, the performing comprising:

obtaining, for a first user interface (UI) event, a first UI event definition comprising a first parameter definition and a second parameter definition;

obtaining, for the first UI event definition, a first trigger event definition and a second trigger event definition, wherein the first trigger event definition associates a first event subscriber to the first UI event with a first validation condition and a first parameter value for the first parameter definition, wherein the second trigger event definition associates a second event subscriber to the first UI event with a second validation condition and a second parameter value for the second parameter definition;

associating a first page of a web application with the first UI event definition by adding the first UI event to the first page;

detecting, through a first action performed by the end user, the first UI event in the first page of the web application;

transmitting the first UI event to an event bus;

identifying, by the event bus and based on a first type of the first UI event, the first event subscriber and the second event subscriber, wherein the first type of the first UI event specifies the first action and a first item affected by the first action;

making a first determination, based on testing the first validation condition and data in a context cache, that the first validation condition is satisfied, wherein the data in the context cache comprises data that the end user of the web application input on a second page of the web application;

performing, based on the first determination, a second action in the first page of the web application by applying the first parameter value to the first parameter definition; and

making a second determination, based on testing the second validation condition, that the second validation condition is not satisfied.

2. The non-transitory computer readable medium of claim 1 , wherein the first UI event is in a first portion of the first page and wherein the first validation condition of the first event subscriber is a test on data from an external source.

3. The non-transitory computer readable medium of claim 1 , wherein the second action comprises displaying a message specified by the first event subscriber in the first page.

4. The non-transitory computer readable medium of claim 1 , wherein the performance of the second action comprises performing a second UI event, and wherein the event based validation further comprises:

obtaining, for the second UI event, a second UI event definition comprising a third parameter definition;

obtaining, for the second UI event definition, a third trigger event definition that associates a third event subscriber to the second UI event with a third validation condition and a third parameter value for the third parameter definition;

associating the first page of the web application with the second UI event by adding the second UI event to the first page;

detecting, through a third action performed by the end user, the second UI event in the first page of the web application;

transmitting the second UI event to the event bus;

identifying, by the event bus and based on a second type of the second UI event, the third event subscriber to the second UI event, wherein the second type of the second UI event specifies the third action and a second item affected by the third action;

making a third determination, based on testing the third validation condition, that the third validation condition is satisfied; and

performing, based on the third determination, a fourth action in the first page of the web application by applying the third parameter value to the third parameter definition.

5. The non-transitory computer readable medium of claim 1 , wherein the first determination and the second determination are performed in parallel.

6. A system performing event-based validation, comprising:

a computer processor;

a builder that, when executed on the computer:

obtains, for a first UI event, a first UI event definition comprising a first parameter definition and a second parameter definition;

obtains, for the first UI event definition, a first trigger event definition and a second trigger event definition, wherein the first trigger event definition associates a first event subscriber to the first UI event with a first validation condition and a first parameter value for the first parameter definition, wherein the second trigger event definition associates a second event subscriber to the first UI event with a second validation condition and a second parameter value for the second parameter definition;

associates a first page of a web application with the first UI event definition by adding the first UI event to the first page;

an UI event manager that, when executed on the computer processor:

detects, through a first action performed by the end user, the first UI event in the first page of the web application, and

transmits the first UI event to an event bus,

the event bus operatively connected to the UI event manager and configured to:

receive the first UI event;

identify, based on a first type of the first UI event, the first event subscriber and the second event subscriber, wherein the first type of the first UI event specifies the first action and a first item affected by the first action;

make a first determination, based on testing the first validation condition and data in a context cache, that the first validation condition is satisfied, wherein the data in the context cache comprises data that the end user of the web application input on a second page of the web application;

perform, based on the first determination, a second action in the first page of the web application by applying the first parameter value to the first parameter definition; and

make a second determination, based on testing the second validation condition, that the second validation condition is not satisfied.

7. The system of claim 6 , wherein the first UI event is in a first portion of the first page and wherein the first validation condition is a test on-data from an external source.

8. The system of claim 6 , wherein the second action comprises displaying a message specified by the first event subscriber in the first page.

9. The system of claim 6 , wherein the performance of the second action comprises performing a second UI event, wherein the builder, when executed on the computer processor, further:

obtains, for the second UI event, a second UI event definition comprising a third parameter definition;

obtains, for the second UI event definition, a third trigger event definition that associates a third event subscriber to the second UI event with a third validation condition and a third parameter value for the third parameter definition;

associates the first page of the web application with the second UI event by adding the second UI event to the first page,

wherein the UI event manager, when executed on the computer processor, further:

detects, through a third action performed by the end user, the second UI event in the first page of the web application; and

transmits the second UI event to the event bus,

wherein the event bus is further configured to:

receive the second UI event;

identify, based on a second type of the second UI event, a third event subscriber to the second UI event, wherein the second type of the second UI event specifies the third action and a second item affected by the third action;

make a third determination, based on testing the third validation condition, that the third validation condition is satisfied; and

perform, based on the third determination, a fourth action in the first page of the web application by applying the third parameter value to the third parameter definition.

10. The system of claim 6 , wherein the first determination and the second determination are performed in parallel.