KB-2312 Preparing for Java 17: A guide for Appian RPA developers

pauline.delacruz — Wed, 05 Jun 2024 19:11:48 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:11:48 PM

Purpose

As part of our commitment to maintaining supported software versions, Appian is updating to Java 17. This indicates that the Java Runtime Environment (JRE) or Java Development Kit (JDK) to Java 17 must be upgraded on all host machines running RPA agents. This required upgrade ensures the Java Virtual Machines (JVM) that run RPA agents are updated and will continue to function seamlessly.

In order to ensure enough time to adapt to this new change, starting with RPA 9.10, Appian RPA agents will now support Java 17 apart from the usual Java 8. From RPA 9.12 onwards (release date: August 2, 2024), Java 8 will no longer be supported, and all RPA agents' JVM are expected to be running on Java 17.

Upgrading to Java 17

The JRE/JDK to Java 17 must be upgraded on all host machines running RPA agents. For custom-made Java robotic tasks, upgrading to Java 17 should not present any problems, as most of the code written for earlier versions of Java is compatible with Java 17. The Appian RPA SDK will be compatible with this new version, but please ensure that the various libraries/frameworks that may have included in the robotic tasks are compatible with this version of the JVM.

Java 17 can be downloaded from Oracle or any OpenJDK vendor. To determine the current version of Java installed, this can be found in the Java Control Panel on Windows and Mac. For more detailed instructions on finding the Java version, please see the following documentation.

RPA Java Developers: Upgrading to Selenium 4

For developers who are only using low-code methods in their robotic tasks, there is no need to review the robotic tasks. The following section is intended for developers who have robotic tasks developed in Java, automate processes in internet browsers, and use the Appian RPA SDK (IWebBrowserSupport interface).

With the release of Appian RPA 9.12, Appian will update the version of Selenium used for the automation of processes on internet browsers. The new version of Selenium 4 allows us to deploy the latest security patches as well as use the latest capabilities provided by this framework.

There are two main points to keep in mind for the upgrade:

Are your robotic tasks using any of these Selenium WebDriver interface methods?
findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, for more information on how to adapt your code, please see the following documentation.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, the code may need to be updated to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. For more information, please consider the following the documentation here.

For a more detailed outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open open a case with Appian Support.

Affected Versions

This article applies to all versions of Appian using RPA.

Last Reviewed: June 2024

Tags: java, RPA, how-to, infrastructure

KB-XXXX Preparing for Java 17: A guide for Appian RPA developers

pauline.delacruz — Wed, 05 Jun 2024 19:01:03 GMT

Revision 9 posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 7:01:03 PM

Purpose

Upgrading to Java 17

RPA Java Developers: Upgrading to Selenium 4

There are two main points to keep in mind for the upgrade:

Are your robotic tasks using any of these Selenium WebDriver interface methods?
findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, for more information on how to adapt your code, please see the following documentation.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

For a more detailed outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open open a case with Appian Support.

Affected Versions

This article applies to all versions of Appian using RPA.

Last Reviewed: June 2024

Tags: java, RPA, how-to, infrastructure

KB-XXXX Preparing for Java 17: A guide for Appian RPA developers

pauline.delacruz — Wed, 05 Jun 2024 18:56:26 GMT

Revision 8 posted to Appian Knowledge Base by pauline.delacruz on 6/5/2024 6:56:26 PM

Purpose

Upgrading to Java 17

RPA Java Developers: Upgrading to Selenium 4

There are two main points to keep in mind for the upgrade:

Are your robotic tasks using any of these Selenium WebDriver interface methods?
findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

For a more detailed outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open open a case with Appian Support.

Affected Versions

This article applies to all versions of Appian using RPA.

Last Reviewed: June 2024

Tags: java, RPA, how-to, infrastructure

KB-XXXX Preparing for Java 17: A guide for Appian RPA developers

Juan Rodríguez — Wed, 05 Jun 2024 10:12:10 GMT

Revision 7 posted to Appian Knowledge Base by Juan Rodríguez on 6/5/2024 10:12:10 AM

