Hi There,
Is the rest API end point where you can use the Business Object ID and have it return the node information of the business workspace?
Regards,
Matthew Barben
Hello Matthew,
What BWS info are you looking for?
The XECM REST API and CS Core REST API is surprisingly excellent, and mostly well documented.
The next best thing about the REST API is that you can call a WR with it, making is readily possible to implement your own Custom API Command (be it either a lookup, or Custom Action) without any OScript whatsoever.
For Example:
I implement a REST Command called ECMPath for OI (because ECMPath isn't in the OT API but a needed value for creating a good OI Control File)
What info do you need off the of the BWS? If you just need the "biz props" / cat & atts why not just use the core REST API to pull that info off it with the bws_id?
Failing that, make your own Custom WR that returns whatever you want.
https://developer.opentext.com/apis/14ba85a7-4693-48d3-8c93-9214c663edd2/e2542ad2-e957-4380-8e1a-3413451e9b51/d3b93af3-cac7-489b-aa52-779c756b8b08#tag/businessworkspaces
https://developer.opentext.com/apis/14ba85a7-4693-48d3-8c93-9214c663edd2/e2542ad2-e957-4380-8e1a-3413451e9b51/935d02c0-4e03-4f1d-b3cd-7d9a6017e4f7#tag/categories
Thanks Clark,
The scenario in this case is:
I am aware that there is likely some work around for this (for instance WebReports), I am not looking to own that extension through customisation - I would rather that it be in the API to use (and for everyone to enjoy 😎)
In my scenario, I am looking to assist a customer with a fallback in the instance that a workspace gets created in Content Server but the data id does xecm__BusinessObjectWorkspace__c does not get created in Salesforce.
Hey Matthew,
I believe the official XECM Answer/Official API Answer would be that you require more information to resolve the bws_id. via the XECM REST API you can resolve the bws_id using:
Here is a line from C# program of mine:
var request = new RestRequest("/api/v2/businessworkspaces?limit=30&page=1&sort=asc_name&metadata&expanded_view=true&where_bo_type=" + bo_type + "&where_ext_system_id=" + ext_system_id + "&where_bo_id=" + bo_id, Method.GET);
That's the best you are gonna get from the official API.
Unofficially, I think the info you want it stored in. OTSAPXECM_WKSP_LINKS
With the awesome power of the WR and the REST API you could simply implement your own REST lookup and call that instead. The gaps in the official API are readily solved with WR.
-MC