Home Original page

Implement Package Detection for Accessibility Integration with Userway by sanjacornelius · Pull Request #6866 · ProcessMaker/processmaker

Issue & Reproduction Steps

This PR implements detection for the accessibility package and integrates UserWay when the package is installed. The integration includes loading the appropriate scripts to display the UserWay accessibility icon on all pages, including the login page. If the accessibility package is uninstalled, the UserWay icon will no longer be displayed.

Solution

  • Add a check for the accessibility package.
  • Include UserWay scripts if the accessibility package is detected.

ci:next

How to Test

Test Case A: Verifying UserWay Integration

  1. Ensure you have a UserWay account configured.
  2. Ensure the accessibility package is installed.
  3. Install the accessibility package if not already installed.
  4. Navigate to any page within the application, including the login page.
  5. The UserWay accessibility icon should be visible on all pages.

Test Case B: Verifying UserWay Icon Removal

  1. Ensure the UserWay account is configured.
  2. Uninstall the accessibility package if not already.
  3. Navigate to any page within the application, including the login page.
  4. The UserWay accessibility icon should no longer be visible on any pages.

Related Tickets & Packages

Code Review Checklist

  • I have pulled this code locally and tested it on my instance, along with any associated packages.
  • This code adheres to ProcessMaker Coding Guidelines.
  • This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
  • This solution fixes the bug reported in the original ticket.
  • This solution does not alter the expected output of a component in a way that would break existing Processes.
  • This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
  • This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
  • This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
  • This ticket conforms to the PRD associated with this part of ProcessMaker.