AQuAMan

RE: AQuAMan

nicholasr589844 — Mon, 23 Feb 2026 18:53:03 GMT

Hello, i was curious if there is any documentation on appian, i am trying to dynamically link another apps record type to it so that my apps record type automatically sends data to it to ease onboarding. any ideas?

RE: AQuAMan

simonj3483 — Thu, 05 Feb 2026 15:05:32 GMT

is execute stored procedure still a required plugin as it is deprecated on the Appmarket?

RE: AQuAMan

Appian AppMarket — Tue, 23 Sep 2025 22:00:00 GMT

v7.1.0 Release Notes

Support for installing and running on MS SQL Server.

RE: AQuAMan

glaralandin — Tue, 16 Sep 2025 01:44:01 GMT

Hi [mention:7628077af4b9463e9533a897fad2351f:e9ed411860ed4f2ba0265705b8793d05] , where can I find the detailed documentation for AQuAMan? Thanks!

RE: AQuAMan

AswinKumar — Tue, 09 Sep 2025 18:42:50 GMT

Hi ,

I’m using the Aquaman and facing a challenge with Appian Data Types.

Currently, Aquaman is not supporting Data Type Objects, since Appian’s xpathdocument() function only accepts XML instances and not XSD schemas.

My question is:
How can we overcome this limitation?

Is there a recommended way to convert CDT/XSD definitions into XML instances that xpathdocument() can consume?
Or does the plugin have/plan to have support for handling XSD directly?

Thanks in advance for your guidance!

RE: AQuAMan

sohamp0002 — Fri, 24 Jan 2025 08:23:20 GMT

Can I get the app version which is lower or equal to 24.2.760

RE: AQuAMan

Appian AppMarket — Wed, 15 Jan 2025 11:00:00 GMT

v7.0.0 Release Notes

