I have recently see a strange behaviour in supervisor…
People have published new release of report on repository and asked me to lock older versions so that users only access to newest release. I did the operation using general-supervisor and locked the reports but 4 users of one group still access some of this old reports…
They said they have tried first to did it using the supervisor of this group but they didn’t success too so they had asked me…
maybe they are conflicts between the differents overload ? What do you think about the problem ?
thank you for your suggestions. Yesterday, to correct it, i made in the folder an unlink of the bad report so that they don’t appear anymore in supervisor… but some users still see it using files/retrieves from corporate document… completely crazy !!!
As you said, i make users send “toto.rep” file to repository and I saw it appears in my supervisor. Ok, we are well on the same repository, Ouf ! :o
Another thing which is crasy is that on my BO, all things are rights, the reports which has not to be displayed are not displayed… But I am in 518 and users in 513… Could it be a BO Bug?? I have just open a case on OCS…
Just be very careful about 5.1.3. That release was a big challenge. 5.1.3 is 5 releases behind. For some reason the odd numbers have been problems. 5.1.6 or 5.1.8 are MUCH better. I wouldn’t bother trying to fix this with 5.1.3.
A trivial question: if you (using supervisor) want to delete documents, when you have the list of the documents do you see only one doc instance or more?
For example, if you should have more than one document domain, you could have disabled the document on one domain, but not in the other.