Is there any support for OpenText Extended ECM for Engineering in CWS?

Hello.
We are in 16.3.6 and I would like to know if there is CWS API support for xENG, stuff like:

Create a controlled document,
Promote or Demote a ProcessFlow
Create Revision

If so, can you share links to documentation please?

Thank you.
David

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Appu_Nair1

This forum is a very old Builder Forum many new developers do not even look here. You should mostly try this forum at least I think you will get a better recommendation https://forums.opentext.com/forums/categories/cs-Enterprise-Library-Services .When XECM started originally there was a CWS middleware called RCS now it is called ECMLink these are rolled up SOAP and REST code so you don't end up programming in raw SOAP layer. My guess is XENG is a hot things at OT and there might be awesome REST API's now

Your posting leads me to think that you want to work with objects in the CRT/ASM modules of OT I am pretty sure API's exist for those and if it isn't creating them is also not that difficult.

All comments

Appu_Nair1

Your posting leads me to think that you want to work with objects in the CRT/ASM modules of OT I am pretty sure API's exist for those and if it isn't creating them is also not that difficult.

David_Uztariz

Thank you Appu...

I will check it out.
And yes. I am trying to implement an integration layer for CRT/ASM modules .

Appu_Nair1

One thing that many orgs do and it may not be a true webservices things is OT has a useful module called Object Import & Object Export it is used to bulk load things from file systems. The Files are XML instructions. Many times when a new module comes a addition to OE/OI layer happens and we used to do a lot of otherwise repetitive work like adding Contacts ,Distribution Lists ,Matrices so since XENG is really a rollup of Transmittals, CRT/ASM I am hoping you could probably get a OI/OE version .Then you can most probably do what you need but it probably will live in a asynchronous layer. That is if you find proper public API's don't exist.