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
  • Hi  , where can I find the detailed documentation for AQuAMan? Thanks!

  • 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!

  • I'm afraid not. I only make the current version available for support purposes. Id' recommend you upgrade to 24.3 anyway to benefit from the features made available in that release.

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

  • 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.
  • Hi  ,

    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.

  • In the Application Record Type remove the line "isCancel: null, /* Boolean */" in the context for the Import Tests

  • HI  ,

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

      

  • 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

  • Hi  

    Try changing the end of the expression AQA_ER_getPatchMetadata to this:

      local!appianVersion: filter(
        fn!regexmatch("Appian-Version",_),
        local!manifestContentItems
      ),
      local!createdOn: filter(
        fn!regexmatch("Created-On",_),
        local!manifestContentItems
      ),
      'type!{urn:com:appian:types:AQA}AQA_PATCH_METADATA'(
        appianVersion: trim(split(local!appianVersion,"Appian-Version:"))[2],
        patchDateTime: rule!AQA_ER_getPatchDateTime(patchCreatedDate: trim(split(local!createdOn,"Created-On:"))[2])
      )