-
Notifications
You must be signed in to change notification settings - Fork 18
Description
Describe the bug
When using the AAS Web GUI (version v2-250417, running in Docker) with Discovery integration enabled, the "Jump" buttons on entity elements correctly appear and are clickable.
However, after clicking a jump button and navigating to the shell view, if the user then goes back in the browser (e.g., using the browser back button) and tries to click a different jump button, nothing happens. The navigation does not occur again unless the page is refreshed.
To Reproduce
Steps to reproduce the behavior:
Open the AAS Web GUI and navigate to a Submodel/Entity view where jump buttons are available.
Click a jump button – this navigates to the corresponding Asset Administration Shell view.
Use the browser's back button to return to the previous Entity view.
Click another (different) jump button.
✅ Expected: it should navigate to the new shell view.
❌ Actual: nothing happens unless the page is manually reloaded first.
Expected behavior
Clicking a second jump button after navigating back should also trigger a jump to the corresponding shell view.
Environment
AAS Web GUI version: v2-250417 (Docker)
Browser: [Chrome]
Discovery integration: ✅ enabled
Possible cause
This may be due to client-side routing (e.g., React Router) not recognizing the navigation as a route change, since the target route path might appear identical or the component is not reloaded.
Suggestions
Using unique query parameters or forcing a component update could potentially resolve this
Metadata
Metadata
Assignees
Labels
Type
Projects
Status