IP Library › Granted Patent US 11,683,385
Granted Patent B2
US 11,683,385 · App. 17/393,260 · Granted Jun 20, 2023

Smart forms for automated configuration of solutions

Inventors: Susheel Nesargi (Saint Johns, FL); David Berglund (Ponte Vedra, FL); Glen Casey (Quinton, AL)
Assignee: Fidelity Information Services. LLC
H04L67/34G06F3/0482G06Q10/0633H04L67/06H04L67/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,683,385
App. No.
17/393,260
Granted
Jun 20, 2023
Kind
B2
Abstract

A smart forms solution that enables transactions institutions to provide configuration parameters in a streamlined manner so that developers can construct end-to-end solutions in an automated manner includes performing, by a processor, operations including: receiving data from a form in a webpage; validating the received data; saving the validated data; determining a location to send the saved data; sending the saved data to the determined location; invoking an API at the determined location with the saved data; and using the saved data to perform a manual operation.

Claims (65)

1. A method comprising:

performing, by a processor, operations including:

receiving data from a form in a webpage;

validating the received data;

saving the validated data;

initiating, by a decisions workflow component, an API call through an API gateway connected to a production firewall to initiate a connection to an automation services component to process the saved data;

creating, by the automation services component using backend automation, a service ticket in a digital workflow component using the saved data;

initiating, by the automation services component using backend automation, an API call in the digital workflow component to retrieve the service ticket;

authenticating, by a python service layer, the retrieved service ticket;

determining, by the digital workflow component, based on the saved data and the service ticket, a location to send the saved data;

sending, by the digital workflow component, the saved data from the service ticket to the determined location;

invoking, by the automation services component using backend automation, an API at the determined location with the saved data from the service ticket;

using, by a terminal emulator, the saved data from the service ticket to automatically perform a manual operation that changes a component at the determined location; and

initiating, by the automation services component, an API call in the digital workflow component to close the service ticket.

2. The method of claim 1 , wherein the validated data is saved in an .xml file.

3. The method of claim 1 , wherein the API is a Representational state transfer (REST) API used for sending parameters.

4. The method of claim 1 , wherein the saved data is provided to the API using a JavaScript Object Notation (JSON) format.

5. The method of claim 1 , wherein the saved data defines an operation that a human user would use to perform the manual operation, and contains data that would otherwise be entered manually while performing the manual operation.

6. The method of claim 1 , wherein the using the saved data to perform a manual operation includes using an open source 3270 terminal emulator.

7. The method of claim 1 , wherein the receiving data from a form in a webpage includes using open source components written in Selenium Python.

8. The method of claim 1 , wherein the manual operation includes logging into an application, navigating through specific screens via one or more of a mouse click or a keystroke, and entering the saved data into an area of functionality of the application.

9. The method of claim 1 , wherein the determining the location to send the saved data includes:

acknowledging a service ticket raised by a requestor,

determining whether the service ticket is associated with user administration including one or more of adding, deleting, or reinstating a user, and

determining the determined location as a mainframe.

10. The method of claim 9 , further comprising sending a notification to the requestor that the service ticket has been processed, and closing the service ticket.

11. A system comprising:

a memory to store instructions; and

a processor to execute the stored instructions to perform operations including:

receiving data from a form in a webpage;

validating the received data;

saving the validated data;

initiating, by a decisions workflow component, an API call through an API gateway connected to a production firewall to initiate a connection to an automation services component to process the saved data;

creating, by the automation services component using backend automation, a service ticket in a digital workflow component using the saved data;

initiating, by the automation services component using backend automation, an API call in the digital workflow component to retrieve the service ticket;

authenticating, by a python service layer, the retrieved service ticket;

determining, by the digital workflow component, based on the saved data and the service ticket, a location to send the saved data;

sending, by the digital workflow component, the saved data from the service ticket to the determined location;

invoking, by the automation services component using backend automation, an API at the determined location with the saved data from the service ticket;

using, by a terminal emulator, the saved data from the service ticket to automatically perform a manual operation that changes a component at the determined location; and

initiating, by the automation services component, an API call in the digital workflow component to close the service ticket.

12. The system of claim 11 , wherein the validated data is saved in an .xml file.

13. The system of claim 11 , wherein the API is a Representational state transfer (REST) API used for sending parameters.

14. The system of claim 11 , wherein the saved data is provided to the API using a JavaScript Object Notation (JSON) format.

15. The system of claim 11 , wherein the saved data defines an operation that a human user would use to perform the manual operation, and contains data that would otherwise be entered manually while performing the manual operation.

16. The system of claim 11 , wherein the using the saved data to perform a manual operation includes using an open source 3270 terminal emulator.

17. The system of claim 11 , wherein the receiving data from a form in a webpage includes using open source components written in Selenium Python.

18. The system of claim 11 , wherein the manual operation includes logging into an application, navigating through specific screens via one or more of a mouse click or a keystroke, and entering the saved data into an area of functionality of the application.

19. The system of claim 11 , wherein the determining the location to send the saved data includes:

acknowledging a service ticket raised by a requestor,

determining whether the service ticket is associated with user administration including one or more of adding, deleting, or reinstating a user, and

determining the determined location as a mainframe.

20. A non-transitory computer-readable medium storing instructions that, when executed by a processor, perform operations including:

receiving data from a form in a webpage;

validating the received data;

saving the validated data;

initiating, by a decisions workflow component, an API call through an API gateway connected to a production firewall to initiate a connection to an automation services component to process the saved data;

creating, by the automation services component using backend automation, a service ticket in a digital workflow component using the saved data;

initiating, by the automation services component using backend automation, an API call in the digital workflow component to retrieve the service ticket;

authenticating, by a python service layer, the retrieved service ticket;

determining, by the digital workflow component, based on the saved data and the service ticket, a location to send the saved data;

sending, by the digital workflow component, the saved data from the service ticket to the determined location;

invoking, by the automation services component using backend automation, an API at the determined location with the saved data from the service ticket;

using, by a terminal emulator, the saved data from the service ticket to automatically perform a manual operation that changes a component at the determined location; and

initiating, by the automation services component, an API call in the digital workflow component to close the service ticket.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 10, 2021
From: NESARGI, SUSHEEL; BERGLUND, DAVID; CASEY, GLEN
To: FIDELITY INFORMATION SERVICES, LLC (FIS)
Reel/Frame 057131/0285 →
Continuity (1)
Related Publication 20230042857A1 · Feb 9, 2023