So today's challenge needs to be run through some extra heads before I start testing:
A client in the T&D industry has two 55" full HD screens where they want to display one or more ProcessBook displays. The solution involves using the ERD menu to select the context for the initial display, let's call this regions of a country. Once the region display has been opened they want to list the status of all their substation with color coding, and this is easy - I've put that in place with a grid component. But once they click the stations in that list they want to open the substation detail display in screen number 2.
So I'm pondering how to implement this. I know that the ERD system only handles one context at a time, but I also know I can implement my own context handlers using VBA code. The question is whether or not this'll help me. I want end users (well, super users at least) to be able to keep editing my display, using some sort of known syntax when they add more attributes to their display.
What would it take to get something like this working?
If I want to keep using the E.AttributeName syntax I'd be stuck with the original context of the region display, and not the substation context I need. I could set it programmatically, because all previous experience doing that is that the ERD add-in does not reflect these changes.
An alternative could be to implement all value symbols using their actual attribute name in AF, and then programatically update the value configuration using the context (from my grid component) + the attribute name. (Ex: AF2.\\AFServer\database\path\to\element|AttributeName)
Another alternative: the E in E.AttributeName seems to be implemented as a dataset in ProcessBook. I've previously written a RegressionLine dataset addin, so I'm somewhat familiar with doing that. I could implement my own E2 dataset, which handles a secondary element of interest for these few displays.
Would be interested in any feedback!