This content has been marked as final. Show 7 replies
You can't get all revisions using GET_SEARCH_RESULTS. Only the latest released revision is available. This is the correct behavior.
You'll have to write something custom to get all revisions.
The console page can pull up all the revisions of a document. Is this anything that can be leveraged?
Keith Fosberg wrote:The console page can pull up all the revisions of a document.You mean the document information page? If you know the dDocName value for a given document, DOC_INFO/DOC_INFO_BY_NAME will return minimal revision information for all revisions of the provided dDocName (but not all of the metadata for every revision) in a single service call.
It really depends on exactly what you are attempting to do. If you are looking for a revision "listing", this is ok. If you need more data, like "what was the title of revision 5?", you'll need to execute the DOC_INFO service with the correct dID number for the desired revision.
Otherwise, you're looking at a customization if you need more data in a single execution.
What they would like to do is be able to list all the revisions of a given document and pull the one they want.
Pulling a specific revision is easy enough if I have the dID value but it doesn't appear that there is anything available out of the box to get a listing that gives me the revision number and dID for each revision of a given document.
If I need to write a custom Webcenter webservice interface to handle that I think they can be convinced that it's not a capability worth delaying delivery for a number of weeks for. :)
This component should be quite an easy one - it will be faster to go and run queries directly against DOCUMENTS and REVISIONS tables rather than analysing the (html) output of dDocInfo service.
However, can you describe your use case in with a bit more details (in plain English)?
Note that there is always just one "current" revision (if fulltext is used, only this revision is indexed), so what's the purpose of having direct access to older, or newer (not yet released) revisions? Maybe, rather than "older revision" the customer wants "a revision that was valid in the given timeframe"? It may complicate your component, but you will produce much better results...
If you call the DOC_INFO service, all that revision ID data is in the result set "REVISION_HISTORY".
You can see this if you go to the Content Server and go to a document information page. If you are using Top Menus as your layout, add "&IsSoap=1" to the end of the doc info page URL. You'll see the result set midway down the page.
What we are storing in UCM are pdf documents (they are appraisals and related documents.
The user will get hit a URL which will run (among other things) a web service call to get a list of the documents associated to a property. They may, in the course of doing business, upload a document several times. There was some talk about making it possible for them to grab older versions.
We are just using Webcenter/UCM as a file repository. We are not running a website or applications out of it.
I have to stay with the parameters of all calls to Webcenter/UCM being done as webservice requests (choice for that architecture was made above my pay grade and they aren't interested in arguments from me otherwise!)