# US 2021/0263716 A1 · Method and system for implementing custom ui actions in a web application using hidden containers

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

- Number: US 2021/0263716 A1
- Document ID: US20210263716A1
- Status: Published application
- Kind: A1
- Application number: 17/316,401
- Filed: 2021-05-10
- Published: 2021-08-26
- Earliest claimed: 2014-12-30
- Assignees: Open Text Corporation
- Applicants: Open Text Corporation
- Inventors: Sachin Gopaldas Totale; Swati Bhatia
- Web page: https://patentgrep.com/patent/US20210263716A1

## CPC

- G06F 8/38: for implementing user interfaces
- G06F 8/60: Software deployment
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In general, the disclosed technology relates to a method for generating a web application. The method includes selecting a webpage in the web application and implementing a custom user interface (UI) action on the webpage. Implementing the custom UI action on the webpage may include creating a hidden component on the webpage, associating a custom UI action with the hidden component, specifying at least one input for the hidden component based on the custom UI action, specifying at least one target output for the hidden component based on the custom UI action, and associating the hidden component with a custom UI action trigger event. The method further includes deploying the web application after implementing the custom UI action on the webpage.

## Claims

### Claim 1

A computer program product comprising a non-transitory, computer-readable medium storing computer-readable instructions, the computer-readable instructions comprising instructions for:
providing, by a development server, a designer user interface to a designer client computer;
receiving via the designer user interface, user input to create a custom user interface (UI) action component, the custom UI action component comprising custom UI action source code for a custom UI action and a custom UI action definition that references the custom UI action source code for the custom UI action and specifies a first input to obtain for the custom UI action and a custom UI action trigger for the custom UI action;
receiving at the development server, an indication that the custom UI action component has been selected for incorporation into a webpage of a web application;
based on user interaction with the designer user interface,
creating a hidden component on the webpage of the web application;
associating the custom UI action component with the hidden component of the webpage; and
associating the custom UI action component with a first visible component of the webpage;
configuring, by the development server, the hidden component according to the custom UI action definition based on associating the custom UI action component with the hidden component;
deploying the web application as a deployed web application to a web server, the deployed web application comprising code for:
transmitting the webpage to a web browser to be rendered in the web browser; and
initializing the hidden component to listen for the custom UI action trigger, wherein the hidden component is responsive to the custom UI action trigger to obtain the first input from the first visible component and execute the custom UI action on the first input within the hidden component to generate a result, wherein the deployed web application is executable to provide the webpage, including the first visible component and the hidden component, to a client device in response to a request.

### Claim 2 (depends on 1)

The computer program product of claim 1, wherein the hidden component provides an interface between the custom UI action and the first visible component on the webpage.

### Claim 3 (depends on 1)

The computer program product of claim 1, wherein the computer-readable instructions further comprise instructions for configuring the hidden component to publish an event on a software event bus, the event including the result of the execution of the custom UI action.

### Claim 4 (depends on 1)

The computer program product of claim 1, wherein the webpage includes a second visible component, wherein the hidden component is configured to listen for the custom UI action trigger from the second visible component.

### Claim 5 (depends on 1)

The computer program product of claim 1, wherein the custom UI action definition specifies a first output target and wherein the computer-readable instructions further comprise instructions for configuring the hidden component to provide the result of the execution of the custom UI action to the first output target.

### Claim 6 (depends on 5)

The computer program product of claim 5, wherein the webpage comprises a second visible component and wherein the first output target is the second visible component.

### Claim 7 (depends on 5)

The computer program product of claim 5, wherein the first output target is a data service associated with the deployed web application.

### Claim 8 (depends on 5)

The computer program product of claim 5, wherein configuring the hidden component according to the custom UI action definition based on associating the custom UI action component with the hidden component comprises:
specifying that the first input is an input for the hidden component based on the custom UI action definition;
associating the hidden component with the custom UI action trigger based on the custom UI action definition; and
specifying the first output target as an output target for the hidden component based on the custom UI action definition.

### Claim 9

A method for implementing custom user interface actions in web applications, the method comprising:
providing, by a development server, a designer user interface to a designer client computer;
receiving via the designer user interface user inputs for creating a custom user interface (UI) action component, the custom UI action component comprising custom UI action source code for a custom UI action and a custom UI action definition that references the custom UI action source code for the custom UI action and specifies a first input to obtain for the custom UI action and a custom UI action trigger for the custom UI action;
receiving via the designer user interface, an input selecting the custom UI action component for incorporation into a webpage of a web application;
associating, based on user interaction with the designer user interface, the custom UI action component with a hidden component on the webpage;
associating, based on user interaction with the designer user interface, the custom UI action component with a first visible component of the webpage;
configuring the hidden component according to the custom UI action definition based on the association of the hidden component with the custom UI action component and the first visible component;
deploying the web application as a deployed web application to a web server, the deployed web application comprising code for:
transmitting the webpage to a web browser to be rendered in the web browser; and
initializing the hidden component to listen for the custom UI action trigger, wherein the hidden component is responsive to the custom UI action trigger to obtain the first input from the first visible component and execute the custom UI action on the first input within the hidden component to generate a result, wherein the deployed web application is executable to provide the webpage, including the first visible component and the hidden component, to a client device in response to a request.

