Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Determining if Robot Runtime is running on a Citrix server

Updated on September 21, 2021

If a connection to a Citrix server times out due to session inactivity, the Robot Runtime client does not receive any notification. To address this issue, use the IsContextConnected static method.

The IsContextConnected method takes the context name as an argument and returns a Boolean value that indicate whether the context is connected. The context name is case insensitive. There is a 10-second timeout interval before the methods returns a False value, to indicate that there is no longer a connection.

Adding the IsContextConnected method to the Robot Studio toolbox

  1. In Robot Studio, open the Runtime tab in the Toolbox window.
  2. Right-click in the Runtime tab and select Choose Items.
  3. In the Add Toolbox Items dialog, click the Pega Robot Static Members tab.
  4. Click Browse and then select the OpenSpan.Runtime.Core.dll file in the Pega Robot Studio program folder.
  5. Expand the RuntimeHost tree view node and select the IsContextConnected check box.
  6. Click OKto save your changes.

    The following is an example:

    When using this static method within an automation, you must add the Citrix Context name in the connection block property.

    Adding the Citrix Context name in the connection block property

     

     

     

     

     

     

     

     

     

    • Previous topic How do Robot Runtime and Robot Manager work together?
    • Next topic Does spyware detection software affect Studio's ability to interrogate and integrate applications?

    Have a question? Get answers now.

    Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us