Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

We are getting NO Stream display error

SA-4731

Summary



We are moving from screen1 to screen2 by using submit button,then we are using Back Space Button to go screen1 from Screen2 , then clicking on the submit button that time we are getting" no stream display error".

Also Please let us know the Back Space Button compatability with Browsers.

Error Messages



"No Stream to display error"


Steps to Reproduce



We are moving from screen1 to screen2 by using submit button,then we are using Back Space Button to go screen1 from Screen2 , then clicking on the submit button that time we are getting" no stream display error".


Root Cause



The root cause of this problem is software use/operation error.

 User is moving from screen 1 to screen 2 and presssing Browser back button to comeback to screen1. Again user clicking submit button on screen 1 and observed that "No stream display error". 



Resolution



The explanation for this behavior is as follows: 


Given three solutions to overcome the issue

1)Write javascript code to completely disable the action of browser back button/backspace key in key board.
2)Implement BACK button and do the code of clearing the cache and other customizations for smooth navigation among screens.
3)Use screen flow rule to do navigation among different screens. Convert the use case to screen flow so that you would be having smooth navigation between screens.
 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us