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
The last list item for Key Features and Functionality indicates a test is performed for missing accessibilityText parameter values. Note that no one should be relying on this test (the labels test is valid). Just because a component does not have accessibility text does not mean it fails any a11y requirement. In fact, accessibility text should not need to be used in most cases. It should only be used to provide additional information to non-sighted users. However, the need to do so is based on context. If you design your content correctly, accessibility text should never be needed. In cases where you may believe it IS needed, then you should consider redesigning your content so the information is available to all users, not just non-sighted users. The accessibilityText parameter is one of the most overused of Appian component parameters. In most cases where it is used, it either creates redundancy or confusion for users who rely on a screen reader. The parameter name is misleading because its use does not necessarily make content accessible or even "more accessible".
Hi, can you please adapt scripts from Maria DB to Oracle and/or other DBs as well? GPT isn't quite able to adapt it yet
Hi
The referenced plug-in is this one: https://community.appian.com/b/appmarket/posts/text-file-reader
Okay Thanks..
Just to clarify - the fix worked in the environment where an existing instance of AQuAMan was running so it's not an (AQuAMan) application issue.
Regarding support for MSSQL - apologies, I do not have the scripts for any other DB other than MariaDB.
Hello Stewart Burchell ,
Thanks for the update, recently we upgraded or local environment from 22.3 to 23.3 Appian Version. As checked with appian support team, they mention that the XPATH fix is part of the new version.
However, I am still getting the issue. Raised a Appian Support case to look that is it platform issue or Application?
Also, as I am installing Application in our local environment, and we have MSSQL DB. Can you please provide the scripts in MSSQL as well?
Thanks
Apologies for the delay in relying, I've been out of the office.
I don't have a reference to the hotfix specifically but I do have a reference to a separate support case that you can mention: "612282 - Please make an incident for Xpath broken"
This should provide enough context for your support engineer to apply the relevant fix.
regards
Stewart
Hello Team,
Can you please share the link to download "Text File Utilities 2.0"? I am little confuse between Text utilities and Text File there are 2 different plugin in App Market? and both them are not in 2.0 version.
SUshil Kapoor
Can you please let us know the hotfix name or number which is required to deploy in on premises server to fix the
fn!xpathdocument() ?
Sushil kapoor