User interfaces generated by a workflow engine

• US 9,826,027 B2
• Filed: 08/19/2014
• Issued: 11/21/2017
• Est. Priority Date: 08/19/2014
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Doerr, Anthony J., Panchura, Bradley M., Sridharan, Vinoth, Chmielewski, David R., Helm, Jeremy J., McLean, Joseph W.
• Primary Examiner(s): HAILU, TADESSE
• Application Number:
  US14/463,387
• Publication Number:
  US 20160055126A1
• Time in Patent Office: 1,190 Days
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

According to one embodiment of the present disclosure, a first processor with a store of application rules and a second processor communicably coupled to the first processor. The second processor generates a request for a next user application screen. The request comprises a current application screen identifier and user data. The second processor transmits the request for the user application screen to the first processor. The first processor receives the request for the next user application screen and determines dynamically, based on the current application screen identifier, the user data, and the plurality of application rules, user interface contents of the next user application screen. The first processor formats a response describing the user interface contents of the next user application screen and transmits the response to the second processor. The second processor receives the response and renders the next user application screen.

Claims

1. An apparatus capable of performing a workflow process, the apparatus comprising:

a memory operable to store a plurality of application rules, the application rules describing one or more tasks associated with the workflow process; and

a processor communicably coupled to the memory and operable to repeatedly process a single get next screen request/response interface until the workflow process is complete, wherein the single get next screen request/response interface comprises an application programming interface (API) between a workflow client and the apparatus, and repeatedly processing the single get next screen request/response interface comprises repeating the following steps;

receive, from the workflow client, a next screen request for a next user application screen, the next screen request comprising a text-based screen descriptor meta language interface that includes a current application screen identifier, a next application screen identifier, and user data;

determine dynamically, based on the current application screen identifier, the next application screen identifier, the user data, and the plurality of application rules, user interface contents of the next user application screen;

format a next screen response describing the user interface contents of the next user application screen, the next screen response comprising a text-based screen descriptor meta language interface that includes one or more navigation controls and one or more screen sections, each screen section of the one or more screen sections comprising a related group of input/output controls; and

transmit the next screen response to the workflow client.

2. The apparatus of claim 1, wherein:

the current application screen identifier is a null value;

the next application screen identifier is a null value; and

the user interface contents of the next user application screen include an application initialization screen.

3. The apparatus of claim 1, wherein:

the current application screen identifier comprises a value N;

the next application screen identifier is a null value; and

the user interface contents of the next user application screen include the next application screen N+1 according to the application rules describing one or more tasks associated with the workflow process.

4. The apparatus of claim 1, wherein:

the processor is further operable to determine, based on the next screen request and the plurality of application rules, that an error has occurred; and

the user interface contents of the next user application screen comprise an error message.

5. The apparatus of claim 1, wherein:

the current application screen identifier comprises a value N;

the next application screen identifier comprises a value X; and

the user interface contents of the next user application screen include a modal screen X.

6. The apparatus of claim 1, wherein:

the screen descriptor meta language is based on one of Java Script Object Notation (JSON) or Extensible Markup Language (XML).

7. The apparatus of claim 1, wherein:

the response describing the user interface contents of the next user application screen describes a screen indicating the workflow process is complete.

8. A method of performing a workflow process, the method comprising repeating a single get next screen request/response interface until the workflow process is complete, wherein the single get next screen request/response interface comprises an application programming interface (API) between a workflow client and a workflow server, and repeating the single get next screen request/response interface comprises repeating the following steps:

receiving, from the workflow client, a next screen request for a next user application screen, the next screen request comprising a text-based screen descriptor meta language interface that includes a current application screen identifier, a next application screen identifier, and user data;

determining dynamically, based on the current application screen identifier, the next application screen identifier, the user data, and a plurality of application rules describing one or more tasks associated with the workflow process, user interface contents of the next user application screen;

formatting a next screen response describing the user interface contents of the next user application screen, the next screen response comprising a text-based screen descriptor meta language interface that includes one or more navigation controls and one or more screen sections, each screen section of the one or more screen sections comprising a related group of input/output controls; and

transmitting the next screen response to the workflow client.

9. The method of claim 8, wherein:

the current application screen identifier is a null value;

the next application screen identifier is a null value; and

the user interface contents of the next user application screen include an application initialization screen.

10. The method of claim 8, wherein:

the current application screen identifier comprises a value N;

the next application screen identifier is a null value; and

the user interface contents of the next user application screen include the next application screen N+1 according to the application rules describing one or more tasks associated with the workflow process.

11. The method of claim 8, further comprising determining, based on the next screen request and the plurality of application rules, that an error has occurred;

and

wherein the user interface contents of the next user application screen comprise an error message.

12. The method of claim 8, wherein:

the current application screen identifier comprises a value N;

the next application screen identifier comprises a value X; and

the user interface contents of the next user application screen include a modal screen X.

13. The method of claim 8, wherein:

the screen descriptor meta language is based on one of Java Script Object Notation (JSON) or Extensible Markup Language (XML).

14. The method of claim 8, wherein:

the response describing the user interface contents of the next user application screen describes a screen indicating the workflow process is complete.

15. A system comprising a workflow server and a workflow client communicably coupled by a network and operable to perform a workflow process;

the workflow server comprising;

a memory operable to store a plurality of application rules, the application rules describing one or more tasks associated with the workflow process; and

a processor communicably coupled to the memory;

the workflow client comprising a memory, a processor, and a display;

the processor of the workflow client is-operable to;

generate a next screen request for a next user application screen, the next screen request comprising a text-based screen descriptor meta language interface that includes a current application screen identifier, a next application screen identifier, and user data; and

transmit the next screen request for the user application screen to the workflow server;

the processor of the workflow server is operable to;

receive the next screen request for the next user application screen;

determine dynamically, based on the current application screen identifier, the next application screen identifier, the user data, and the plurality of application rules, user interface contents of the next user application screen;

format a next screen response describing the user interface contents of the next user application screen, the next screen response comprising a text-based screen descriptor meta language interface that includes one or more navigation controls and one or more screen sections, each screen section of the one or more screen sections comprising a related group of input/output controls; and

transmit the response to the workflow client;

the processor of the workflow client is further operable to;

receive the next screen response; and

render the next user application screen on the display.

16. The system of claim 15, wherein:

the capability of the processor of the workflow client to render the next user application screen on a display is independent of the application rules.

17. The system of claim 15, wherein:

the workflow client repeatedly transmits next screen requests to the workflow server until the workflow process is complete.

18. The system of claim 15, wherein:

the screen descriptor meta language is based on one of Java Script Object Notation (JSON) or Extensible Markup Language (XML).