Hello,
When we access a webreport in Classic, the page will redirect to the webreport, but in Smart UI, the webreport is always opened in a new tab. Is there a Smart UI setting to open webreports without creating a new tab?
Thanks,
Ji
This is just the default Smart UI behaviour for opening a node type that has no corresponding Smart UI action. I don't think it's configurable.
In 16.2 Smart UI support was added for a number of WebReport destinations. There is also a parameter prompt screen that shows a Smart UI form to take user input. Support hasn't been added for the 'browser' and 'destop' destinations or a Smart UI equivalent yet. Showing custom WebReports content in the Smart UI can only currently be done using a custom perspective which loads Content Inteligence widgets. What content were you wanting to show?
RegardsIan
Hi Ian, thanks for the reply.
The webreport loads a custom UI for the user to enter data and copy a folder template. Currently, the form is accessed using a webreport shortcut that's a featured item in Classic view. When using this webreport link in Smart UI, everything still works appropriately, except opening the webreport in a new tab. We were hoping the user navigation could be the same in both classic and smart views so that the process flow could be what users are used to. If we were to use a custom WR tile to perform the same functionality, would there be a way to hide/show items for the user in the repository view based on whether they're using smart or classic UI?
It appears, fhat the WebReport opens in Classic UI. All Classic UI pages open in a new window by design. Smaty UI cannot save user context of the current poage (tab, sorting, pagination etc.) and that is why any "foreign" page opens in a new window.
There is a configuration property to force Classic UI pages open in the same window. But it is usable only on custom pages embedding Smart UI, not on the CS built-in /app, because there is no administration page to change the default value.
Smart UI should be able to save the user context by using URL routing and browser history more, than today. This improvement could happen in June 2019.
