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 /Author,

    We are facing issues in Aquaman application while trying to analyse a patch which contains Process Models. Please find the below error:

    "An error occurred while evaluating expression: =rule!AQA_ER_identifyObjectType(objects: pv!patchObjects) (Expression evaluation error in rule 'aqa_er_identifyobjecttype' at function a!forEach [line 7]: Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!forEach [line 14]: Error in a!forEach() expression during iteration 1: Expression evaluation error at function 'xpathdocument' [line 23]: A Namespace with the prefix 'n1' has already been declared.) (Data Inputs)"

    Please find attached screenshots for reference.

      

    Could you please help me with the same. Thanks.

    Regards,

    Subhadeep

  • v2.2.2 Release Notes
    • The 'Execute Stored procedure' plug-in has been deprecated as this functionality is now part of the base Appian product.

  • Please refer to 's comment regarding a modification to the "AQA Tables" database script that is necessary for AquAMan to be compatible with version 23.1 of the Appian Platform.

    Make sure to only change the lines referring to `OBJECT_TYPE_ID` 12, (i.e. Interfaces), and not those referring to Object Type 7, Expression Rules.

  • Hi Author,

    I tried AquAMan with the version 23.1 and while uploading a patch of interfaces , the patch analysis is stuck in 'Analyzing Objects' status because on backend there is a process named 'AQA Analyze Objects Batch System' which gets paused by exception only in case of a patch with interface. 

    Could you please help me with this.

  • I try AquAMan with the version 23.1 and it doesn't work properly. Problem is due to XPath for object type and object attribute for interface. Previously the tag bname was rule but now interface.

    To solve this issue, it is necessary to update some rows of the SQL script by changing:

    /*[name()=\'contentHaul\']/*[name()=\'rule\'] => /*[name()=\'contentHaul\']/*[name()=\'interface\']

  • is there any option for us to push the applications directly to the Aquaman instead of import and export?

  • Yes. I did. run it. After running it ONLY I was able to get rid of the  UI expression error and was successfully verify the installation and also check the one of my application packages

  • Thanks Stewart. I did run the process model. I ran the first check on the Aquaman Patch. It took a bit of time but it completed the test. Very Impressive.

    Next I tried to Import some QA rules. It gave the following error: 

    1. "An Error Has Occurred An error occurred while applying the context for the Application related action [identifier=302]. Details: No process parameter found corresponding to override [name=pv!isCancel]. Non-parameter process variables cannot be overridden."

    2. Second issue : is when I try to Update a registered applicaton including teh Aquaman. it just opens an blank screen. 

  • Hi Anon - did you run the post deployment utility process as per the installation guide? That might explain the error in the group as the value for the Admin Group for AQuAMan won’t have been updated in the database.

  • Tagging you in the hope you see this message :)