If you access the new support page, there is a section where you can find roadmaps for the products, and if you check the Documentum related ones, you’ll see the target date for ths new version listing new features. Without going into much detail (As I’m not sure how public this info is), these caught my atention:
- Ongoing exposure of D2 APIs through REST (goodbye DFS?)
- Native support for S3 object storage protocols to alleviate storage costs (goodbye OnDemand, hello AWS?)
- New REST Services (see #1, no mention of DFS anywhere to be found)
- Webtop will get a 16.3 version (yeah!)
14 thoughts on “Documentum 16.3 delayed until Feb 2018”
S3 support was even in EMC’s plans: https://www.slideshare.net/michaelmohen/whats-new-in-documentum-73 (slide 26)
Are they going to replace vulnerable jars in D2 (https://nvd.nist.gov/vuln/detail/CVE-2017-5586)?
Regarding D2, for their “first” version, I’ll be happy if at least they remove all the duplicated libraries
Is DFS a personal target for your projects? Baseline REST is a mature offering and it has active Engineering working on it. The planet seems to be focused on a RESTful interface and the DCTM platform is meeting that focus with a set of platform APIs. As I’m sure you are aware Captiva, xCP and D2 can be access through REST interfaces.
I think DFS (in its current state) is pure, obsolete crap. I’m also on the REST boat 🙂
LikeLiked by 1 person
Hey, REST funs, how can I launch workflow using REST API? The underlying protocol is not an issue at all, the imbeciles who unable to implement base functionality during 5 years – that is the issue.
I haven’t done that with REST, but I’m going to risk an answer: the same way that you do with DFS, coding it? 😛 (I’m pretty sure it can be done from REST as you have access to DFC in the worst scenario)
Bad attempt. DFS has built-in workflow service :DEVIL
I was afradi so 😀 how long it took them to implement it? 😀
Technically, from customers’ perspective it took nothing: first major release (I’m talking about D6, that was 2008 if my memory serves me right) was bundled with full-functional DFS – CMA was positioning it as a full-featured replacement of DFC. On the other hand, REST after more than 8 years of development (check this: http://craigrandall.net/archives/2009/07/dctm-restful-svcs-eap/) is still a piece of dog crap.
I buy your argument 🙂 I still rather use REST, as long as it meets the business requirements. Besides, and I’m quoting EMC/OT here (lol), if you want to use worflows, you should use their “rapid application development platform”, aka xCP (or “excremental (de)composition platform) 😛
Aha! If I need transactional processing I need to use DFC, and if I need both I need to consider other alternatives 🙂 Your boat have never left a dock 🙂
Andrey, can you be a bit more explicit about your definition of “Transactional processing”? Are you referencing “chained” operations which need to be completed or rolled back as a unit?
A more recent source for REST Services information is here.
Craig Randall has been gone a very long time.
Tomas, you just have confirmed my thesis that ECD employees experience difficulties with reading, my original message was about the fact that after more than 8 years of development REST API lacks a lot of vital functionality (if talk about “transactional processing” the ““chained” operations” is just a small part of required API, but even this part is implemented incorrectly). And Craig’s blog was mentioned above to provide the correct estimation of how old REST API is – compare with yours “Baseline REST is a mature offering and it has active Engineering working on it”. All what ECD was/is doing could be described using following quote:
> Doug the Head: We got sandy beaches.
> Avi: So who the fuck wants to see them?
Thomas Rouse: Documentum has mature REST API, which does not support even 10% of Content Server functionality
Customers: So who the fuck wants to use it?
[…] again I get inspired by to write this blogpost by Alvaro de Andres Documentum 16.3 delayed until Feb 2018 blogpost – there is some “interesting discussion” about REST where you can find […]