Dynamic template connection with index for open page - #2508
Draft
kjellMenu wants to merge 1 commit into
Draft
Conversation
kjellMenu
marked this pull request as ready for review
August 10, 2026 13:13
kjellMenu
marked this pull request as draft
August 10, 2026 13:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 Description
Please describe the changes introduced by this Pull Request.
What problem does this solve?
It addresses the scalability issue when working with User Defined Types (UDTs) and indexed tags (e.g.,
UDT Veld.Motor[0],UDT Veld.Motor[1]) from a single (OPC UA) connection. Currently, FUXA requires manual placeholder coupling or creating separate target devices for every single instance, which becomes inefficient in large-scale environments. This solution introduces a proof of concept to dynamically bind structured tag names to a single Template screen upon page navigation.*This Draft PR was created in response to the discussion thread Best practices for scalable UDTs and Template Screens with OPC UA? #2476
What was changed?
The frontend runtime component (
client/src/app/fuxa-view/fuxa-view.component.ts) was modified to intercept and resolve structured tag paths dynamically when a page loads.applyIndexedTagMapping()was added to strip a temporary@validation token, read the target index, and resolve the string name.Indexduring theloadPage()command to trigger the resolution.Why is this needed?
This functionality eliminates the need to manually assign every single tag to a template screen. When working with a single PLC tag connection, it allows you to dynamically handle hundreds of identical template screens (like motors or valves) via text-based mapping, significantly reducing engineering configuration overhead and improving project scalability.
🧪 Type of Change
Please mark the relevant option:
🚫 Build Artifacts Check
Please confirm:
/client/dist