RPA Modules

Appian RPA provides several modules that include methods to make it easier to develop the actions a robotic process performs. You can use low-code modules to configure a robotic process more quickly and easily. Java modules are also available for specific actions and use cases.

Low-code modules

Low-code modules streamline the robotic process development process. You don't need to use Java to set up and configure actions in a robotic process workflow. Instead, you'll select options from a menu and configure which variables to use. If you're an Appian developer getting started with Appian RPA, you'll find the low-code modules familiar. Although your robotic process may be complicated, development using low-code modules is simple and accessible.

You can find these low-code modules in the Actions menu when you configure steps in a workflow:

rpa-modules-actions.png

Java modules

Appian RPA's Java modules are collections of interfaces, classes, and methods that developers can use in their code. These modules are designed for more experienced Java developers. These modules are organized based on common use cases, notably regarding the software a robotic process interacts with.

The following modules are available in Appian RPA and are included in the jidoka packages listed in parentheses:

  • Appian Services (jidoka-client-api-appian): Contains methods for common actions interacting with Appian applications, such as calling web APIs, uploading documents, and downloading documents.
  • Client (jidoka-client-api): Available for every robot and provides the basic interfaces and classes needed to develop a robotic process. The interface IRobot is part of this module.
  • Browser (jidoka-browser-api): Enables the robotic process to navigate and interact with web browsers.
  • Falcon (jidoka-falcon-api): Enables image processing and image recognition.
  • Data-provider (jidoka-data-provider-api): Enables access to different data providers, such as Excel and ZIP files and folders.
  • MS Outlook (jidoka-msoutlook-api): Allows for easier handling in Outlook. This module uses Jacob to communicate with COM libraries provided by Outlook.
  • SAP (jidoka-sap-api): Provides access to the available objects in SAP using SAP GUI Scripting.
  • Process Queues (included in jidoka-client-api): Processes items in a queue from multiple robotic processes running in parallel.
  • UI Automation (included in jidoka-client-api): Utilize the UI-Automation framework to allow Windows applications to provide and consume information about a user interface (UI).

For a list of all methods included in each module, consult the Javadocs in the Appian RPA Console. In the console, click Help > Javadoc in the left menu.

Add dependencies

Appian RPA allows you to extend functionality by creating your own Maven projects and referencing default modules. The projects will end as .jar files in the repository, also known as Maven dependencies.

To use a module in your robotic process, you must include its dependency in the pom.xml.

1
2
3
4
5
<dependency>
    <groupId>com.novayre.jidoka.module</groupId>
    <artifactId>package.name</artifactId>
    <version>${jidoka.version}</version>
</dependency>

Modify the following values:

  • package.name is the name of the package that contains the specific module. For example, to add a dependency for the Browser module, it would be jidoka-browser-api. See the list above for the package name associated with each module.
  • ${jidoka.version} specifies the module's current version, which you can find in the following area:

    1
    2
    3
    
    <properties>	
        <jidoka.version>X.Y.Z</jidoka.version>
    </properties>
    

Another way to extend module functionalities is by creating workflow libraries. Learn more about libraries.


This version of the Appian RPA documentation was written for Appian 21.1, and does not represent the interfaces or functionality of other Appian versions.
Open in Github Built: Fri, Sep 17, 2021 (04:05:09 PM)

On This Page

FEEDBACK