I’m having trouble finding out if it’s possible to actually set which of the regions that will be open when a new interaction pops up. The only thing I found is the views.CaseViewSideButtonRegion.order option that only allows me to change the order of the tabs, not which one who should have focus.
Is this possible with options and if not is it possible with custom code?
Well I’m not sure about that. I see you can use the .active-order option for other regions that will select the first in the defined list.
But active-order does not exist for views.CaseViewSideButtonRegion or views.ToolbarWorksheetButtonRegion, I’m thinking that active-order was the default functionality you where referring to?
I think, you want to open a specific caseview with any next interaction - this should be easily configured on WDE level (on application object level or higher agent, agent groups, etc.),because of the WDE is storing information about latest window and caseview composite. So, if you run WDE for first time and arrange your windows/caseview as you want, with each next login the arrange will be always same.
So easy, why reinvent the wheel…
Yes ok, I see your point now. Though I have another problem with that, in our test environment this works, all is saved in the agents Annex as expected but not in production. Even though have checked all options for this that I can think of. Any clues to why this is?
This must be allowed on WDE level (option options.record-option-locally-only) and of course the agents must have write permission on own agent objects.
Do you find how to focus ?
WDE focuses on the last tab opened in the previous interaction
I need to focus always on my custom tab, regardless the previous one
Thus, how to desactivate the last-information-panel process ?
That. As petitspirou said, our WDE works on that way, opening last tab on the previous interaction.
You can try to work launching and event on load like the button “splitToggleButton” of the views (if you work with customized view, i supose you have one) works whenever you click on it.
See the interaction example on WDE samples, but must be something like:
Actually the problem is the following. My custom view loads a CRM page and it takes sometimes severals seconds
If I can start loading the CRM before the tab is selected, it could be ok