Create a new version of a category programmatically

Alabasta · 2021-09-29T15:38:41+00:00

There was an error rendering this rich post.

Hi All,

I'm trying to write some code to update the list of attributes inside an existing category.

Is it possible change programmatically a category (via REST API, Content Script o via LAPI) to add or remove an attribute?

Thanks in advance for your help.

Cristoforo

Find more posts tagged with

Comments

Appu Nair

LAPI is deprecated no one uses it. Version 16 of the CS server removes the LAPI endpoints in Oscript.if your server supports it Lapi can do the trick.

Category Definitions can be changed via SOAP(CWS) Preferred

Categories that usually get applied on Objects(like Folders, Documents) can be manipulated via REST/SOAP/WR/OSCRIPT/Content Script(answer Modules).REST can create a Category but no attributes last time I checked so looks like at some point they will support it.

I think I have created Category Definitions(131 Subtype) objects using Answer Modules code, it is probably posted in the Answer modules KB. Actually, AM support people gave it to me and I think I embellished it a little bit.

Content Server's language is Oscript so all these external coding avenues become Oscript at the server so that is also an option

that would be my $0.02😀

Ed Davis

It would be great if the REST API for Categories were extended to include Category Definition and Definition Updates. Some commenters have alluded to OT doing something around this in a future build and I do always check the updated API. I have quite a few automation tools and designers for creating Web Report Forms that utilize AJAX calls to service category data, but I still have to create the Category manually. I'm not a CWS nor oScript Dev guy or do I inspire to be one as most of my work utilizes REST API's, JavaScript and JSON data. The other reason is that we have extremely limited access to the back-end of our environment because we have a Application Support Agreement with a Vendor who looks after this. And we also require Segregation of Duties SoD for audit purposes, so we generally separate out the Front-End and Back-End Access. I really hope that future REST API versions include more complete object CRUD type functionality that is currently available from the UI .

That said, what is the process for submitting a "Feature Request".

Cheers,

Appu Nair

You have to write to support at Opentext dot com with a valid End User Code . This forum is self registering and does not take into account whether you are a paying customer. Once they know you are a paying customer you will have to somehow convince them that I need code to create subtype 131 and create attributes because more than likely 131 can be created but really of no use until they give you the code . If your need was emergent then one would write the missing piece in Oscript so it is a proper api or write a WR Extension custom tag.
While this is not a proper API by any standards creating categories or any other objects can also be done by XMLImport & XMLExport ( This is not Object Import & Export) .This functionality is very old and forms the basis of the Transport Subsystem of OT CS. In reality what you would do is somehow place a XML file that contains the Create category Instruction on a livelink server and run a URL to consume it.The XML file has to be on the livelink server .I don't think it is smart enough to overlay versions so perhaps OT Transports have additional code to handle that.

Ed Davis

Thank you Appu...

I'll try to create a Feature Request to OT Support. Seems kind of odd to be able to create a Category, but not define it. The other options suggested would be problematic as I do not have Back-End accessibility. We are currently migrating to Azure with xECM for our SAP implementation so I suspect that because of our financial audits and SoD it will be further locked down. I'm a bit surprised that the REST API has not matured much over the last couple of years, but that may be a reflection that the SMART interface hasn't either and it utilizes REST. WE are doing some great things with the REST API, but like the SMART UI, you get so far then you have to resort back to Classic functionality.

Cheers,