Best practices for Citrix automation

Another Monday has developed several tools and collected best practices to increase the stability of processes within the Citrix environment and prevent execution failures.

Global Delay

Not every application environment requires the same performance. If the process is executed in an underperforming Citrix environment, the robot may act faster than the environment itself. This will cause instability and failures.

In addition to the property setting Delaybefore/After, which slows down the execution of the robot, the user also can use the GlobalDelayBefore/After function.

The argument GlobalDelayBefore/After can be set within the argument section. By using Global Delay, the delay is automatically set before or after each action. This allows the user to create a stable basic configuration to better adapt the robot to the related environment.

In this example, the GlobalDelay is set to 2000 milliseconds. This value will be added to the specific Delaybefore/after for each activity.

Delays.png

Wait Image appears

As the performance of a Citrix environment is not always reliable and depends on various factors, using only GlobalDelay is not sufficient in most cases. Currently, Another Monday recommends using the activity Wait Image Appears.

The activity Wait Image Appears waits for a certain image to appear as a base for a decision. This activity is used in combination with the Decision activityThis combination means that the process won´t continue the execution as long as the image has not appeared. So, when entering a new window, the user can place these activities at the beginning of the window scope, to make sure that the window is already opened when executing the next steps.

Flow.png

 

 

Was this article helpful?
0 out of 0 found this helpful