Event-driven application systems and methods
View Patent ↗An event-driven application system and method includes an activity-function engine in communication with an event-driven application. The activity-function engine includes an event matching list having a plurality of input-event to activity-function mappings. The event-driven application includes at least one programmable object having at least one activity-function. The activity-function engine is configured to receive an input-event from the application, to match the input-event to the at least one activity-function based on the plurality of input-event to activity-function mappings, and to execute the at least one activity-function.
1. A computerized system comprising:
an activity-function engine including an event matching list having a plurality of input-event to activity-function mappings, the activity-function engine configured to execute on at least one processor; and
an application configured to be stored in memory and executed by the at least one processor, the application including at least one programmable object having at least one activity function;
wherein the activity-function engine is configured to receive an input-event from the application, to match the input-event to the at least one activity-function based on the plurality of input-event to activity-function mappings, and to execute the at least one activity-function.
2. The computerized system according to claim 1 , wherein the activity-function engine is configured to execute multiple activity-functions matching the input-event in a defined execution order.
3. The computerized system according to claim 1 , wherein the at least one activity-function is configured to return a feedback code.
4. The computerized system according to claim 3 , wherein the feedback code is a SUCCESS code when the at least one activity-function successfully executes, a PARTIAL-SUCCESS code when the at least one activity-function successfully executes and at least one additional activity-function does not execute due to unavailability of a programmable object of the at least one programmable object having the at least one additional activity function, a NO-MATCH code when the at least one input event does not match any activity functions, a FAIL code when the at least one activity-function encounters an error, a BREAK code when subsequent activity-functions matching the input-event are not to be executed, or a RERUN code when the activity-function engine is to process the input-event an additional time.
5. The computerized system according to claim 1 , wherein the input-event includes a unique event identifier.
6. The computerized system according to claim 5 , wherein the unique event identifier comprises:
an event type identifier defining a category of input-event;
an object identifier defining a specific programmable object of the at least one programmable object; and
an event identifier defining a specific input-event.
7. The computerized system according to claim 6 , wherein the unique event identifier is in packed form.
8. A computerized method comprising the steps of:
receiving, at an activity-function engine, an input-event from an application;
matching, at the activity-function engine, the input-event to at least one activity-function of at least one programmable object of the application based on an event matching list comprising a plurality of input-event to activity-function mappings; and
executing the at least one activity-function.
9. The computerized method according to claim 8 , wherein the step of executing the at least one activity-function includes executing the at least one activity-function in a defined execution order.
10. The computerized method according to claim 8 , additionally comprising the step of:
returning a feedback code by the at least one activity-function.
11. The computerized method according to claim 10 , wherein the feedback code is a SUCCESS code when the at least one activity-function successfully executes, a PARTIAL-SUCCESS code when the at least one activity-function successfully executes and at least one additional activity-function does not execute due to unavailability of a programmable object of the at least one programmable object having the at least one additional activity function, a NO-MATCH code when the at least one input event does not match any activity functions, a FAIL code when the at least one activity-function encounters an error, a BREAK code when subsequent activity-functions matching the input-event are not to be executed, or a RERUN code when the activity-function engine is to process the input-event an additional time.
12. The computerized method of claim 8 , wherein matching, at the activity-function engine, the input-event to at least one activity-function of at least one programmable object of the application is based on a unique event identifier of the input-event.
13. The computerized method according to claim 12 , wherein the unique event identifier comprises:
an event type identifier defining a category of input-event;
an object identifier defining a specific programmable object of the at least one programmable object; and
an event identifier defining the input-event.
14. The computerized method according to claim 13 , wherein the unique event identifier is in packed form.
15. A non-transitory, tangible computer-readable medium storing instructions adapted to be executed by a computer processor to perform a method comprising the steps of:
receiving, at an activity-function engine, an input-event from an application;
matching, at the activity-function engine, the input-event to at least one activity-function of at least one programmable object of the application based on an event matching list comprising a plurality of input-event to activity-function mappings; and
executing the at least one activity-function.
16. The non-transitory, tangible computer-readable medium of claim 15 , wherein the step of executing the at least one activity-function includes executing the at least one activity-function in a defined execution order.
17. The non-transitory, tangible computer-readable medium of claim 15 , additionally comprising the step of:
returning a feedback code by the at least one activity-function.
18. The non-transitory, tangible computer-readable medium of claim 17 , wherein the feedback code is a SUCCESS code when the activity-function successfully executes, a PARTIAL-SUCCESS code when the at least one activity-function successfully executes and at least one additional activity-function does not execute due to unavailability of a programmable object of the at least one programmable object having the at least one additional activity function, a NO-MATCH code when the at least one input event does not match any activity functions a FAIL code when the activity-function encounters an error, a BREAK code when subsequent activity-functions matching the input-event are not to be executed, or a RERUN code when the activity-function engine is to process the input-event an additional time.
19. The non-transitory, tangible computer-readable medium of claim 15 , wherein matching, at the activity-function engine, the input-event to at least one activity-function of at least one programmable object of the application is based on a unique event identifier of the input-event.
20. The non-transitory, tangible computer-readable medium of claim 19 , wherein the unique event identifier comprises:
an event type identifier defining a category of input-event;
an object identifier defining a specific programmable object of the at least one programmable object; and
an event identifier defining the input-event.