Hi guys,
when you do share in Classic view it does http://****/llisapi.dll/open/20172301 which opens the file and opens a web page that the contains the file. is it possible to set the same on the smart UI Share. if so how do you do it?
thanks,
Dayan.S
You can open the same node in Smart UI by http://****/llisapi.dll/app/nodes/20172301.
The "Share" button in Smart UI shows you that URL.
Classic UI does not provide a button to get Smart UI URL and vice versa. We have not finished the discussion, how to consolidate different CS URLs between Smart and Classic UIs and how to allow you choose, which one you prefer.
Hi there, this topic has gotten some interest with a preference from customers to have the smart UI share link be a direct document open rather than the overview page. Is there an interim solution, or via some Smart UI SDK option?
You could use the CS UI SDK to introduce a custom action, which would work similarly like the existing "Share" and generate URLs like:
I would not recommend this. I would ask OpenText for making the document page more useful. Smart UI has a concept of pages specific to any object type. The object types should use this customizability to offer the best view of the object.
Technically, I am afraid, that there is no way to make the /app/node/:id URL download the content instead of open the Smart UI page for it in the existing product.
The most often complaint about the document page is, that the document overview widget there is not useful, because you need to see the document content, when you open a document page. On the other hand, sometimes you want to see document properties, go to the parent folder etc.
We would like to improve the current page to be more useful by showing a quick full-page viewer there, offering other actions on a toolbar.
Would you still need to open/downlaod the documebnt content, if the document page were more useful?
Always thought that the row of promoted commands or the current inline action commands in the document overview page would make it much more valuable. Then maybe something like a popup viewer of the document that didn't require launching the authoring application.
Most of the organisations I've worked with have had the same opinion, though most, sadly, don't see the point of putting in a feature request.
For the current project I'm working on we've added another command/button to add the URL for the overview page to the clipboard, rather than opening it in an email. The user can then paste that link into whatever makes sense, an existing email, a document, etc. I've never found the opening a new email with the link in it fits the users use cases very well (and thankfully most of the browsers now have a decent method for adding currently selected text to the clipboard).
I am afraid, that the document overview widget is not extensible. You can add buttons or custom menu items executing your command to the browse table and metadata widgets.
Yes, usefullness of the document overview widget has been questioned. I would like to see a full-page document preview with a toolbar tor actions, which would cover the quick viewing scenario and give more sence to the page. But nothing has been planned.
The command "Copy Link" copying to clipboard the externally accessible URL of the selected node will be added in CS 16.2.3 in December.
