Best Of

We have built an entire UI for Content Server (with easy handoffs to Classic and SmartView) using VUE (just upgraded to VUE3). This allows us to deploy a variety of features and in fact it provides a unique IDE for WebReports development and support (among many other things - including some Workflow specific features). That said, we have other products that are just developed using raw HTML and JavaScript within the existing Classic interface, and we have another product that extends the existing SmartView interface for developers. My point (besides taking a moment to talk about our products :-) ) is that there is no one perfect approach. You can build a full blown-unique UI as we have done and benefit from all of the great, robust, powerful functionality that CS provides below the surface. I think we had a video on how to build something like this at some point, but I can say that we tend to use WebReports to serve our VUE client. We could use REST requests, but many of the specialized, proprietary functions we provide do not exist in the REST API. Also some REST request do more than we need, or less than we need, resulting in extra complexity, and or lower performance. What we do instead, is to create WebReports that can access CS functionality through the TAG/Sub-tag interface. We get whatever information we need, fine tuned to our exact purpose, and then we have the WebReport return data in a pre-defined JSON format. Our client is designed to expect this JSON format. So as an example, you might click on a menu option in the VUE client, it sends a request (could be REST or Classic) to run a WebReport, the WebReport could perform a task, and then send back a JSON response something like this:

{"error":false,"data":"your action was successully completed, 10 items updated.","errorMsg":""}

The client code is designed to parse this and maybe pop up a message that shows the response.

I should add that we have created this VUE framework to be reusable for all of our products by defining the schema that it uses and expects.

Cheers

Greg

To me, it looks like there's an element of re-invention of the "wheel" here. Marketing hype aside, I will just mention the coding aspects.

1. https://developer.opentext.com/apis and Find Cloud in there, and you are looking for Content Management
2. Your screencap shows a Business Object, or in other words, a Workspace Object, a.k.a Extended ECM for <nnnnn> that <nnnn> could be anything. Usually, you will find nnn as {SAP, Maximo, Success Factors, Sales Force, Microsoft Dynamics, Service Now (??), Extended ECM for Anything by Answer Modules and ad infinitum….}
3. Each of those folder-looking Objects has a GUId(Dataid) locator, so if you execute an API and say ListObjects, it will be akin to select * from DTREE where Parentid=12345.
4. Since it is a workspace object, everything underneath that is like select * from DTREE where Ownerid=12345)
5. Livelink, a.k.a Content Server, is the engine powering this, so they keep the objects with a subtype mechanism, but you dont need to know all of that deeply, Suffice to say that all Document Objects in livelink have the same subtype, aka 144, so if you locate a Document Object by hovering over its link you will see a number n your screencap 39184 is the dataid. One could use an api and ask What art thou? And it will say workspace. So if you have a document, the rest api has enough methods to "FETCH" your document.
6. So all you now have to do is somehow use the api of Service Now and put it however you want.This is one api that could get you what you want

PS: Service Now has an integration available, so if you connect it properly, you do not have to re-invent the wheel.

If you do have that integration, then you have to just expose that view you see here and not duplicate that, so in service now, you could show that view in your screencap. OT has made integration widgets,that is what we do with our product in Maximo and others in the respective UI's. If it is a native document in service now and you want that brought over to OTCS, look under attachment declarations and scheduled tasks…