IP Library Granted Patent US 10,182,122
Granted Patent B2
US 10,182,122 · App. 14/841,146 · Granted Jan 15, 2019

Action flow fragment management

Inventors: Sachin Gopaldas Totale (Pleasanton, CA); Deepak Michael (Banaglore, IN)
Assignee: Open Text Corporation
H04L67/16H04L67/02H04L67/10H04L67/42
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 10,182,122
App. No.
14/841,146
Granted
Jan 15, 2019
Kind
B2
Abstract

Action flow fragment management includes executing a parent action flow including multiple steps. At least two steps are distinct pages of a web application. During execution of the parent action flow, an action flow fragment expression is obtained and executed using data gathered from a data source to obtain an action flow fragment identifier. An action flow fragment corresponding to the action flow fragment identifier is selected and executed. When execution of the action flow fragment completes, execution of the parent action flow continues.

Claims (88)

1. A method for action flow fragment management comprising:

executing a first parent action flow comprising a first plurality of steps, wherein at least two steps of the first plurality of steps correspond to distinct pages of a web application;

obtaining, during execution of the first parent action flow, a first action flow fragment expression comprising a function on data from one or more data sources configured to output a resulting identifier;

executing the first action flow fragment expression using first data gathered from a first data source to obtain, as output from the first action flow fragment expression, a first action flow fragment identifier identifying a first action flow fragment stored in a fragment store;

selecting, from a plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier, the first action flow fragment reusable in a plurality of action flows;

executing the first action flow fragment that was selected based on the first action flow fragment identifier; and

returning execution to the first parent action flow when execution of the first action flow fragment completes.

2. The method of claim 1 , wherein executing the first action flow fragment expression comprises:

performing an operation in the first action flow fragment expression that identifies an invalid action flow fragment based on the first data, and

selecting a default action flow fragment identifier as the first action flow fragment identifier,

wherein executing the first action flow fragment comprises executing a default action flow fragment in the first parent action flow based on the default action flow fragment identifier.

3. The method of claim 1 , wherein executing the first action flow fragment expression comprises:

performing an operation in the first action flow fragment expression that identifies the first action flow fragment identifier.

4. The method of claim 3 , further comprising:

gathering the first data from an internal source within the first parent action flow,

wherein performing the operation uses the first data from the internal source.

5. The method of claim 4 , further comprising:

gathering the first data from an action flow context of the first parent action flow, wherein performing the operation uses the first data from the action flow context.

6. The method of claim 1 , further comprising:

obtaining, during execution of a second parent action flow, a second action flow fragment expression;

executing the second action flow fragment expression using second data gathered from a second data source to obtain the first action flow fragment identifier;

selecting, from the plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier;

executing the first action flow fragment; and

continuing execution of the second parent action flow when execution of the first action flow fragment completes.

7. The method of claim 1 , further comprising:

executing the first action flow fragment expression using second data gathered from a second data source to obtain a second action flow fragment identifier;

selecting, from the plurality of action flow fragments, a second action flow fragment corresponding to the second action flow fragment identifier;

executing the second action flow fragment; and

continuing execution of the first parent action flow when execution of the second action flow fragment completes.

8. A system for action flow fragment management comprising:

a data repository for storing a plurality of action flow fragments;

a computer processor; and

memory comprising instructions for a fragment subsystem that, when executed on the computer processor;

executes a first parent action flow comprising a first plurality of steps, wherein at least two steps of the first plurality of steps correspond to distinct pages of a web application;

obtains, during execution of the first parent action flow, a first action flow fragment expression comprising a function on data from one or more data sources configured to output a resulting identifier;

executes the first action flow fragment expression using first data gathered from a first data source to obtain, as output from the first action flow fragment expression, a first action flow fragment identifier identifying a first action flow fragment stored in the data repository;

selects, from a plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier, the first action flow fragment reusable in a plurality of action flows;

executes the first action flow fragment that was selected based on the first action flow fragment identifier; and

returns execution to the first parent action flow when execution of the first action flow fragment completes.

9. The system of claim 8 , wherein executing the first action flow fragment expression comprises:

performing an operation in the first action flow fragment expression that identifies an invalid action flow fragment based on the first data, and

