Skip to main content
May 15, 2025
Question

Appian RPA - Custom Code developer [RPA Beginner]

  • May 15, 2025
  • 11 replies
  • 0 views

Hi [mention:b1ec831bc63f413fb8baec7179cee8b3:23b05a61c3e5445190d9bfa00453bce4] / [mention:5357deb643314f689f0553cc98556414:23b05a61c3e5445190d9bfa00453bce4] , 

https://docs.appian.com/suite/help/24.4/rpa-9.16/java-module-ms-outlook.html 

I'm working on creating a custom Java code for the Appian RPA MS Outlook module. While I've finished the Java component, I'm unsure how to integrate or put those into Appian RPA. 

It would be great to get some insights on best practices and common challenges from someone with experience in this area. I tried to follow the Appian RPA documentation, but somewhere felt like lost.

Could anyone with experience incorporating custom Java code into Appian RPA offer some guidance?

 

Thanks,

Bharathwaj RK

11 replies

davidj137213
May 16, 2025

Did you see this part of the documentation?

docs.appian.com/.../deploying-code.html

May 19, 2025

yeah, that is where I am stuck, I was able to build the jar using Maven, but not sure how to deploy this code back to RPA designer.

May 19, 2025

[mention:fcc981e8b4ba4f2ca9666e0fe8df41f0:e9ed411860ed4f2ba0265705b8793d05] [mention:f230ca2f70fd46c69ade4c1fdbb22398:e9ed411860ed4f2ba0265705b8793d05] [mention:6241b81ad8614f7fb6a0592f3a44684e:e9ed411860ed4f2ba0265705b8793d05] 

Tried to create a new maven project using the command from https://docs.appian.com/suite/help/24.4/rpa-9.16/maven-setup.html 

command used

mvn archetype:generate -B -DarchetypeGroupId=com.novayre.jidoka.robot 
-DarchetypeArtifactId=robot-archetype -DarchetypeVersion=3.7.0 
-DgroupId=com.appian.robot -DartifactId=RKB_Outlook 
-Dversion=0.0.1 
-Drepository=https://us.appian.community/rpa/repo/ -Pjidoka-repo

Received Response

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------< org.apache.maven:standalone-pom >-------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> archetype:3.4.0:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< archetype:3.4.0:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO]
[INFO] --- archetype:3.4.0:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Batch mode
[WARNING] Archetype not found in any catalog. Falling back to central repository.
[WARNING] Add a repository with id 'archetype' in your settings.xml if archetype's repository is elsewhere.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.922 s
[INFO] Finished at: 2025-05-19T17:07:32+10:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.4.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.novayre.jidoka.robot:robot-archetype:3.7.0) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

naveenkumarr7411
May 19, 2025

I’ve been through this rabbit hole myself—setting up custom Java code for Appian RPA can feel a bit like taming Outlook itself [emoticon:98f842990f454422aa6a04953955f9d9]

From the error log, it looks like Maven can’t locate the robot-archetype:3.7.0 from the Appian RPA repository. That usually means the custom repository isn’t properly recognized.

Here are a few quick things to check:

1. Make sure settings.xml is updated

You need to add the Appian Community repo explicitly in your Maven settings.xml. Here’s what it should include:



  
    jidoka-repo
    
      
        archetype
        https://us.appian.community/rpa/repo/
      
    
  



  jidoka-repo


2. Try without the -Pjidoka-repo flag initially
Sometimes Maven can behave better if you just include the repo in settings.xml and leave out the profile flag from the command.


If everything is set up right and you still hit a wall, let me know—happy to share a working settings.xml snippet or my own successful setup steps.

May 19, 2025

[mention:845bdda7f0db42be805e5a424906729d:e9ed411860ed4f2ba0265705b8793d05] 

Thank you for your response. still facing some weird error. not sure why.

My settings.xml



  
  
  
  

  
	
	  jidoka
	  appianUsername
	  rpaMavenRefreshKey
	
  
  
	
		jidoka-repo
		
			
				jidoka
				https://us.appian.community/rpa/repo/
				
					true
				
				
					true
				
			
			
				archetype
				https://us.appian.community/rpa/repo/
			
		
	  
		
		  jidoka
		  https://us.appian.community/rpa/repo/
		  
			true
		  
		  
			true
		  
		
	  
	
  
  
  
    jidoka-repo
  


CMD Used - Tried with and without -Pjidoka-repo

mvn archetype:generate -B 
-DarchetypeGroupId=com.novayre.jidoka.robot 
-DarchetypeArtifactId=robot-archetype 
-DarchetypeVersion=3.7.0 
-DgroupId=com.appian.robot 
-DartifactId=RKB_Outlook -Dversion=0.0.1 
-Drepository=https://us.appian.community/rpa/repo/ -Pjidoka-repo

