Skip to main content
Version: 10.2.9

Create ODF 2 project

Explore IDEA adoption scenarios

There are two scenarios to create a project:

  • You start a project, and you want to begin using IDEA for Bot Task testing. In this case, it is highly recommended generating a project from an ODF 2 Archetype.
  • You are already in the middle of the work on an ODF-based project, and you want to start using IDEA for Bot Task testing. In this case, the recommendation is to add dependencies.

Scenario 1: create project

For instructions, refer to the Create project guide.

Scenario 2: switch to existing project

note

Required Maven dependencies are already auto-generated in your POM when you create a project from the latest ODF 2 Archetype. In this case, the maniputations below are not needed.

If you manually upgrade your legacy project and want to add execution support in IDEA, perform these steps manually:

  1. Add the Bot Task JUnit library (will be pulled from repository.workfusion.com by Maven) as a test scope dependency to an ODF-BCB module.
  2. At the same location, specify bot-execution-engine that is compatible with your ODF version.
<dependencies>
<dependency>
<groupId>com.workfusion.odf</groupId>
<artifactId>bot-task-junit</artifactId>
<version>${latest.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.workfusion.studio</groupId>
<artifactId>bot-execution-engine</artifactId>
<version>${odf.compatible.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
tip

To see compatible versions of the dependencies, generate a new project from a Simple Archetype version that corresponds to the version of the WorkFusion platform you use. Copy the dependencies from the ODF-BCB module's POM.xml.

Build Maven project

You can use any of IDEA build tools. For example, the Build Project icon on the top right. 

Known issues

PKIX path building failed

During a Maven build, you can get the following exception: PKIX path building failed. For more details, follow this link.

To fix the issue, add the following JVM parameters:

MAVEN_OPTS="-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true"

Alternatively, open the nexus/central repository in your browser, download the certificate, and import it to the Java TrustStore on your local machine.