selecting a default action flow fragment identifier as the first action flow fragment identifier,

wherein executing the first action flow fragment comprises executing a default action flow fragment in the first parent action flow based on the default action flow fragment identifier.

10. The system of claim 8 , wherein executing the first action flow fragment expression comprises:

performing an operation in the first action flow fragment expression that identifies the first action flow fragment identifier.

11. The system of claim 10 , wherein the fragment subsystem further:

gathers the first data from an internal source within the first parent action flow,

wherein performing the operation uses the first data from the internal source.

12. The system of claim 10 , the fragment subsystem further:

gathers the first data from an action flow context of the first parent action flow, wherein performing the operation uses the first data from the action flow context.

13. The system of claim 8 , the fragment subsystem further:

obtains, during execution of a second parent action flow, a second action flow fragment expression;

executes the second action flow fragment expression using second data gathered from a second data source to obtain the first action flow fragment identifier;

selects, from the plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier;

executes the first action flow fragment; and

continues execution of the second parent action flow when execution of the first action flow fragment completes.

14. The system of claim 8 , the fragment subsystem further:

executes the first action flow fragment expression using second data gathered from a second data source to obtain a second action flow fragment identifier;

selects, from the plurality of action flow fragments, a second action flow fragment corresponding to the second action flow fragment identifier;

executes the second action flow fragment; and

continues execution of the first parent action flow when execution of the second action flow fragment completes.

15. A non-transitory computer readable medium for action flow fragment management comprising computer readable program code for:

executing a first parent action flow comprising a first plurality of steps, wherein at least two steps of the first plurality of steps correspond to distinct pages of a web application;

obtaining, during execution of the first parent action flow, a first action flow fragment expression comprising a function on data from one or more data sources configured to output a resulting identifier;

executing the first action flow fragment expression using first data gathered from a first data source to obtain, as output from the first action flow fragment expression, a first action flow fragment identifier identifying a first action flow fragment stored in a fragment store;

selecting, from a plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier, the plurality of action flow fragment reusable in a plurality of action flows;

executing the first action flow fragment that was selected based on the first action flow fragment identifier; and

returning execution to the first parent action flow when execution of the first action flow fragment completes.

16. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for:

performing an operation in the first action flow fragment expression that identifies an invalid action flow fragment based on the first data, and

selecting a default action flow fragment identifier as the first action flow fragment identifier,

wherein executing the first action flow fragment comprises executing a default action flow fragment in the first parent action flow based on the default action flow fragment identifier.

17. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for:

performing an operation in the first action flow fragment expression that identifies the first action flow fragment identifier.

18. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for:

gathering the first data from an internal source within the first parent action flow,

wherein performing the operation uses the first data from the internal source.

19. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for:

obtaining, during execution of a second parent action flow, a second action flow fragment expression;

executing the second action flow fragment expression using second data gathered from a second data source to obtain the first action flow fragment identifier;

selecting, from the plurality of action flow fragments, the first action flow fragment corresponding to the first action flow fragment identifier;

executing the first action flow fragment; and

continuing execution of the second parent action flow when execution of the first action flow fragment completes.

20. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for:

executing the first action flow fragment expression using second data gathered from a second data source to obtain a second action flow fragment identifier;

selecting, from the plurality of action flow fragments, a second action flow fragment corresponding to the second action flow fragment identifier;

executing the second action flow fragment; and

continuing execution of the first parent action flow when execution of the second action flow fragment completes.

Assignments (7)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2017
From: EMC CORPORATION
To: OPEN TEXT CORPORATION
Reel/Frame 041140/0299 →
RELEASE OF SECURITY INTEREST Recorded Jan 23, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC CORPORATION
Reel/Frame 041073/0443 →
PATENT RELEASE (REEL:40134/FRAME:0001) Recorded Jan 23, 2017
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: EMC CORPORATION, AS GRANTOR
Reel/Frame 041073/0136 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2015
From: TOTALE, SACHIN GOPALDAS; MICHAEL, DEEPAK
To: EMC CORPORATION
Reel/Frame 036628/0619 →
Continuity (1)
Related Publication 20170064013A1 · Mar 2, 2017