Response: 

[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> archetype:3.4.0:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< archetype:3.4.0:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO]
[INFO] --- archetype:3.4.0:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Batch mode
[INFO] Downloading from archetype: https://us.appian.community/rpa/repo/archetype-catalog.xml
[WARNING] Could not transfer metadata /archetype-catalog.xml from/to archetype (https://us.appian.community/rpa/repo/): status code: 401, reason phrase:  (401)
[WARNING] failed to download from remoteorg.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata /archetype-catalog.xml from/to archetype (https://us.appian.community/rpa/repo/): status code: 401, reason phrase:  (401)
[WARNING] No archetype found in remote catalog. Defaulting to internal catalog
[WARNING] Archetype not found in any catalog. Falling back to central repository.
[WARNING] Add a repository with id 'archetype' in your settings.xml if archetype's repository is elsewhere.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.214 s
[INFO] Finished at: 2025-05-19T17:49:35+10:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.4.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.novayre.jidoka.robot:robot-archetype:3.7.0) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

May 21, 2025

Hey! Great job getting through the Java component, that’s already a solid step forward. When it comes to integrating custom Java code into Appian RPA, the key is making sure your code aligns with Appian’s required structure and annotations.

Common hiccups include dependency conflicts and missing annotations, so double-check those. Also, make sure your RPA agent has the right permissions and environment variables set up to run your script smoothly.

If you're looking for more support or to scale your automation efforts, Charter Global offers end-to-end intelligent automation services that could be helpful: https://www.charterglobal.com/services/intelligent-automation/

May 22, 2025

 [mention:fcc981e8b4ba4f2ca9666e0fe8df41f0:e9ed411860ed4f2ba0265705b8793d05] / [mention:b1ec831bc63f413fb8baec7179cee8b3:23b05a61c3e5445190d9bfa00453bce4] / [mention:5357deb643314f689f0553cc98556414:23b05a61c3e5445190d9bfa00453bce4] 

Team,

Failure in the first step while creating the Custom Code Development for Appian RPA, while creating the Maven project in my local. I have the settings.xml ready and no issues with that.

https://docs.appian.com/suite/help/24.4/rpa-9.16/maven-setup.html#create-the-maven-project

Could someone please help me with progressing on this?

PS: Also I am using my enterprise Appian environment

C:\Users\BharathwajRK\eclipse-workspace\ProcensolLibraries>mvn archetype:generate -B 
-DarchetypeGroupId=com.novayre.jidoka.robot 
-DarchetypeArtifactId=robot-archetype 
-DarchetypeVersion=3.7.0 
-DgroupId=com.appian.robot.procensolLibraries 
-DartifactId=rkb-test-robot 
-Dversion=0.0.1 
-DarchetypeRepository=https://procensoldemo.appiancloud.com/rpa/repo 
-Pjidoka-repo

[INFO] Scanning for projects...
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloading from jidoka: https://procensoldemo.appiancloud.com/rpa/repo/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading from jidoka: https://procensoldemo.appiancloud.com/rpa/repo/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21 kB at 47 kB/s)
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (14 kB at 32 kB/s)
[INFO] Downloading from jidoka: https://procensoldemo.appiancloud.com/rpa/repo/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml (1.1 kB at 33 kB/s)
[INFO]
[INFO] ------------------< org.apache.maven:standalone-pom >-------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] >>> archetype:3.4.0:generate (default-cli) > generate-sources @ standalone-pom >>>
[INFO]
[INFO] <<< archetype:3.4.0:generate (default-cli) < generate-sources @ standalone-pom <<<
[INFO]
[INFO]
[INFO] --- archetype:3.4.0:generate (default-cli) @ standalone-pom ---
[INFO] Generating project in Batch mode
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/archetype-catalog.xml
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/archetype-catalog.xml (17 MB at 12 MB/s)
[WARNING] Archetype not found in any catalog. Falling back to central repository.
[WARNING] Add a repository with id 'archetype' in your settings.xml if archetype's repository is elsewhere.
[INFO] Downloading from jidoka: https://procensoldemo.appiancloud.com/rpa/repo/com/novayre/jidoka/robot/robot-archetype/3.7.0/robot-archetype-3.7.0.jar
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/com/novayre/jidoka/robot/robot-archetype/3.7.0/robot-archetype-3.7.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  6.063 s
[INFO] Finished at: 2025-05-22T10:13:03+10:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.4.0:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.novayre.jidoka.robot:robot-archetype:3.7.0) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Thanks,

Bharathwaj RK