Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

BaSyx / Documentation / Components / AAS Web UI / Features / Status Error

Status Checks and Error Handling

User Story and & Use Case

As AAS Web UI user

I want to see if the Asset Administration Shells registered in the AAS Registry are available.

I also want to know if an error occurred during the use of the AAS Web UI and what caused the error.

The UI provides a feature to periodically check the status of the Asset Administration Shells registered in the AAS Registry. The status of the Asset Administration Shells is displayed in the AAS List on the left side of the application. If an error occurs during the use of the AAS Web UI, the user is informed about the error and the cause of the error.

Feature Overview

If an Asset Administration Shell or a Submodel is not available, the user is informed about the isse through a status indicator in the AAS List on the left side of the application. The indicator can automatically appear/disappear when the periodic status check discovers a change in the status of the Asset Administration Shells or Submodels. The user can also manually trigger the status check by clicking on the refresh button in the AAS List. The periodical check is performed every 60 seconds.

Status Indicator

If an error occurs during the use of the AAS Web UI, the user is informed about the error and the error message is displayed in a red snackbar at the top of the application. The snackbar will dissapear after 60 seconds or if the user clicks on the close button. The snackbar will also display network errors.

Snackbar

Back to the top