### Claim 10 (depends on 9)

The method of claim 9, wherein the hidden component provides an interface between the custom UI action and the first visible component on the webpage.

### Claim 11 (depends on 9)

The method of claim 9, wherein the custom UI action definition comprises an event to publish based on the result of executing the custom UI action, and wherein configuring the hidden component according to the custom UI action definition comprises configuring the hidden component to publish the event on a software event bus.

### Claim 12 (depends on 9)

The method of claim 9, wherein the webpage includes a second visible component, and wherein the hidden component is configured to listen for the custom UI action trigger from the second visible component.

### Claim 13 (depends on 9)

The method of claim 9, wherein the custom UI action definition specifies a first output target and wherein configuring the hidden component according to the custom UI action definition comprises configuring the hidden component to provide the result of the execution of the custom UI action to the first output target.

### Claim 14 (depends on 13)

The method of claim 13, wherein the webpage comprises a second visible component and wherein the first output target is the second visible component.

### Claim 15 (depends on 13)

The method of claim 13, wherein the first output target is a data service associated with the deployed web application.

### Claim 16 (depends on 13)

The method of claim 13, wherein configuring the hidden component according to the custom UI action definition comprises:
specifying that the first input is an input for the hidden component based on the custom UI action definition;
associating the hidden component with the custom UI action trigger based on the custom UI action definition; and
specifying the first output target as an output target for the hidden component based on the custom UI action definition.

### Claim 17

A system for implementing custom user interface actions in web applications, the system comprising:
a designer client computer;
a web client computer;
a server system comprising:
a web server to host a web application; and
a development environment to develop the web application, the development environment comprising instructions for:
providing a designer user interface to the designer client computer;
receiving via the designer user interface, user input to create a custom user interface (UI) action component, the custom UI action component comprising custom UI action source code for a custom UI action and a custom UI action definition that references the custom UI action source code for the custom UI action and specifies a first input to obtain for the custom UI action and a custom UI action trigger for the custom UI action;
receiving an indication that the custom UI action component has been selected for incorporation into a webpage of a web application;
based on user interaction with the designer user interface,
creating a hidden component on the webpage of the web application;
associating the custom UI action component with the hidden component of the webpage; and
associating the custom UI action component with a first visible component of the webpage;
configuring the hidden component according to the custom UI action definition based on the user associating the custom UI action component with the hidden component;
deploying the web application as a deployed web application to the web server, the deployed web application comprising code for:
transmitting the webpage to the web browser to be rendered in the web browser; and
initializing the hidden component to listen for the custom UI action trigger, wherein the hidden component is responsive to the custom UI action trigger to obtain the first input from the first visible component and execute the custom UI action on the first input within the hidden component to generate a result, wherein the deployed web application is executable to provide the webpage, including the first visible component and the hidden component, to a client device in response to a request.

### Claim 18 (depends on 17)

The system for implementing custom user interface actions in web applications of claim 17, wherein the hidden component provides an interface between the custom UI action and the first visible component on the webpage.

### Claim 19 (depends on 17)

The system for implementing custom user interface actions in web applications of claim 17, wherein the custom UI action definition comprises an event to publish based on the result of executing the custom UI action, and wherein configuring the hidden component according to the custom UI action definition comprises configuring the hidden component to publish the event on a software event bus.

### Claim 20 (depends on 17)

The system for implementing custom user interface actions in web applications of claim 17, wherein the webpage includes a second visible component, wherein the hidden component is configured to listen for the custom UI action trigger from the second visible component.

### Claim 21 (depends on 17)

The system for implementing custom user interface actions in web applications of claim 17, wherein the custom UI action definition specifies a first output target and wherein configuring the hidden component according to the custom UI action definition comprises configuring the hidden component to provide the result of the execution of the custom UI action to the first output target.

### Claim 22 (depends on 21)

The system for implementing custom user interface actions in web applications of claim 21, wherein the webpage comprises a second visible component and wherein the first output target is the second visible component.

### Claim 23 (depends on 21)

The system for implementing custom user interface actions in web applications of claim 21, wherein the first output target is a data service associated with the deployed web application.

### Claim 24 (depends on 21)

The system for implementing custom user interface actions in web applications of claim 21, wherein configuring the hidden component according to the custom UI action definition based on associating the custom UI action component with the hidden component comprises:
specifying that the first input is an input for the hidden component based on the custom UI action definition;
associating the hidden component with the custom UI action trigger based on the custom UI action definition; and
specifying the first output target as an output target for the hidden component based on the custom UI action definition.
