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
Hi Ed - I am looking into this issue. Initially I also thought it was because the was related to the patch now containing the 'patches.xml' file (which isn't an Appian design object) but even excluding this (as you previously mentioned) I am still getting failures. The symptom appears to be that the analysis is incorrectly identifying some objects. Since this was working previously my current hypothesis is that one (or more) object type has changed its structure that the XPath is no longer correct.
As an interim you can (as I have just done) cancel any failed process instances as this then allows the analysis process to proceed on the remaining objects. In my example I am cancelling 34 out of 2000 objects, which means I can still successfully analyze >98% of the objects. Given that it's all about risk, then if you're prepared to accept that you don't have automated insight into those that are failing you could still manually examine those if you are risk averse.
I'll come back with an update when I determine the root cause of the error.
Stewart
If you just updated like we had done it seems that the file structure of the patch has changed. I made some changes to AQA_ER_getPatchObjects and we were back up running.
fn!reject( fn!isnull, a!forEach( items: ri!patchContent, expression: if( and( contains( rule!AQA_ER_allObjectFileExtensions(), document( fv!item, "extension" ) ), /*file not called patches*/ document(fv!item,"name")<>"patches.xml" ) , fv!item, null ) ) )
even we are getting this error, Appian AppMarket Appian CommunityAppian Internal CST/CSE Developer User Group, please resolve this issue as soon as possible, we are not able to use Aquaman
AQA_ER_getObjectAttributeValueByAttributeName--its failing here in this rule, every time, we run a patch
I got this error while analyzing patches with individual objects. The patch contained one expression rule only.
in the expression AQA_ER_findNumberOfBatches,
local!numObjects: count(pv!patchObjects) needs to be changed to
local!numObjects: count(ri!patchObjects)
We just updated to 21.2 and have started having issues when trying to "Analyze Patch" We are getting the following;
: 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) (Data Inputs)
Started to setup Applications and found a bug. When Registering an application "Test Fail Override For Unused Variables" has a dropdown item of Information, but when if/when you need to update the application, Information is not in the dropdown list in the AQA_if_application interface.