Best Of
Re: Document creation with Category Metadata not set in single shot using Rest and CWS SOAP Web service.
Some Advice I try to give this to young upcoming developers :)
For small-scale testing meaning you are a developer and the company has given you free rein on a CS instance when you say File in a payload you will be able to use postman to put a file on the server, run postman on the server and do all these things. However, when your code needs to work in production it will just fail as CS is actually a Document management system and they have to abide by web regulations, OT is on a typical threat mitigation team as many governmental organizations use CS, ( a virus is essentially something you put on a server) so this expectation of creating a payload with these things in your code should definitely be avoided I mean these kinds, "file":"D:\\CWSTest.txt",
Several great programmers before like @Ferdinand Prantl @Matthew_Pinkney and all have commented why you should refrain from trying to send a file that you have to put in a CS server ...
So I tried your code on my system and it worked in POSTMAN (on a server :)) before that, I went to JSONLINT.com to understand what you were doing as you are sending a list of categories From this screencap look at what the postman code is doing it is definitely not sending the File from a server point
in my headers, I have otcsticket that I got from an earlier call
In closing my advice is if you can afford it try with the simplest of categories stabilize your code with just text attributes then move on to more complicated like Date and other things. REST API errors are sometimes not very user-friendly...
I am not sure if CWS you need as it is getting very old and not many people to want to use SOAP nowadays...
I work with Oscript so many times I open up the debugger and see what is wrong with my rest call
If the simplest of REST works progress with the next category as in your example
Re: OScript Orphaning an object
Hi @Dave Carpeneto and @Greg Griffiths Thanks for all the details. The way I was orphaning an object previously, that was not the correct way.
However, after the discussion with @Appu Nair I am able to successfully orphan an navigation menu object and create a custom navigation menu . And @Greg Griffiths the steps I have followed is the exact same I have executed.
Thanks for all of your help.
A very happy new year. :)
Re: Content Server API - older versions
You are not.
The "REST API v1.0 (2014-06)" entry at https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=42329092&objAction=browse&viewType=1 still links to https://developer.opentext.com/webaccess/#url=resources%2Fapis%2Fcontent-server-v1.1&tab=501 which currently generates a redirect to the "OpenText AppWorks Developer website update!" intercept page. The Offline SDK Documentation package doesn't include it either.
I have not been successful in my hunt for a source for the Swagger docs to match each specific point/patch release of Content Server - and the docs that are available are very clear that the implementation of the RESTful interface is considered to be "product version specific" (ie. different versions might contain breaking changes).
Re: Content Server API - older versions
@Karen Weir , thanks for your reply.
But I already checked the link you mentioned and "Content Server REST API v1.0 (2014-06)" is pointing to https://developer.opentext.com/webaccess/#url=resources%2Fapis%2Fcontent-server-v1.1&tab=501, which redirects me to AppWorks page.
Am I missing something?
stakagi
Re: Grunt hangs when trying to build a sample
Re: Recommended version of NodeJS and npm for Widget Development
Thanks, @Karen Weir, it pushed this up in my mailbox after the Xmas vacation :-)
The best bet for Smart UI development is using one of the two most recent the Node.js LTS versions. This is what the OpenText developers do. Today it means 12 (maintenance) or 14 (active). Versions of Smart UI that we released during the last year were built with Node.js 12, for example.
The project generator for Smart UI extensions depends on a very old versions of the Yeoman Generator and other related NPM modules and that is why problems are likely to occur, when it is used today. A bug about this has been already filed for the Smart UI SDK project, but I am not sure, when it will be fixed.
My workaround was generating the project with Node.js 10 without installing the dependencies (which would fail), then switching to Node.js 12, and continue installing the dependencies and building the project. You probably use a Node.js version manager to be able to choose the version of Node.js flexibly, like nvm on Linux or Mac, or nvs or nvm-windows on Windows. For example:
nvm use 10 yo csui-extension --skip-install nvm use 12 npm i grunt
Re: Initiate Workflow from REST
