Good morning / afternoon / evening,
We recently implemented LiveLink as document management tool, but we encountered some problems. The main problem is that the last version is always the valid version, but there is no way to 'mark' this version as 'in draft'.
Let me explain the problem with an example. When we publish a workinstruction for a new function, this workinstruction has version 1 in LiveLink. If this function is changed (due to a change request or project), the workinstruction also needs to be changed. The changing of this document takes some time, so the workinstruction which has version 1 needs to have an 'in draft' version, which is not valid but can be accessed by multiple LiveLink users.
We asked Open Text but there was no answer that was satisfactory enough for us. I know there must be more companies experiencing this problem, so my question is: how did you or your company manage to insert some kind of status management in LiveLink? We run version 9.2.0.
We recently implemented LiveLink as document management tool, but we encountered some problems. The main problem is that the last version is always the valid version, but there is no way to 'mark' this version as 'in draft'.
Let me explain the problem with an example. When we publish a workinstruction for a new function, this workinstruction has version 1 in LiveLink. If this function is changed (due to a change request or project), the workinstruction also needs to be changed. The changing of this document takes some time, so the workinstruction which has version 1 needs to have an 'in draft' version, which is not valid but can be accessed by multiple LiveLink users.
We asked Open Text but there was no answer that was satisfactory enough for us. I know there must be more companies experiencing this problem, so my question is: how did you or your company manage to insert some kind of status management in LiveLink? We run version 9.2.0.