Information
  • Author: Appian Corporation
  • Type: Utility
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Industry: All Industries
  • Compatible Version(s): 24.3
  • First Released:
  • Last Updated:
  • Cost: Free
Share
Home » AppMarket » AQuAMan

AQuAMan

Overview

As a Peer Reviewer, I want to have a fast and predictable method of checking the quality of application patches so that I do not have to exert a lot of time and energy manually checking these against the application standards.

As a Lead Developer, I want to define and manage the quality standards that comprise the 'Definition of Good' for my application so that they can be applied and reported on in a peer review against an application patch.

Key Features & Functionality

  • Automate 80% of the Peer Review checklist items
  • Register Appian applications and define common standards across that application
  • Run a suite of tests across an Application patch
  • Report on failed tests
  • Copy tests between applications
  • Define new object/attribute tests (including database table and view objects) and apply within an application
  • Set the reported significance for a failed test (Fail/Warning/Information)
  • Report on unused variables in Expression Rules and Interfaces
  • Report on the complexity score for Expression Rules and Interfaces
Anonymous
  • in reply to Stewart Burchell

    Hello  ,

    Thanks for the update, recently we upgraded or local environment from 22.3 to 23.3 Appian Version. As checked with appian support team, they mention that the XPATH fix is part of the new version.

    However, I am still getting the issue. Raised a Appian Support case to look that is it platform issue or Application?

    Also, as I am installing Application in our local environment, and we have MSSQL DB. Can you please provide the scripts in MSSQL as well? 

    Thanks

  • in reply to sushilk061231

    Hi  

    Apologies for the delay in relying, I've been out of the office.

    I don't have a reference to the hotfix specifically but I do have a reference to a separate support case that you can mention: "612282 - Please make an incident for Xpath broken"

    This should provide enough context for your support engineer to apply the relevant fix.

    regards

    Stewart

  • Hello Team,

    Can you please share the  link to download  "Text File Utilities 2.0"?  I am little confuse between Text utilities and Text File  there are 2 different plugin in App Market? and both them are not in 2.0 version.

    Thanks

    SUshil Kapoor

  • in reply to Stewart Burchell

    Hello  ,

    Can you please let us know the hotfix name or number  which is required to deploy in on premises server to fix the  

     fn!xpathdocument()  ?

    Thanks

    Sushil kapoor

  • v5.0.0 Release Notes
    1. Support for new Object Types:
    2. Portal
    3. AI Skill
    4. Report on potentially risky design constructs:
    5. Process Models with:
    6. Multiple End nodes
    7. Send Message nodes
    8. Receive Message nodes
    9. User Input Tasks with:
    10. no Exception paths
    11. no Escalations
    12. Interface components with no label configured
    13. Interface components with no accessibility text configured

  • in reply to subhadeepr3242

    Hi - apologies for the slow response on this.

    I have discovered that this is due to a change in a release of Appian that causes the fn!xpathdocument() to throw this error when introspecting into some (but not all) Process Models. There is a hotfix for this that you can raise with Appian support. Just mention the error and the fact that it is in the function mentioned and they can apply the hotfix to your environment.

  • in reply to subhadeepr3242

    How to resolve this AQUAMAN issue?

  • in reply to subhadeepr3242

    Hi Stewart,

    Have you had the time to investigate on the issue? I am eagerly waiting for your feedback on the same.

    Thanks,

    Subhadeep

  • in reply to Stewart Burchell

    Hi Stewart,

    Thanks for your quick acknowledgement. Yeah we are seeing this error for all the process models. Whenever a patch contains a Process Model, this error is blocking the patch analysis. A patch without any process model is successfully processed by Aquaman.

    We have further analysed and found that this error surfaced from 18th September, 2023. Prior to that it was all working fine.

    FYI. We are currently on Appian Version: 23.2 and 23.3

    Please find attached instance of the process model, I have used in examining in my second screenshot in earlier post.

    Process Model.xml

    Thanks,

    Subhadeep

  • in reply to subhadeepr3242

    Hi Subhadeep

    I am not seeing this/hearing about this anywhere else. Is it for all your process models or just the one that you are examining in your second screenshot? Are you able to send me an instance of one of your process models?

    thanks

    Stewart

© 2025 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.