Contributions
Why did I start getting file conversion errors relating to fonts not being available in my database?
Starting around the middle of June 2023, we started getting font conversion errors, indicating that a font was not in our database when converting the file to .pdf. It had to choose a similar font. Why did it start getting this error at this time. We have been using Collaborator Enterprise (v13.6) since June of 2021. What triggered this change? Why did we start getting this error after two years of use? I can put the same document in our test server that is using v14.3, and the conversion happens just fine. I could see us having a problem the whole time we have been using v13.6, but why did we start having problems after 2 years of use? Other than upgrading, what can we do to add different fonts to our database?261Views0likes0CommentsChecking links within documents in review
Is there a way to check links within documents that are in review? Many of our documents we are reviewing have links in them. In order to check the links we currently have to download a copy of the document so that we can check links outside of the tool. Is there a way to check them within the tool and avoid the extra work? Is there a way to check links within the document after it has been converted to a .pdf?547Views0likes0CommentsRe: Auto logout from web interface
My organization got so frustrated with this situation that we created our own script to log people off at any interval we wanted. We log off the most inactive person after we reach a threshold of a set value. Since we have implemented this, we have not had one license denial.3KViews0likes0CommentsRe: Allow Admins to close reviews
Another option is to put a comment in the chat section that explains why you are making a change to roles. You can explain that the person has left the company or is out on short term leave. This at least shows dates when your comment was made if an auditor looks at it and has questions. Many things can be adequately explained to an auditor if it was documented when it was done, rather than trying to explain during an audit.1.7KViews0likes0CommentsArchiving to a different Network location
I am using Collaborator Enterprise 13.6 and trying to archive my nearly 1 TB of data in my Content Cache folder on my server. We have tried to archive off to a separate network location (to free up space on my server) and it will not copy the files. We have to do this the brute force method and archive to a location on the same server (small increments) then copy that archive to the other network location. We will have to do this with each incremental archive. Then they are not together, but they are still individual archives. I would like to request that the ability to archive to another network location be added so that when an archive is done, the data is all together in one Content Cache folder, and I don't have to look through a bunch of separate archives to find the review I want to restore.798Views0likes1CommentLinks within Document Reviews
Is there a way to check links within documents that are in review? Because Collaborator makes a .pdf of the document that is under review, the only way we know of to verify links or to go to the link in question is to download a copy of the document under review and click on the links outside of Collaborator (within Word, etc.). Is there a way to verify that the links work correctly from within the document in review?573Views0likes0CommentsNot allowing removal of participants without confirmation
I would like to suggest that removing of names can't happen without a confirmation. This is especially true when the removal of the name will allow the review to be completed prematurely. If there was a confirmation screen that popped up that said "Are you sure you want to delete this person even if the review will complete at this time, and in order to re-open the review you will need the assistance of an admin?" We have had several recent examples where a participant was removed from the review before the replacement participant was added, and the review ended prematurely and had to be re-opened by an admin. The proper sequence would be to add the new participant before you delete the old participant. The review would not end in this sequence because the new participant would have to approve of the review before it completed. People do not know that they need to add before they delete. The confirmation screen would not prevent this from happening in all cases, but it is better than not knowing that they will cause problems if they delete first. We are open to other suggestions, if someone has a better way of avoiding the situation.495Views0likes0Comments