Uploaded image for project: 'Fidelis AI'
  1. Fidelis AI
  2. FAI-333

Score Cards: Validation implementation

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major

      So, once we've identified what it is we need to validate we can set about implementing it!

      We should consider the 10 Usability Heuristics for User Interface Design as they relate to validation.

      These suggest:-

      #1 Visibility of system status
      #9 Help users recognize, diagnose, and recover from errors

      We should show an indicator beside sections containing invalid data to allow the User to identify problematic areas in the model from the top-level page/screen and drill down further to the point of error.

      #5 Error prevention

      We should endeavour to prevent Users from making mistake where possible.

      We should engage with the kogito-ui and kogito-tooling teams to discuss, propose and agree standards for "kogito editors" and what provision we can expect (or demand!) from the channel itself vs editor (e.g. if we show a list of validation errors this could possibly be supported by integrating with VSCode).

      Should validation errors be persisted or identified "on open"? (or other triggers)

      This JIRA is a placeholder.

              manstis@redhat.com Michael Anstis
              manstis@redhat.com Michael Anstis
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: