Throttling Events in Entity Lifecycle Management
First Claim
1. A method of simplifying, for a non-programming user, creation of an entity management workflow, the method including:
- representing a plurality of case-status states in a workflow state machine that handles machine-generated events that are generated by machines without reliance on human-machine interaction;
for at least a first case-status state after a first event, recording in memory a first event filtering condition to determine whether to ignore or process an incoming second event;
initializing an integer count parameter of the first filtering condition that specifies a limit on a number of times within a time period, in excess of which additional events with characteristics that match each other will be ignored or discarded; and
loading a workflow engine with instructions to handle incoming machine-generated events, and executing the instructions that are selected responsive to at least the case-status states and the first event filtering condition.
1 Assignment
0 Petitions
Accused Products
Abstract
The disclosed declarative framework implements a machine for multi-step progression of interaction with an entity. The framework is usable for a broad range of applications—providing a simple rule-based authoring tool for specifying elements and components of a complex state machine, including state definitions, state transition triggers, state transition conditions and state transition actions. Case-status states, a first filtering condition, and a count parameter that specifies a limit on a number of times within a time period in excess of which additional events with characteristics that match will be ignored or discarded are usable to determine whether to ignore or process an incoming event—throttling the rate at which certain actions occur. A workflow engine gets loaded with instructions derived from the states and event filtering conditions, for handling incoming machine-generated events. Once defined, the state machine is automatically generated and implemented based on the declarative input provided.
-
Citations
20 Claims
-
1. A method of simplifying, for a non-programming user, creation of an entity management workflow, the method including:
-
representing a plurality of case-status states in a workflow state machine that handles machine-generated events that are generated by machines without reliance on human-machine interaction; for at least a first case-status state after a first event, recording in memory a first event filtering condition to determine whether to ignore or process an incoming second event; initializing an integer count parameter of the first filtering condition that specifies a limit on a number of times within a time period, in excess of which additional events with characteristics that match each other will be ignored or discarded; and loading a workflow engine with instructions to handle incoming machine-generated events, and executing the instructions that are selected responsive to at least the case-status states and the first event filtering condition. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A method of simplifying, for a non-programming user, creation of an entity management workflow, the method including:
-
representing a plurality of case-status states in a workflow state machine that handles machine-generated events that are generated by machines without reliance on human-machine interaction; for at least a first case-status state after a first event, recording in memory a first event filtering condition to determine whether to ignore or process an incoming second event; wherein the first filtering condition includes a time parameter that specifies a once-only time period that starts with a first event, during which the second event with characteristics that match the first event will be ignored or discarded; and loading a workflow engine with instructions to handle incoming machine-generated events, and executing the instructions that are selected responsive to at least the case-status states and the first event filtering condition. - View Dependent Claims (8, 9, 10)
-
-
11. A non-transitory computer readable storage medium impressed with computer program instructions executable by a processor to simplify for a non-programming user, creation of an entity management workflow, the instructions, when executed on a processor, implement actions comprising:
-
representing a plurality of case-status states in a workflow state machine that handles machine-generated events that are generated by machines without reliance on human-machine interaction; for at least a first case-status state after a first event, recording in memory a first event filtering condition to determine whether to ignore or process an incoming second event; initializing an integer count parameter of the first filtering condition that specifies a limit on a number of times within a time period in excess of which additional events, with characteristics that match each other, will be ignored or discarded; and loading a workflow engine with instructions to handle incoming machine-generated events, and executing the instructions that are selected responsive to at least the case-status states and the first event filtering condition. - View Dependent Claims (12, 13)
-
-
14. A method of simplifying, for a non-programming user, creation of an entity management workflow, the method including:
-
generating for display a data entry columnar GUI that accepts declarative input, which specifies a state machine implementing an automated multi-step progression of interaction with an entity, wherein the data entry columnar includes; at least one column for states in the multi-step progression; time-based transition triggers that cause state transitions; event-based transition triggers, including definitions of conditions that cause state transitions; throttling expressions, which include a time parameter that specifies a once-only time period that starts with a first event, during which a second incoming event with characteristics that match the first event will be ignored or discarded; and receiving declarative input to the data entry columnar that defines state transition triggers which are alternatively specified by timers that cause state transitions upon expiration of a time period and by events that cause state transitions and that defines throttling expressions; receiving declarative input to the data entry columnar that specifies selected alternative actions to perform responsive to the state transitions caused by at least one of time-based transition triggers and event-based transition triggers; and saving the declarative input or a workflow constructed from the declarative input. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
Specification