OverviewAs 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
Report on missing labels/accessibility text for Interface Object components
Hi Stewart Burchell/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
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
How to resolve this AQUAMAN issue?
Hi Stewart,
Have you had the time to investigate on the issue? I am eagerly waiting for your feedback on the same.
Thanks,
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