In short, use the app as any customer normally would – all the usual elements such as searching for products, browsing information pages etc., but the primary focus should be on the My Account section, which you should land on immediately after logging in. We’re looking for anything that blatantly breaks, and as such I’ve installed logging utilities throughout the app that capture and document events. I ask that you try to avoid a screen-by-screen comparison against the original MyALICLE, as things are intentionally different by design (so things like search results not appearing in the exact same order do not constitute actual issues). As well, certain portions of the original MyALICLE website were not ported to this app, including:
the “apps” portion of the homepage; in the interest of simplicity the My Account home is the same for all users. The information on those app panels is readily available in other areas of the app.
“Tell Us More”; I saw no reason to keep this in but if it is deemed essential it can be returned
“New from ALI CLE”; since users remain in the main app this section is redundant
CLE Content/Library Unified Search
There was some confusion during the last discussion regarding the library layout, as some people were momentarily confused by the lack of filters atop the library page. I believe this is simply unfamiliarity when used to a particular layout, so please try to think of the CLE Content/Library layouts exactly as you would a CLE/publication search in the main portion of the app – because that’s exactly what it is. Every search in the app uses the same search layout with relevant filters being added and removed from the left-hand column as search contexts change, just like in CLE search. In the case of these searches, we’re looking for things like:
links that don’t work
buttons that do nothing
data that doesn’t display correctly, etc.
The actual data queries will be reviewed by other members of the tech team.
Changes in Navigation/User Experience
CLE Center is no longer a dual-purpose page for both search results and individual programs (e.g. clicking “View in CLE Center” from an on-demand program in the library – as seen in previous demonstrations, each program has its own overview page (regardless of program type or status) as each program is easily accessible from its own URL (e.g. ali-cle.org/user/cle/1175196) and from there users can elect to begin/resume a program, take the evaluation, apply for CLE, etc.
“Subscriptions” is no longer a separate page, but a panel now at the bottom of the My Account page. Functionality remains the same, with the title of the subscription being a link to the available issues in said subscription.
Testing Tips
The browser console is your best friend – it allows you to look under the hood and see if the page, especially its scripts, is having issues. You open your console in every major browser by pressing CTRL+SHIFT+I (or Command+Option+I for macOS). If you’re not familiar with what you’re looking at, that’s okay; the simplest thing to look for will be very easy to spot – JavaScript errors appear in red boxes of text in the console. If you see an error in the console it still may not be indicative of a problem, console errors happen all the time and we’re looking for anything that specifically breaks the app. If you’re unsure, please don’t hesitate to reach out and ask and we’ll be happy to provide guidance.
What’s New
First attempt at WCAG accessibility patches (to no longer need UsableNet).
Multiple new compatibility/fallback procedures for fullscreen viewing (as specs and support unfortunately keep changing).
Prompt server auto-backup and restore for potential server issues.
Post-program evaluation is now two pages, with first page being entirely optional (as well, two questions have changed).
Player now has floating unmute button when live programs are joined without user interaction (sits in middle of video, disappears when clicked).
Search variables renamed to better handle bots hitting our pre-render, returning search results instead of errors.
New category-based WordPress content pages which can automatically display upcoming programs rather than manual updates.
New York state “cyber credits” have been added.
Overall HTML cleanup for better search-engine/automated consumption (e.g. use of semantic-web terms like <main> instead of just <div>).
Cleanup of UI for coursebook subscription page.
An automated/cleanup method now prevents browser mixed-content warnings by rewriting any content (e.g. course detail) that may have insecure HTTP links.
Program attendance now has a rudimentary scoring system, which can disallow credit-application.
Certificate files are served as auto-filled PDF files where applicable (if PDF file is present on server), traditional HTML if not – with no interaction required from the user.
User homepage has been restyled according to feedback; subscription panel is now deprioritized at the bottom.
Admin dashboard and all other admin functions (e.g. program control) now sit in their own menu in the main navigation rather than a floating button.
Player now supports rudimentary elements of browser/system notifications and Web Workers (as a future element to better user experience and increase visibility of prompts and other messages).
Most deprecated references to specific AngularJS functions (e.g. $http) have been replaced with their more modern standard-JavaScript equivalents to ensure reliability.
The CLE Content and Library sections have been further separated, with the Library only displaying non-CLE content (e.g. coursebooks, purchased periodicals, etc.). My belief was that as we offer fewer and fewer publication products the line between CLE and non-CLE content will be less relevant, but for now I welcome feedback regarding the change.
When you log into the existing MyALICLE using Wanda Webcast, your library contains links for coursebooks and on-demand courses – the new library contains filters for all non-CLE items regardless of whether a user has purchased anything of that particular type, and I believe that was causing some confusion.
Attendance Scoring Formula
The program length (50/60 minutes, other, I need clarification) is determined by checking the base length in the state we use for comparing general certificate data, CA. The number of prompts clicked is tallied, then multiplied by the prompt interval (defaulted to 15 minutes), then divided by the length like so: ((promptCount * interval) / programlength) So for example if a person clicked three prompts in a 60-minute program: ((3 * 15) / 60 = .75 * 100) = 75%, a passing score.
Options/Future Planning
Passing threshold can be set across the board (e.g. 50%), or it is recommended to put a column in the MCLE state table if it needs to vary by state. As well, if states require custom formulae for more complicated situations (e.g. probably New York) we can simply build it as an included code file and isolate that grading system solely for that state.