I’m modelling a module that contains a tree which shows a hierarchy of several entities.
Besides the hierachical tree perspective, there is also for every entity a dedicated module with an overview of that entity.
Requirement
Whenever I click an entity, either in the tree or in one of the overview pages, a detail form must open that shows the entity’s information.
Depending on the context (tree vs. overview) the form has to display different content, so I have two different forms for the entity.
I want to be able to model multiple trees for the same entities, so that I can show the information in different ways to different user groups.
Problem
When I open the tree “overview”, based on my definition of activity descriptors in the module in the app model, an engine, model and module name are set.
When I click an entity in the tree, those descriptors get lost. There is only the descriptor for the model and the instance given.
Therefore the match-condition for the detailed form no longer works the same way it does when the entity is opened from the overview module (here the respective activity descriptors are kept); the scene description is no longer unique.
For one tree in my application I can work around that behaviour. If I added a second tree that shows exactly the same data (e.g. a read-only tree), I could not tell which detail form should be loaded because the descriptors coming from the module are missing.
Question
Is this behaviour a bug or is it intended?
If it is intended, how can I model two different detail forms for the same entity that are opened from two different trees?
.