Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Word 2007 Document Footer Information from Livelink

Status
Not open for further replies.
mdietelbach

mdietelbach

IS-IT--Management
Jan 20, 2011
4
CA
Forgive me if this has been answered anywhere in this forum. I have searched a little but have yet to locate some details on this topic.

High level objective:
During the creation and management of documents created in Word (include other office products here as well) we have had a standard in the past of including a footer reference to the document name and its location. With the switch over to Livelink, this information that is displayed is less than useful to the end user because by default it includes only the document name and the path to the nodeID of the folder the document is stored in. The main purpose of this information is to provide clear information about the document printed on the physical paper.


We are interested in what options we have for obtaining three key pieces of information from Livelink that we believe would be sufficient to clearly identify that document as a point in time.

Document ID
Document Name (more for the human readability)
Document Version #

We would like this to be included as part of the document templates so that the user does not have to understand where this information is coming from, but mearly use or leverage the piece of code that obtains this information.

My understanding todate is that we need to use oscript to accomplish this. I have seen the following piece of code but not being a programmer, I am not sure how to use this piece of information.

FetchVersion(volumeID, dataID, versionNUM, objectPATH)

We have
Livelink ® Version 9.7.1.1158, RM module and many other components of the Opentext Suite. We are using Livelink WebUI as well as we have Enterprise Connect integration at the Desktop. We are using EC 1.5.0.715

We are more interested in how other people are handing this business item than re-inventing the wheel. With respect to Major/Minor versioning, it would be very nice that the document that was printed contained the matching version number of what is stored in Livelink. Right now, you need to change the document version number to 3.0 when you are editing 2.8 minor version, and then promote major as 3.0 so that these are in sync. Any method for helping with this type of document versioning presentation would be great.

Thanks in advance.

Mark
 
Sort by date Sort by votes
 
Upvote 0 Downvote
Thanks Greg for your input. I had to laugh at the second post. "Why would you want to do this, the document could be moved in livelink??? "

I see that as an OpenText failure to understand the business value. The customer wasn't really asking to have the "PATH" represented in the document, they like me want to place some evidence of where the printed document came from! In a file system that is the path, in Livelink the two key pieces of information are the DocID and Version #. The inclusion of the Doc Name is for the human readability.

DOCUMENT NAME [DocID] [Version#]

If the above was placed in the footer of a document, when it is printed you would use the DocID to take you directly to that document, check the version ID against what is there now to confirm it is the same OR you would know that it was from a previous version of the document. That helps the human identify that the physical piece of paper they are looking at is valid or not.

I also had to laugh at the third thread. Customizing livelink to embed the DocID in to the name is clever but points out that there is still a basic lacking in access to this information. I personally don't like that approach as you are using the document name to convey additional information that the "DOCUMENT MANAGEMENT SYSTEM" already does. Access to that piece of information is a fundamental building block.

Oh well, nothing like a stick and a dead horse....

Thanks for taking the time to respond. That is much appreciated.

Mark
 
Upvote 0 Downvote
Mark,
Happy to help, a thought occurred to me that if you opened the Doc via WebDAV rather than downloading it you may get a path reference there, have you tried it ?

Have you logged this question with OT, as the threads I found are a little old and there may be another way / module to do it now ?

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006
 
Upvote 0 Downvote
Greg,

This question has been asked six ways to sunday with OpenText Professional Services staff onsite. With other much bigger issues it has continuously fallen through the cracks. I will go back and check about direct questions to support. I believe they have been asked with very little result.

WebDAV - Very interesting subject. We had OT professionals state that WebDAV is not something you would use in a production scenario. ?? We are using Enterprise Connect, the replacement for Livelink Explorer Professional because we are on Vista and it made no sense to go with the old product. I do know that WebDAV is used by EC and we have it installed. I can make drive connections to the repository and perhaps I would see the path information in a different manner but again, the path is not really what I am interested in. DocID and Version are the two key pieces of information.

Mark
 
Upvote 0 Downvote
Upvote 0 Downvote
as I also would have tried to do it should a dev need exist


Looks like javaobject from oscript is the way to go

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

P
  • Locked
  • Question
Downloading files from Livelink URL
Replies
3
Views
361
appnair
appnair
aix_tiger
  • Locked
  • Question
How to backup STRATA LIVELINK
Replies
1
Views
200
ggriffit
ggriffit
sherriffot
  • Locked
  • Question
Tabs error Smart View - Opentext livelink
Replies
0
Views
185
sherriffot
sherriffot
sherriffot
  • Locked
  • Question
Change the label of search terms - Opentext livelink
Replies
1
Views
146
ggriffit
ggriffit
sherriffot
  • Locked
  • Question
Viewing by BravaServer does not work on SmartView - Opentext livelink
Replies
3
Views
264
Ekta Singh
Ekta Singh

Part and Inventory Search

Sponsor

Back
Top