9.0

Edit

RPA development best practices

Watch webinar video

Download Business Processes used

Here, you can download zip files with Business Processes from the RPA Best Practices webinar:

Wait of condition

Bad practice: use Thread.sleep

<robotics-flow>
  <robot driver="internet explorer" name="driver1">
  <script><![CDATA[
    ie = driver1.getWrappedObject();
    ie.get("...");
    Thread.sleep(2000);
    ie.find(By.id("id1")).click();
    Thread.sleep(2000);
    ie.find(By.id("id2")).click();
    Tread.sleep(3000);
  ]]></script>
  </robot>
</robotics-flow>

Reason: stop executing this thread during this time (2000, 3000, etc.).

Best practice: use WebDriverWait

<robotics-flow>
  <robot driver="internet explorer" name="driver1">
  <script><![CDATA[
    ie = driver1.getWrappedObject();
    ie.get("...");
    WebDriverWait wait = new WebDriverWait(ie, 10);
    wait.until(ExpectedConditions.presenceOfElementLocated(By.id("...")));
    ...
  ]]></script>
  </robot>
</robotics-flow>

Reason: executing thread is not stopped, flexible tool for control of waiting, ignoring exception, control of polling interval, etc.

Close driver manually

If script with the robot plugin fails, all drivers are closed. Processing of errors is done if needed.

Bad practice: close driver manually

<robotics-flow>
  <robot driver="internet explorer" name="driver1">
  <script><![CDATA[
    ie = driver1.getWrappedObject();
    ie.get("...");
    try {
      ...
    } catch (Exception e) {
      ...
    } finally {
      ie.quit();
    }
  ]]></script>
  </robot>
</robotics-flow>

Best practice: throw the error further, and plugin closes all drivers

<robotics-flow>
  <robot driver="internet explorer" name="driver1">
  <script><![CDATA[
    ie = driver1.getWrappedObject();
    ie.get("...");
    try {
      ...
    } catch (Exception e) {
      ...
      throw e;
    }
  ]]></script>
  </robot>
</robotics-flow>

Use Bot Source

Bad practice: Don't use Bot Source in Bot Tasks.

Reason: by default using 5 threads and 50 batch size, it means that all bot configs executing in 5 threads, and in each thread contain 50 bot configs in queue.

Best practice: Use Bot Source to improve performance

Reason: For the Bot Source description, see Bot Source Threads for RPA.

Configured Bot Source: set threads count to number of available nodes, and batch size should be one.

← PreviousNext →