One idea I have is to use 2 ProcessBook instances instead of only one. This way you can make use of 2 ERDs.
The "tricky" part then is to pass the new path, when clicked, to the other PB instance so you can change it. I was thinking of the DDE protocol, but I dont know if this is available for PB.
A very basic ( not sexy ) method would be to poll a file or a database, that would work for sure.
This method would have the advantage of sticking with mostly basic functionalities, as you were requesting super users to be in best position to manage the displays.
Hope this helps and I am curious to see what you end up with!
1 of 1 people found this helpful
Maybe you've already checked this approach: you are able to read an attribute on a child parent E..\ChildAttribute|AttributeName.
You can also create an additional AF architecture/view (using reference elements) and put the region element under each substation. Just an idea…
Thanks for the input! Given the time allotted for this job I had to simplify it, but the solution is still good.
Instead of using the ERD menu for the regions, and a secondary context for the substation display part, I let the substation be the element of interest and create buttons for navigating between the few region displays. There's only four regions (= not too much copy/paste work) so it's manageable.
To get my list of substations directly in the display I use a grid component, which also shows traffic light style KPI's. This list is clickable and changes the context of the display, meaning I can hide the ERD menu to get more screen real-estate.
But I like your tip on getting attributes from children/parent elements using the E.-notation, Gael. I haven't used that before, actually!