I used the Accordion and MenuTree to create the navigation it is working as expected as shown in the image.
- The accordion toggle to different areas.
- Pick the right subsystem under an area
- is the landing page.
However there was one request I could not figure out. the request is when user click on production area. They want to see a system overview page in the landing area.
Accordion header.content.type is set as text, changing it to view messes up the navigation on the left because it starts showing embedded view in the left menu.
On click on the production area, accordion expansion works great, with the same click is it possible to open a desired overview page in the landing area?
Thank you for your help
To get a target to show for ① I expect that you would specify the target URL in items.1.target. If that doesn't work then paste your MenuTree JSON here on the forum. See Wiki - how to post code on this forum and if you can keep the post very tidy by using the Hide Details option.
@Transistor, I believe the OP is using the Accordion component here, so the target property will not exist for them.
If this is the case the accordion has a configurable event onItemExpanded that would allow you to configure a Script action. In this script I would grab the item index from the event.index parameter and add some logic that will navigate the user to the correct page based on the item clicked using the system.perspective.navigate function.
1 Like
@rperretta I tried this and it appears to work. One thing I did not like I had to add script to individual item.expanded property.
Is there a better way to achieve this. Read items[i].expanded values and assign landing pages in one place.
-
- home
-
- mix
-
- production
-
- utilities
- etc etc,
Yes.
Right click on the accordion component and click the the Configure Events option in that menu.
Then select the event shown below, click the plus icon, and select Script. Anything you write in that script will fire whenever an item in that accordion is expanded.
You would still have to hard-code some logic to check which item was expanded in that script (using event.index to get the expanded item), but it would allow for a single script to be utilized. You could also name the menu items and views in such a way that you could use the menu item to derive the view path name and ditch the if's.
I would say it makes a bit more sense to simply have an Overview submenu item where needed, as it does not make sense intuitively for the accordion header to perform a navigation. But if this is necessary, that is how I would go about it.
@rperretta,
Thank you for the suggestion to make it truly dynamic.
it worked like a charm, all I had to do was make the naming consistent and it worked with one click event.
I agree that Accordion was to show the areas of the plant and its sub systems. However it is human urge to keep the old functionality as long as possible even after the upgrades
