Skip to content

Option to suppress warnings when whitelisted applications are not found #1401

@chrisswan-rm

Description

@chrisswan-rm

Is your feature request related to a problem? Please describe.
When you whitelist applications (e.g. screen readers) to make them available for use during an exam, SEB always checks that they all exist upon startup and shows an error message for each one if it can't be found. We have clients who want to whitelist a number of applications that students may use (e.g. a selection of 5 approved screen readers), but it is not mandatory that they have them all installed (and they likely won't, as normally the school would just install a single preferred one). In this scenario, the experience of launching SEB is not optimal, because they have to click "OK" to a number of error messages for the applications that were not found.

Describe the solution you'd like
I think this would be a pretty straightforward enhancement, e.g.

  • A new Boolean configurable setting to decide whether to show a warning or not (e.g. in the config tool it could be an extra "Warn if not found" property against each application, alongside the existing "Icon in taskbar", "Autostart" etc. properties) - could be set to true by default to mimic existing behaviour, but the checkbox could be unticked to disable it.
  • Where the new setting is set to false, suppress the message about the application not being available (e.g. via a simple code change in the InformAboutFailedApplicationInitialization method in SafeExamBrowser.Client/Operations/ApplicationOperation.cs).

Describe alternatives you've considered
You could create different SEB configs depending on which application(s) a student wants to use, but this is complicated as you then have to deal with lots of different config files (and associated configuration keys / browser exam keys). It would be much easier to just use a single config file with all allowed applications whitelisted, and be able to configure SEB to not show errors for the ones that don't exist.


As originally reported under #1397.

Metadata

Metadata

Assignees

Labels

enhancementThis issue proposes an enhancement of the software.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions