Main Region

Correct way to reuse tabs using content loader via grid context query (FXP-2732)
| | 1 answers | 15 views

AL
Posted by Alex
Dec 24th, 2016 at 03:16
0

We have a content loader that needs to access specific tabs on our master page. In previous versions of FOEX, we would specify something like "tabId":"SHARE1" in the "custom" column of the grid context query and then use a set items DA with a javascript expression like

this.data.menuItem.tabId

to transfer the value to a page item, which would go into the Shared Id part of the Content Loader, ie

#P5000_SHARED_TAB_NAME#

with the overall content loader setup like so:

alt text

The latest version of FOEX does no longer allow that. It seems this is due to the introduction of the fxTitle functionality - when we tested the contents of the data

alert(JSON.stringify(this.data.menuItem));

"custom" only showed data when the key was "fxTitle", otherwise "custom" would not be shown at all as part of this.data.menuItem.

What is the correct way to handle this? We can't use fxTitle, as this overrides the triggering element text, which we like as a heading for our new tab. We've also tried group_id as mentioned in the grid documentation; however this also did not show up in this.data.menuItem, nor did it have a difference on being able to hit the correct tab. What's the correct way of dealing with this?

1 Comment

AL
Alex on Feb 1st, 2017 at 12:50

We had strange behaviour with the old method after trying to hit the same tab a second time, the page got caught in a small iframe. The group_id method however worked fine.

Profile Image
Posted by FOEX-SUPPORT
Jan 2nd, 2017 at 15:05
0

It seems that you have uncovered a problem that the group_id defined in the context menu query is not being used correctly.

The behaviour should be: when using "group_id" in your context menu query you do not need to set the "Share/Reuse Tab/Panel/Slice" and "Shared ID" settings. The tab will be automatically opened in a shared/group tab.

We will be supplying a fix in the next hot fix release due out soon.

Note: with the supplied fix you will also still be able to use your design as above, but it just adds more overhead when you can simply use the menu SQL group_id column to define the groups.

0 Comments

You must log in or sign up to post questions and answers.