-
Notifications
You must be signed in to change notification settings - Fork 96
Stepped Tracker previous steps as links #1868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@ivan-calderon @tomhazledine @jake-costa |
Latte Goal: @jake-costa review any accessibility concerns, docs review by @ivan-calderon |
A11y comments added to Stepped Tracker Figma Specs. @ivan-calderon Ready for review |
Lungo Goal: No dev capacity |
Macc Goal: |
To be scheduled after feedback on Stepped Tracker labs release. Pushing back to backlog. |
The Stepped Tracker is being used in the Salt Migration pf Trade Processing Systems - image exported from Figma is included - also included is the an exported image of the existing TPS system that is built in Google Web Toolkit and has all the characteristics of an old Windows Application. Critique from Ops representative Saiprasad Nimale on current system: " No free navigation for Maker, Maker required to click Next button to travel to next screen - 15 screens required to be travers by clicking Next button only." @chrispcode - FYI - you seemed interested in the 'why' and use case yesterday - user commentary above. |
(Couldn't upload images so linking to Confluence page with them on) |
Spoke with @mike-gray-pxd who will provide some more detailed requirements and edge cases for forward/back navigation within the stepper. |
Hi @bhoppers2008 - I added some notes to the images in the Confluence page above. "Transaction processing is a '4 eyes' process where a maker's work is checked by a 'checker'. For both roles - but particularly the checker role - there is an operational need to navigate the steps non-linearly. |
The text was updated successfully, but these errors were encountered: