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
I do not understand what you are looking for ...
Hello, i was curious if there is any documentation on appian, i am trying to dynamically link another apps record type to it so that my apps record type automatically sends data to it to ease onboarding. any ideas?
is execute stored procedure still a required plugin as it is deprecated on the Appmarket?
Per my observation, there are two issues
1. Appian function `document()` returns the filename without extension for `name` attribute - check on line 7 (AQA_ER_getPatchMetadata)
document(fv!item,"name")=cons!AQA_TEXT_MANIFEST_NAME
will never match the manifest file from the patch because
2. the constant AQA_TEXT_MANIFEST_NAME has by default the full filename as value (MANIFEST.MF). Hence, the local variable `local!manifest` will remain empty. This leads to
3. local variable `local!manifestContent` will initialize as list of strings (because the manifest file seems not present in the patch), not as a single string (as it is done by the readtextfromfile() function)
4. function `fn!keyval()` expects a single string, not a list of strings. In this case, it receives a list of strings and will never return the expected value (Created-On), but null instead
This causes the error described above.
Stewart Burchell Would you please consider looking at this and fixing it in the source code?
Thanks!
Hi Stewart Burchell , 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