OK, so this subject has been posted several times since 2008 with little or no feedback, but I will try to see what's out there...
For those of you who are struggling with the basics, I've got it running quite nicely on my dev instance (so pop any question you have here and I'll try to answer them). However I've come to a couple of issues I'm "hoping" someone has resolved.
- Placeholders or "leaf nodes" appear to have little use. For instance I can create a "new document" instance which is then pretty obvious to the case user that something needs to go there. A placeholder only appears on validation. So I'd like to understand the thinking behind placeholders AND how I can satisfy the validation, in the demo, simply creating a dm_document object with the name "Fingerprints" (correct capitalisation) is not sufficient.
- For the supporting classes, of which there are many there is no documentation, which means when I try to trouble shoot the above, I'm left scratching. Here's the declaration to see if I can catch someone's eye...
com.documentum.fc.client.smart.IDfSmartObject.getSubordinateMaterializedPlaceholder (name)
- There's a big push at present for xCP which I'm pretty sure encompasses Smart Containers. Now the Smart Container is a great little leverage for getting users to build manageable structures and I would like to push this out to most departments however I need some confirmation of the legitimacy and long term support of said classes, so:
- Are Smart Containers remaining in Composer for the foreseeable future?
- Will new versions of Webtop include "File > New > Smart Container Instance" by default?
- xCP is currently being marketed as freely downloadable startup solutions but will the same be said of Smart Containers in future releases?
Thanks in advance
Colin Hewertson
