# US 2022/0284367 A1 · Titanium Task-Engine System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0284367 A1
- Document ID: US20220284367A1
- Status: Published application
- Kind: A1
- Application number: 17/751,542
- Filed: 2022-05-23
- Published: 2022-09-08
- Earliest claimed: 2019-10-25
- Assignees: Nintex UK Ltd.
- Applicants: Nintex UK Ltd.
- Inventors: Alain Marie Patrice Gentilhomme; Ryan Christopher Duguid; Adrian Rosario Francis Bezzina; Zoe Dee Clelland
- Web page: https://patentgrep.com/patent/US20220284367A1

## CPC

- G06Q 10/06311: {Scheduling, planning or task assignment for a person or group}
- G06Q 10/0633: Workflow analysis
- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The present disclosure is related to computing devices, systems, and methods for a new task-engine system that connects to a variety of task-interaction providers, enabling a user to use any one of multiple task-interaction providers to create and complete tasks within a workflow. That is, the connection to a variety of task-interaction providers allows a user to interact with the workflow through any of the task-interaction providers and create and/or complete any number of tasks in the workflow. The task-engine system may also update the creation and/or completion of a workflow task in all other task-interaction providers, such that all users may be aware of, or notified of, the current state of the workflow through any of the task-interaction providers.

## Claims

### Claim 1

A computing device comprising:
a processor; and
a non-transitory, computer-readable medium operably coupled to the processor, the computer-readable medium having computer-readable instructions stored thereon that, when executed by the processor, cause the computing device to,
receive at least one task;
determine a connector for the at least one task, wherein the connector comprises a proxy for communicating with at least one task-interaction provider;
connect to the determined connector;
send the at least one task, through the determined and connected connector, to at least one task-interaction provider;
receive, based at least in part on the sending, a response from the at least one task-interaction provider.

### Claim 2 (depends on 1)

The computing device of claim 1, wherein the at least one task-interaction provider is external to the computing device.

### Claim 3 (depends on 1)

The computing device of claim 1, wherein the computer-readable instructions further cause the computing device to:
configure the response; and
deliver the configured response.

### Claim 4 (depends on 3)

The computing device of claim 3, wherein the least one task is received from an originating source, wherein the computer-readable instructions further cause the computing device to:
configure the response in accordance with the originating source; and
deliver the configured response to the originating source.

### Claim 5 (depends on 4)

The computing device of claim 4, wherein the task originating source comprises at least one of a workflow, an RPA, a workflow designer, and combinations thereof.

### Claim 6 (depends on 1)

The computing device of claim 1, wherein the computer-readable instructions further cause the computing device to create a proxy instance associated with the at least one task.

### Claim 7 (depends on 1)

The computing device of claim 1, further comprising a task integration that comprises at least one of a user interface or the connector.

### Claim 8

A method of enabling communication with at least one task-interaction provider, the method comprising:
receiving, by a computing device, at least one task;
determining, by the computing device, a connector for the at least one task, wherein the connector comprises a proxy for communicating with the at least one task-interaction provider;
connecting, by the computing device, to the determined connector;
sending, by the computing device, the at least one task through the connected and determined connector to the at least one task-interaction provider;
receiving, by the computing device, based at least in part on the sending, a response from the at least one task-interaction provider.

### Claim 9 (depends on 8)

The method of claim 8, wherein the at least one task-interaction provider is external to the computing device.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
configuring, by the computing device, the response; and
delivering, by the computing device, the configured response.

### Claim 11 (depends on 10)

The method of claim 10, wherein the at least one task is received from an originating source, and wherein the configuring the response is in accordance with the originating source, and wherein the delivering the configured response is to the originating source.

### Claim 12 (depends on 11)

The method of claim 11, wherein the task originating source comprises at least one of a workflow, an RPA, a workflow designer, and combinations thereof.

### Claim 13 (depends on 8)

The method of claim 8, further comprising:
creating a proxy instance associated with the at least one task.

### Claim 14 (depends on 13)

The method of claim 13, wherein the computing device further comprises a task integration that comprises at least one of a user interface or the connector.

### Claim 15

A non-transitory, computer-readable medium having stored thereon computer-readable instructions that when executed by a computing device cause the computing device to:
receive at least one task;
determine a connector for the at least one task, wherein the connector comprises a proxy for communicating with at least one task-interaction providers;
connect to the determined connector;
send the task through the connected and determined connector to the at least one task-interaction provider;
receive, based at least in part on the sending, a response from the at least one task-interaction provider.

### Claim 16 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the computer-readable instructions further cause the computing device to:
configure the response in accordance with the originating source; and
deliver the configured response.

### Claim 17 (depends on 16)

The non-transitory, computer-readable medium of claim 16, wherein the at least one task is received from an originating source, and the computer-readable instructions further cause the computing device to:
configure the response in accordance with the originating source; and
deliver the configured response to the originating source.

### Claim 18 (depends on 17)

The non-transitory, computer-readable medium of claim 17, wherein the task originating source comprises at least one of a workflow, an RPA, a workflow designer, and combinations thereof.

### Claim 19 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the computer-readable instructions further cause the computing device to:
create a proxy instance associated with the at least one task.

### Claim 20 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the computing device further comprises a task integration that comprises at least one of a user interface or the connector.