Best Of

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…

@GregPetti gave you the right way, I misread your post as it was working in one environment vs another, so ignore mine 😊

The RUNSQL sub-tag is returning a "RECARRAY" which is to say an array of records. Even if you only expect one row, you will have to index it. E.g..

[LL_REPTAG_$LiveReport_GetKUAFID RUNSQL RECARRAY:1:ID /]

or

[LL_REPTAG_$LiveReport_GetKUAFID RUNSQL RECARRAY:1 RECORD:ID /]

If you have more than one row, you can use the [LL_WEBREPORT_FOR tag to loop through them and an LL_WEBREPORT_IF tag to screen out the rows you don't want.

Cheers

Greg

I should note that there are better ways to do this besides RUNSQL (this sub-tag is often disabled on customer systems as it is disabled by default).

If all you need to do is return a column from a SQL query that returns one row you could associate the LiveReport as a datasource and the use

[LL_WEBREPORT_DATASOURCE /]

which basically does the same thing. Or (assuming only one row is returned) just put a line like this in a row section like this:

[LL_WEBREPORT_STARTROW /][LL_REPTAG=ID /][LL_WEBREPORT_ENDROW /]

This automatically loops through the rows so you get row #1 automatically and the =ID tag looks up the ID column.

Greg