As part of our commitment to maintaining supported software versions, we are updating to Java 17. As part of this change, you must upgrade the Java Runtime Environment (JRE) or Java Development Kit (JDK) to Java 17 on all host machines running RPA agents. This required update ensures the Java Virtual Machines (JVM) that run your agents are updated and that they continue to function seamlessly.

In order to ensure you have enough time to adapt to this new change, starting with RPA 9.10, Appian RPA agents will now support Java 17 apart from the usual Java 8. From RPA 9.12 onwards (release date: August 2, 2024), Java 8 will no longer be supported, and RPA agents JVM are expected to be running on Java 17.

Upgrading to Java 17

You must upgrade the JRE/JDK to Java 17 on all host machines running RPA agents. For custom-made Java robotic tasks, upgrading to Java 17 should not present any problems, as most of the code written for earlier versions of Java is compatible with Java 17. The Appian RPA SDK will be compatible with this new version, but you must make sure the various libraries/frameworks you may have included in your robotic tasks are compatible with this version of the JVM.

You can download Java 17 from Oracle's website or use any OpenJDK vendor. If you don't know what version of Java you have installed, you can find the version in the Java Control Panel on Windows and Mac. For more detailed instructions on finding your version of Java, go to How to find Java version in Windows and Mac on the Java website.

RPA Java Developers: Upgrading to Selenium 4

If you are using only low-code methods in your robotic tasks, there is no need to review your robotic tasks. The following paragraph is intended for developers that have robotic tasks developed in Java, that automate processes on internet browsers, and are using the Appian RPA SDK (IWebBrowserSupport interface).

Since you have developed your robotic tasks in Java, you need to review some code, but adapting to Selenium 4 should be straightforward. With the release of Appian RPA version 9.12, we will update the version of Selenium used for the automation of processes on internet browsers. The new version of Selenium 4 allows us to deploy the latest security patches as well as use the latest capabilities provided by this framework. There are two main points to keep in mind for the upgrade:

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Affected Versions

This article applies to all versions of Appian using RPA.

Last Reviewed: June 2024

Tags: java, RPA, how-to, infrastructure

KB-XXXX Preparing for Java 17: A guide for Appian RPA developers

pauline.delacruz — Tue, 04 Jun 2024 16:50:06 GMT

Revision 6 posted to Appian Knowledge Base by pauline.delacruz on 6/4/2024 4:50:06 PM

According to our commitment to maintaining supported software versions, we are updating to Java 17. As part of this change, you must upgrade the Java Runtime Environment (JRE) to Java 17 on all host machines running RPA agents. This required update ensures the Java Virtual Machines (JVM) that run your agents are updated and that they continue to function seamlessly.

Upgrading to Java 17

You must upgrade the Java Runtime Environment (JRE) to Java 17 on all host machines running RPA agents. For custom-made Java robotic tasks, upgrading to Java 17 should not present any problems, as most of the code written for earlier versions of Java is compatible with Java 17. The Appian RPA SDK will be compatible with this new version, but you must make sure the various libraries/frameworks you may have included in your robotic tasks are compatible with this version of the JVM.

RPA Java Developers: Upgrading to Selenium 4

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Affected Versions

This article applies to all versions of Appian using RPA.

Last Reviewed: June 2024

Tags: java, RPA, how-to, infrastructure

Preparing for Java 17: A guide for Appian RPA developers

Juan Rodríguez — Tue, 04 Jun 2024 14:36:12 GMT

Revision 5 posted to Appian Knowledge Base by Juan Rodríguez on 6/4/2024 2:36:12 PM

Upgrading to Java 17

RPA Java Developers: Upgrading to Selenium 4

If you are using only low-code methods in your robotic tasks there is no need to review your robotic tasks. The following paragraph is intended for developers that have robotic tasks developed in Java, that automate processes on internet browsers, and are using the Appian RPA SDK (IWebBrowserSupport interface).

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Tags: java, how-to, infrastructure

