Try the following:
1. Create an ontology, include the EDG schema you will be configuring e.g., EDG Enterprise Assets
2. Create Node Shapes for each of the classes which instances you want to show in the asset hierarchy in a custom way
For example Business Function View1, Business Activity View1, etc. These would be node shapes only, not classes. Set their “applicable to class” values to the appropriate classes which instances you want to show e.g., Business Function, Business Activity, etc
3. For each of the Node Shapes, copy from the applicable classes property shapes only for the relationships you want to show in this hierarchical view
So, let’s say you do not want “types” to show, don’t copy it. You don’t want a connection from the activity to the function to show, don’t copy it. You also don’t need to copy any shapes for the literal values since they do not play into this view - except for rdfs:label.
For the relationships that you do copy, change the sh:class constraint to the sh:node constraint pointing to the corresponding Node Shape
4. Make these node shapes “public” by clicking on the home button and updating the GraphQL view of the ontology
5. Include this new ontology into the enterprise asset collection with your functions and activities
I am between releases right now, so I can’t say that I have tested this fully. But it should work.