This release augments the existing 'Code Complexity' report to include a report on any 'Magic Numbers' that the SAIL code might contain (numeric literals that probably should be encapsulated in a constant or dynamically retrieved from a data source rather than embedded in the code with no accompanying context.

RE: AQuAMan

ignaciom440 — Thu, 21 Nov 2024 11:43:28 GMT

Hi [mention:7628077af4b9463e9533a897fad2351f:e9ed411860ed4f2ba0265705b8793d05] ,

I'm getting an error importing the application to an environment where the primary language is Spanish, the process models that do not have the Spanish language configured are the next ones:

processModel 0000e58d-b678-8000-3c32-564d98564d98 "{en_GB=AQA Database Object Analysis, en_US=AQA Database Object Analysis}": Se produjo un error al crear processModel [uuid=0000e58d-b678-8000-3c32-564d98564d98]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. The process model must have a valid name in the site primary language: Spanish. (APNX-1-4071-007)

processModel 0002eb2a-bbf6-8000-55a7-3a4d983a4d98 "{en_GB=AQA Interface Object Analysis, en_US=AQA Interface Object Analysis}": Se produjo un error al crear processModel [uuid=0002eb2a-bbf6-8000-55a7-3a4d983a4d98]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. The process model must have a valid name in the site primary language: Spanish. (APNX-1-4071-007)

processModel 0016e5bb-b5d7-8000-3c89-564d98564d98 "{en_GB=AQA Patch Management, en_US=AQA Patch Management}": Se produjo un error al crear processModel [uuid=0016e5bb-b5d7-8000-3c89-564d98564d98]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. The process model must have a valid name in the site primary language: Spanish. (APNX-1-4071-007)

Could you apply this changes?

Thanks in advance.

RE: AQuAMan

vidyaj7821 — Wed, 11 Sep 2024 07:56:12 GMT

HI [mention:7628077af4b9463e9533a897fad2351f:e9ed411860ed4f2ba0265705b8793d05] ,

After adding the application, in QA rule view upon clicking on "Import Test" action it is throwing error, could you pls help on this?

RE: AQuAMan

Anurag — Thu, 05 Sep 2024 12:49:56 GMT

Anyone having working database scripts for this utility using Microsoft SQL Server (version 15.00.4335) Database?

We are using Appian 22.4.455.0

RE: AQuAMan

Zoran Šaronja — Sun, 21 Jul 2024 08:54:30 GMT

Hi!

I am testing the Aquaman on version 24.2 and it seems that definition for Translation Strings are missing from AOA_OBJECT_TYPE, AOA_OBJECT_ATTRIBUTE tables.

Is there a patch existing or planned?

Thank you!

RE: AQuAMan

Swati Sharda — Fri, 05 Jul 2024 07:04:00 GMT

Hi @Stewart Burchell,

Aquaman is not working with latest Appian version 24.2 as we are getting error:

An error occurred while evaluating expression: patchMetaData:rule!AQA_ER_getPatchMetadata(patchContent: pv!patchContent) (Expression evaluation error in rule 'aqa_er_getpatchmetadata' at function 'type!{urn:com:appian:types:AQA}AQA_PATCH_METADATA' [line 26]: Invalid index (2) for list: valid range is 1..1) (Data Outputs)

it is due to change in the order of manifest file in new version:

the new version of manifest file:

Manifest-Version: 1.0
Appian-Version: 24.2.295.0
Created-On: 2024-07-04T12:09:28.760Z

older version:

Manifest-Version: 1.0
Created-On: 2021-08-19T07:11:28.264Z
Appian-Version: 21.2.335.0

I have changed the index in AQA_ER_getPatchMetadata from 3 to 2 but Aquaman result showing no analysis.

Can you please check that.

RE: AQuAMan

JJ Cañas — Tue, 30 Apr 2024 13:09:52 GMT

Hi Team,

The client has asked us if it would be possible to export the Aquaman analyzes. I have seen that the application has this two web apis:

But it seems that none of them work for what the client is asking for.

Is there a way to expose these analyzes in a web api so that they are consumed by a CI/CD tool?

Thanks!

RE: AQuAMan

DimitarK — Thu, 18 Apr 2024 06:24:12 GMT

Hi Team,
For the first time we've tried deploying AQuAMan QA application (in Cloud) but we're seeing behavior which is almost identical to the issue posted by subhadeepr3242 6 months ago - where issue occurs only when evaluation some Process Models, but not others. Here's a stack trace of the error: - any ideas on what can be done?

[1] object: pv!Object, attributeName: #"_a-0000e385-9976-8000-9bac-011c48011c48_3445850", objectAttributes: pv!objectAttributes ) =>(EXCEPTION) [2] 2024-04-15 06:48:58,298 [Appian Work Item - 194049 - WorkID 339 - execution02 - process 536878506 - model 1159 : ExpressionGroupRequest] DEBUG com.appiancorp.core.expr.tree.Variable - Variable local!xPathDocument => Context Reference local!xPathDocument ÎÃ¥Ã 2024-04-15 06:48:58,298 [Appian Work Item - 194049 - WorkID 339 - execution02 - process 536878506 - model 1159 : ExpressionGroupRequest] DEBUG com.appiancorp.core.expr.tree.Variable - Variable local!xPathDocument => Context Reference local!xPathDocument ÎÃ¥Ã 2024-04-15 06:48:58,299 [Appian Work Item - 194049 - WorkID 339 - execution02 - process 536878506 - model 1159 : ExpressionGroupRequest] DEBUG com.appiancorp.core.expr.Parse - =#"_a-0000e385-9976-8000-9bac-011c48011c48_3446005"( object: pv!Object, attributeName: #"_a-0000e385-9976-8000-9bac-011c48011c48_3445850", objectAttributes: pv!objectAttributes ) =>(EXCEPTION) 2024-04-15 06:48:58,299 [Appian Work Item - 194049 - WorkID 339 - execution02 - process 536878506 - model 1159 : ExpressionGroupRequest] DEBUG com.appiancorp.core.expr.Parse - Could not evaluate expression parse tree: =#"_a-0000e385-9976-8000-9bac-011c48011c48_3446005"( object: pv!Object, attributeName: #"_a-0000e385-9976-8000-9bac-011c48011c48_3445850", objectAttributes: pv!objectAttributes ) com.appiancorp.core.expr.exceptions.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error in rule 'aqa_er_getobjectattributevaluebyattributename': Invalid index (1) for list: valid range is empty (APNX-1-4198-000) at <DESIGNER RULE>.(_a-0000e385-9976-8000-9bac-011c48011c48_3446005:1) at ______________________________SAIL_TO_JAVA_BOUNDARY______________________________.esId=BFH2LI9O(Unknown Source) at com.appiancorp.core.expr.exceptions.ExpressionRuntimeException.<init>(ExpressionRuntimeException.java:112) at com.appiancorp.core.expr.exceptions.AppianScriptException.<init>(AppianScriptException.java:28) at com.appiancorp.core.expr.exceptions.AppianScriptException.<init>(AppianScriptException.java:24) at com.appiancorp.core.expr.tree.Select.evalWrapped(Select.java:207) at com.appiancorp.core.expr.Tree.eval(Tree.java:448) at com.appiancorp.core.expr.Tree.eval0(Tree.java:438) at com.appiancorp.core.expr.Tree.eval(Tree.java:341) at com.appiancorp.core.expr.rule.Rule.evalBody(Rule.java:1569) at com.appiancorp.core.expr.rule.Rule.doEval(Rule.java:962) at com.appiancorp.core.expr.rule.Rule.eval(Rule.java:849) at com.appiancorp.core.expr.rule.Rule.evalAndCache(Rule.java:743) at com.appiancorp.core.expr.rule.Rule.eval(Rule.java:735) at com.appiancorp.core.expr.rule.Rule.evalWithMetrics(Rule.java:716) at com.appiancorp.core.expr.rule.Rule.eval(Rule.java:702) at com.appiancorp.core.expr.tree.FreeformRule.evalWrapped(FreeformRule.java:162) at com.appiancorp.core.expr.Tree.eval(Tree.java:448) at com.appiancorp.core.expr.tree.FreeformRule.eval0(FreeformRule.java:133) at com.appiancorp.core.expr.Tree.eval(Tree.java:341) at com.appiancorp.core.expr.Parse.evalInner(Parse.java:433) at com.appiancorp.core.expr.Parse.eval(Parse.java:383) at com.appiancorp.core.expr.Parse.eval(Parse.java:369) at com.appiancorp.core.expr.AppianScriptEngine.eval(AppianScriptEngine.java:79) at com.appiancorp.process.engine.ExpressionGroup.eval(ExpressionGroup.java:290) at com.appiancorp.process.engine.ExpressionGroup.eval(ExpressionGroup.java:354) at com.appiancorp.process.engine.ExpressionGroupRequest.execute0(ExpressionGroupRequest.java:106) at com.appiancorp.common.persistence.data.AppianDataUserContextProvider.executeWithConsistentDataReads(AppianDataUserContextProvider.java:143) at com.appiancorp.process.engine.ProcessContinuationRequest.executeOuter(ProcessContinuationRequest.java:68) at com.appiancorp.process.engine.ContinuationRequest.execute(ContinuationRequest.java:129) at com.appiancorp.process.workpoller.UnattendedRequestHandlerBean.onMessage(UnattendedRequestHandlerBean.java:36) at com.appiancorp.process.workpoller.WorkItem.run(WorkItem.java:110) at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:241) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Caused by: java.lang.ArrayIndexOutOfBoundsException: Invalid index (1) for list: valid range is empty at com.appiancorp.core.expr.portable.storage.StorageArray.arrayIndexOutOfBoundsException(StorageArray.java:360) at com.appiancorp.core.expr.portable.storage.StorageArray.doSelect_integerScalarIndex(StorageArray.java:737) at com.appiancorp.core.expr.portable.storage.Storage.doSelect(Storage.java:735) at com.appiancorp.core.expr.portable.storage.Storage._select(Storage.java:693) at com.appiancorp.core.expr.portable.storage.Storage.select(Storage.java:673) at com.appiancorp.core.expr.portable.Value.select(Value.java:209) at com.appiancorp.core.Data.select(Data.java:124) at com.appiancorp.core.expr.tree.Select.eval(Select.java:223) -- 2024-04-15 06:48:58,300 [Appian Work Item - 194049 - WorkID 339 - execution02 - process 536878506 - model 1159 : ExpressionGroupRequest] ERROR com.appiancorp.process.engine.ExpressionGroup - An error occurred while evaluating expression: =rule!AQA_ER_getObjectAttributeValueByAttributeName( object: pv!Object, attributeName: cons!AQA_TEXT_OBJECT_ATTRIBUTE_NAME, objectAttributes: pv!objectAttributes ) (Expression evaluation error in rule 'aqa_er_getobjectattributevaluebyattributename': Invalid index (1) for list: valid range is empty) com.appiancorp.core.expr.exceptions.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error in rule 'aqa_er_getobjectattributevaluebyattributename': Invalid index (1) for list: valid range is empty (APNX-1-4198-000) at <DESIGNER RULE>.(_a-0000e385-9976-8000-9bac-011c48011c48_3446005:1) at ______________________________SAIL_TO_JAVA_BOUNDARY______________________________.esId=BFH2LI9O(Unknown Source) at com.appiancorp.core.expr.exceptions.ExpressionRuntimeException.<init>(ExpressionRuntimeException.java:112) at com.appiancorp.core.expr.exceptions.AppianScriptException.<init>(AppianScriptException.java:28) at com.appiancorp.core.expr.exceptions.AppianScriptException.<init>(AppianScriptException.java:24) at com.appiancorp.core.expr.tree.Select.evalWrapped(Select.java:207) at com.appiancorp.core.expr.Tree.eval(Tree.java:448) ....

RE: AQuAMan

Kurt Bunge — Wed, 10 Apr 2024 15:10:18 GMT

The last list item for Key Features and Functionality indicates a test is performed for missing accessibilityText parameter values. Note that no one should be relying on this test (the labels test is valid). Just because a component does not have accessibility text does not mean it fails any a11y requirement. In fact, accessibility text should not need to be used in most cases. It should only be used to provide additional information to non-sighted users. However, the need to do so is based on context. If you design your content correctly, accessibility text should never be needed. In cases where you may believe it IS needed, then you should consider redesigning your content so the information is available to all users, not just non-sighted users. The accessibilityText parameter is one of the most overused of Appian component parameters. In most cases where it is used, it either creates redundancy or confusion for users who rely on a screen reader. The parameter name is misleading because its use does not necessarily make content accessible or even "more accessible".