Preparing for Java 17: A guide for Appian RPA developers

Juan Rodríguez — Mon, 03 Jun 2024 15:13:27 GMT

Revision 4 posted to Appian Knowledge Base by Juan Rodríguez on 6/3/2024 3:13:27 PM

Upgrading to Java 17

Oracle Java 17 can be downloaded from Oracle website.

RPA Java Developers: Upgrading to Selenium 4

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Tags: java, how-to, infrastructure

Preparing for Java 17: A guide for Appian RPA developers

Juan Rodríguez — Mon, 03 Jun 2024 15:12:04 GMT

Revision 3 posted to Appian Knowledge Base by Juan Rodríguez on 6/3/2024 3:12:04 PM

As part of our commitment to maintaining supported software versions, we are updating to Java 17. As part of this change, you must upgrade the Java Runtime Environment (JRE) to Java 17 on all host machines running RPA agents. This required update ensures the Java Virtual Machines (JVM) that run your agents are updated and that they continue to function seamlessly.

Upgrading to Java 17

Oracle Java 17 can be downloaded from Oracle website.

RPA Java Developers: Upgrading to Selenium 4

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Tags: java, how-to, infrastructure

Preparing for Java 17: A guide for Appian RPA developers

miguel.aguirre — Thu, 23 May 2024 10:28:34 GMT

Revision 2 posted to Appian Knowledge Base by miguel.aguirre on 5/23/2024 10:28:34 AM

In order to ensure you have enough time to adapt to this new change, starting with RPA 9.10, Appian RPA Agents will now support Java 17 apart from the usual Java 8. From RPA 9.12 onwards (release date: August 2, 2024), Java 8 will no longer be supported, and RPA agents JVM are expected to be running on Java 17.

Upgrading to Java 17

All RPA agents must have their Java version updated. For custom-made Java robotic tasks, upgrading to Java 17 should normally not present any problems as most of the code written for earlier versions of Java should work in Java 17. The Appian RPA SDK will be compatible with this new version, but you will need to make sure that the various libraries/frameworks you may have included in your robotic tasks are compatible with this version of the JVM.

The packages can be found in the official Oracle website.

RPA Java Developers: Upgrading to Selenium 4

If you are using only low-code methods in your robotic tasks there is no need to review your Robotic Tasks. The following paragraph is intended to developers that have robotic tasks developed in Java, that automate processes on internet browsers and are not using the Appian RPA SDK (IWebBrowserSupport interface).

Using robotic tasks developed in Java will imply having to review some aspects of the code, although adapting the program for Selenium 4 should not require significant effort. With the release of Appian RPA version 9.12, we will update the version of Selenium used for the automation of processes on internet browsers. The new version of Selenium 4 will allow us to deploy the latest security patches as well as use the latest capabilities provided by this framework. Mainly, there are two key points to have in mind towards the upgrade:

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with Appian RPA Java and Selenium upgrade procedures, please open a Support Case.

Preparing for Java 17: A guide for Appian RPA developers

miguel.aguirre — Thu, 23 May 2024 10:26:47 GMT

Revision 1 posted to Appian Knowledge Base by miguel.aguirre on 5/23/2024 10:26:47 AM

Upgrading to Java 17

The packages can be found in the official Oracle website.

RPA Java Developers: Upgrading to Selenium 4

Are your robotic tasks using any of these Selenium WebDriver interface methods?

findElementByClassName
findElementByCssSelector
findElementById
findElementByLinkText
findElementByName
findElementByPartialLinkText
findElementByTagName
findElementByXPath

If the answer is yes, find more information on how to adapt your code here.

Are your robotic tasks using the object Capabilities or DesiredCapabilities when the Selenium WebDriver is initialized?

If the answer is yes, you may need to adapt your code to use the new objects like FirefoxOptions, ChromeOptions, EdgeOptions, etc. You might want to have this link in consideration.

For a more in-detail outline on the Selenium 4 upgrade procedure, visit their official documentation.

For further assistance with upgrade procedures, please open a Support Case.