SYSTEMS AND METHODS FOR ENTERPRISE WEB APPLICATION DASHBOARD MANAGEMENT

• US 20200133982A1
• Filed: 06/26/2018
• Published: 04/30/2020
• Est. Priority Date: 06/26/2017
• Status: Active Grant

• Current Assignee: Nasdaq, Inc.
• Original Assignee: Nasdaq, Inc.
• Inventors: THANGESWARAN, Sivakumaresan, CHANDRAMOHAN, Binumohan, VEDHA SIVA, Rajkumar
• Granted Patent: US 11,210,353 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06Q 10/0639 Performance analysis of employees; Performance analysis of enterprise or organisation operations
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

The described technology relates to developing and/or maintaining dashboards in enterprise web applications. In some aspects, a portal web application is configured to provide a user interface on a client device to create or modify a dashboard which includes a first plurality of widgets. A second plurality of widgets includes widgets published to the portal web application from a plurality of subscriber web applications, where each of the second plurality of widgets is used in at least one of said subscriber web applications, and the first plurality of widgets includes one or more widgets from the second plurality of widgets. In some other aspects, a dashboard management service is provided by which respective enterprise web applications can create and host widgets while sharing the same with other enterprise web applications which use dashboards developed using the dashboard management service.

Claims

1. A system to create and maintain enterprise web application dashboards, the system comprising:

a first processing system configured to execute a portal web application configured to provide a user interface on a client device to create or modify a dashboard which includes a first plurality of widgets; and

a first storage storing a second plurality of widgets including widgets published to the portal web application from a plurality of subscriber web applications,

wherein each of the second plurality of widgets is used in at least one of said subscriber web applications, and

wherein the first plurality of widgets includes one or more widgets from the second plurality of widgets.

2. The system according to claim 1, further comprising:

an entitlement database associating one or more entitlements with each user and/or with each of a plurality of third party services; and

a widget metadata database associating a requirement for one or more entitlements with each widget of the second plurality of widgets,

wherein the portal web application is further configured to;

in response to a selection of a first widget from the second plurality of widgets to display in the dashboard, display the first widget in the dashboard if an entitlement associating the user to a third party data service used by the first widget is valid, and prevent display of the first widget in the dashboard if said entitlement is not found or is invalid.

3. The system according to claim 2, wherein the first widget is from the first plurality of widgets, and wherein, when the first widget is prevented from displaying in the dashboard:

(a) other widgets are automatically rearranged in the dashboard, and/or at least one of the widgets in the first plurality of widgets automatically changes its displayed data in response.

4. The system according to claim 2, wherein a context of the first widget is configured to be published by the first widget and/or the dashboard, and wherein at least one of the widgets in the first plurality of widgets dynamically changes its display in response to a change in the context of the first widget or the dashboard.

5. The system according to claim 4, wherein the portal web application and/or a dashboard software development kit (SDK) provided by the portal web application, provides a user interface for associating the context with the first widget and others of the first plurality of widgets.

6. The system according to claim 1, wherein the at least one storage stores a software development kit (SDK) which includes tools for creating, packaging and publishing widgets, wherein the SDK is downloaded to the user on the client device, and wherein the downloaded SDK is used in a development environment of one of said subscriber web applications to create one of said first plurality of widgets.

7. The system according to claim 6, wherein the at least one storage further stores an Angular JS module, and is provided to the user to use in said development environment to test said created widgets in an environment other than the portal web application.

8. The system according to claim 1, wherein the first plurality of widgets include one or more widgets created using the portal web application.

9. The system according to claim 8, wherein the first plurality of widgets include one or more widgets imported from a third party application different from the portal web application and the plurality of subscriber web applications.

10. The system according to claim 1, wherein the portal web application is further configured to host the created or modified dashboard.

11. The system according to claim 1, wherein the first processing system is configured to enable said subscriber web applications to publish widgets without a deployment to the portal web application.

12. The system according to claim 1, wherein the system further comprises a widget metadata database which associates each of the second plurality of widgets with a respective widget context.

13. The system according to claim 1, further comprising a second storage storing one or more libraries configured for use by applications for creating and/or rendering dashboards, wherein, a library from said libraries is injected as a dependency to a widget, wherein the library includes access to a data service.

14. The system according to claim 1, wherein each widget of the first plurality of widgets includes a standardized contract, and wherein the contract defines one or more parameters to be satisfied by an application that uses the widget, and wherein the contract is stored in a metadata database in association with the widget.

15. The system according to claim 1, further comprising a database storing information on the dashboard, information on each of the first plurality of widgets, and the relationships.

16. The system according to claim 15, wherein the first processing system is further configured to cache a user state associated with each of said first plurality of widgets and/or the dashboard.

17. The system according to claim 1, wherein at least one of the second plurality of widgets being created in an environment different from the portal web application, and published to the portal web application.

18. The system according to claim 1, wherein at least one of the first plurality of widgets includes a preconfigured expiry date and/or expiry time.

19. A method, comprising:

executing, on a server computer processing system, a portal web application configured to provide a user interface to create a dashboard including a first plurality of widgets, and publish widgets from one or more subscriber web applications;

receiving a request from a user of a client computer system to create a new dashboard; and

enabling the user to select at least some of the first plurality of widgets from a second plurality of widgets stored on a first storage to arrange on the new dashboard, the second plurality of widgets including widgets published by a plurality of subscriber web applications to the portal web application.

20. A non-transitory computer readable storage medium storing instructions which, when executed by at least one processor of a server computer processing system provides for:

executing, on the server computer processing system, a portal web application configured to provide a user interface to create a dashboard including a first plurality of widgets, and publish widgets from one or more subscriber web applications;

receiving a request from a user of a client computer system to create a new dashboard; and

enabling the user to select at least some of the first plurality of widgets from a second plurality of widgets stored on a first storage to arrange on the new dashboard, the second plurality of widgets including widgets published by a plurality of subscriber web applications to the portal web application.

21-33. -33. (canceled)