Common platform for fulfilling different actions

Patent metadata

Field	Value
Publication number	US-11599406-B2
Application number	US-202117165332-A
Country	US
Kind code	B2
Filing date	Feb 2, 2021
Priority date	Feb 2, 2021
Publication date	Mar 7, 2023
Grant date	Mar 7, 2023

Abstract

In some implementations, a device may receive action information, for an action from multiple actions, that indicates at least one of code associated with the action or one or more inputs required to complete the action. The device may receive workflow information, for a workflow included in a set of workflows, that indicates one or more actions from the multiple actions and an order in which the one or more actions are to be completed for the workflow. The device may receive, via an application programming interface (API) call, a request to complete the workflow The device may identify the workflow information associated with the workflow in a data structure. The device may perform the workflow based on the workflow information and the one or more inputs by executing code for the one or more actions indicated by the workflow information and in the order indicated by the workflow information.

First claim

What is claimed is:

1. A system for providing a common application programming interface (API) for executing different procedures, the system comprising:
one or more memories; and
one or more processors, communicatively coupled to the one or more memories, configured to:
store code, associated with performing an action, in an action database, wherein the action database stores code for multiple actions;
obtain information, for a set of procedures, including procedure information for a procedure, of the set of procedures, that indicates at least one of:
input information, associated with the procedure, that indicates one or more inputs for the API associated with the procedure,
a set of actions, from the multiple actions identified in the action database, associated with the procedure,
an order that the set of actions are to be executed for the procedure, or
failure information, for each action included in the set of actions, that indicates whether the procedure is to continue if a particular action included in the set of actions fails;

receive, via an API call, a request to execute the procedure, wherein the request indicates the procedure and values or information for the one or more inputs for the API;
identify one or more parameters that indicate a quantity of requests, associated with one or more actions of the set of actions, permitted over a predetermined time period;
execute the procedure based on the one or more parameters, based on the procedure information,. and based on the one or more inputs, wherein executing the procedure includes executing code for the one or more actions; and
create a monitoring record associated with the request, based on executing the procedure, that indicates information generated by executing the procedure.

2. The system of claim 1 , wherein the one or more processors are further configured to:
identify, based on executing the procedure or based on the monitoring record, a failure associated with the one or more actions included in the set of actions; and
automatically execute the code for the one or more actions based on identifying the failure.

3. The system of claim 1 , wherein the one or more processors, when receiving the request to execute the procedure, are configured to:
receive an indication of target information associated with an expected outcome of executing the procedure.

4. The system of claim 3 , wherein the one or more processors are further configured to:
compare the target information to actual information generated as a result of executing the procedure, wherein the actual information is indicated by:
the monitoring record, or
a data source that stores information associated with the procedure; and

determine whether the procedure has been successfully completed based on comparing the target information to the actual information.

5. The system of claim 4 , wherein the one or more processors, when determining whether the procedure has been successfully completed based on comparing the target information to the actual information, are configured to:
perform a failure operation based on determining that that the procedure has not been successfully completed, wherein the failure operation includes at least one of:
transmitting, to a device associated with the API call or associated with the procedure, an indication that the procedure has not been successfully completed, or
executing code for the one or more actions included in the set of actions.

6. The system of claim 1 , wherein the one or more processors, when obtaining the procedure information for the set of procedures, are configured to:
provide a user interface to be displayed by a client device, wherein the user interface indicates information associated with the set of actions;
receive, from the client device and based on an input provided via the user interface, an indication of the procedure information for the procedure included in the set of procedures; and
store the procedure information in the action database or another database.

7. The system of claim 1 , wherein the one or more processors, when creating the monitoring record associated with the request, are configured to:
determine whether each action included in the set of actions has been successfully completed;
identify, for the one or more actions, one or more data points generated based on executing the code associated with the action; and
create the monitoring record to include at least one of:
an indication, for each action included in the set of actions, of whether the action has been successfully completed, or
an indication, for the one or more actions included in the set of actions, of the one or more data points.

8. The system of claim 1 , wherein the one or more processors, when executing the procedure, are configured to:
identify, for the one or more actions, one or more parameters associated with the one or more actions, wherein the one or more parameters include at least one of:
a cap parameter indicating a permissible number of requests associated with the one or more actions permitted over a time period, or
a rate parameter indicating a permissible rate of requests associated with the one or more actions;

determine whether the request to execute the procedure satisfies the one or more parameters; and
execute code for the one or more actions if the request to execute the procedure satisfies the one or more parameters.

9. The system of claim 1 , wherein the one or more processors are further configured to:
enable testing of the procedure, prior to executing the procedure, wherein the testing comprises:
receiving one or more test inputs associated with testing a particular action of the set of actions; and
providing one or more outputs based on the one or more test inputs.

10. A method for providing a generic platform for completing different workflows, the method comprising:
receiving, by a device, first information associated with performing multiple actions, wherein the first information includes action information, for an action included in the multiple actions, that indicates at least one of code associated with the action or one or more inputs required to complete the action;
receiving, by the device, second information for a set of workflows, including workflow information, for a workflow included in the set of workflows, that indicates one or more actions from the multiple actions and an order in which the one or more actions are to be completed for the workflow;
storing, by the device, the first information associated with performing the multiple actions and the second information for the set of workflows in a data structure;
receiving, by the device, a request to complete the workflow included in the set of workflows, wherein the request indicates the workflow and one or more inputs associated with the workflow;
identifying, by the device, the workflow information associated with the workflow in the data structure;
identifying, by the device, one or more parameters that indicate a quantity of requests, associated with the one or more actions, permitted over a predetermined time period;
performing, by the device, the workflow based on the one or more parameters, based on the workflow information,. and based on the one or more inputs, wherein performing the workflow includes iteratively executing code for the one or more actions indicated by the workflow information and in the order indicated by the workflow information; and
generating, by the device, monitoring information associated with the request based on performing the workflow that indicates output information of the workflow and a result of performing the workflow.

11. The meth

Assignees

• Capital One Services Llc

Inventors

• Grimes Thomas
• Jacobi Allan
• Williams Michael
• Brown Matthew
• Sullivan Keegan
• Wydler Kenneth

Classifications

• G06Q10/0633

  Workflow analysis · CPC title

• G06F11/0787

  Storage of error reports, e.g. persistent data storage, storage using memory protection · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F11/327

  Alarm or error message display · CPC title

• G06F11/079 Primary

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title