US 10,474,506 B1Granted

Finite state machine driven workflows

AssigneeCapital One Services, LLC

InventorsRocky Gray, Justin Bachorik, Randall Randall

Life of this patent

Estimating the term…

Loading patent…

Abstract

Disclosed herein are embodiments for providing finite state machine driven workflows. In an embodiment, a workflow template is defined for a type of task. The workflow template may represent a finite state machine. The workflow template may be linked to an external party and an asset type, which may be stored in a workflow database. An asset may be received from the external party including an external party attribute identifying the external party, an asset type attribute, and an owner attribute. The owner attribute may be associated with an application end user. A determination may be made whether the external party attribute and the asset type attribute of the asset match the external party and the asset type linked to the workflow template. If a match is determined, instances of the task and the one or more actions of the workflow template may be created.

Claims20

Dependent claims

A system, comprising:

a memory;
and
at least one processor coupled to the memory and configured to perform operations comprising:
defining a workflow template for a type of task, the workflow template representing a finite state machine, wherein the workflow template includes a task, one or more actions, and one or more events;
linking the workflow template to an external party and an asset type stored in a workflow database;
receiving an asset from the external party, the asset including an external party attribute, an asset type attribute, and an owner attribute, wherein the owner attribute is associated with an application end user;
determining whether the external party attribute and the asset type attribute of the asset match the external party and the asset type linked to the workflow template;
and
creating instances of the task and the one or more actions of the workflow template when the external party attribute and the asset type attribute of the asset match the external party and the asset type of the workflow template,
wherein the task instance includes a task status indicating a current workflow state of the finite state machine, and wherein the one or more action instances enable interaction between the application end user and the task instance.

7 more elements

A computer-implemented method, comprising:

defining a workflow template for a type of task, the workflow template representing a finite state machine, wherein the workflow template includes a task, one or more actions, and one or more events;
linking the workflow template to an external party and an asset type stored in a workflow database;
receiving an asset from the external party, the asset including an external party attribute, an asset type attribute, and an owner attribute, wherein the owner attribute is associated with an application end user;
determining whether the external party attribute and the asset type attribute of the asset match the external party and the asset type linked to the workflow template;
and
creating instances of the task and the one or more actions of the workflow template when determining that the external party attribute and the asset type attribute of the asset match the external party and the asset type of the workflow template,
wherein the task instance includes a task status indicating a current workflow state of the finite state machine, and wherein the one or more action instances enable interaction between the application end user and the task instance.

4 more elements

A non-transitory computer-readable storage device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

defining a workflow template for a type of task, the workflow template representing a finite state machine, wherein the workflow template includes a task, one or more actions, and one or more events;
linking the workflow template to an external party and an asset type stored in a workflow database;
receiving an asset from the external party, the asset including an external party attribute, an asset type attribute, and an owner attribute, wherein the owner attribute is associated with an application end user;
determining whether the external party attribute and the asset type attribute of the asset match the external party and the asset type linked to the workflow template;
and
creating instances of the task and the one or more actions of the workflow template when determining that the external party attribute and the asset type attribute of the asset match the external party and the asset type of the workflow template,
wherein the task instance includes a task status indicating a current workflow state of the finite state machine, and wherein the one or more action instances enable interaction between the application end user and the task instance.

4 more elements

Dependencies are inferred from the claim text.