Highlighted
Absent Member.. Absent Member..
Absent Member..
1060 views

Slowness running OO on Web UI

Jump to solution

Hi Everyone,

 

A flow from my desktop  OO client takes 2 minutes. The same flow from the OO client on the  OO server also takes 2 minutes.

 

However, the same flow from the web UI - and on the OO server itself - takes nearly 5 minutes.

 

Yes, it is also running the visuals, but it's a bit too much. Can anyone help? Are there any settings which can be configured to minimise this?

 

Thanks,

 

David Salkin

HP SaaS

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. Absent Member..
Absent Member..

The reason for the slowness is this: that during flow execution input dialog boxes are displayed for user input above the step execution area.  But the web interface takes a very long time before it decides to display each input box.

 

However, if you keep on refreshing the step execution window while waiting for the dialog box to appear (by changing page or enabling/disabling the automatic refresh option) then the input box will appear in its proper time.

 

This defect occurs in all browser types.

 

View solution in original post

0 Likes
6 Replies
Highlighted
Absent Member.
Absent Member.

Hi,

 

Can u please post  OO version u are using ? Please mention contentpack version also.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Version: 9.07.001

Content Pack: 9.0.11.10

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Do an "Instant Run" and see how long it takes. Instant run is like Run All, but without visuals.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Even doing instant run is quite slow for us; we have taken to creating stub flows which dynamically launch the flow we want to run faster. Obviously this means the flow you launch must be capable of running headless.

Highlighted
Absent Member.. Absent Member..
Absent Member..

Good practice to break up into sub flows instead of doing everything in a single flow.

Highlighted
Absent Member.. Absent Member..
Absent Member..

The reason for the slowness is this: that during flow execution input dialog boxes are displayed for user input above the step execution area.  But the web interface takes a very long time before it decides to display each input box.

 

However, if you keep on refreshing the step execution window while waiting for the dialog box to appear (by changing page or enabling/disabling the automatic refresh option) then the input box will appear in its proper time.

 

This defect occurs in all browser types.

 

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.