Contributions
Re: User sync with AD group
We considered updating from 11.2 to 11.4, but stopped activity due to various reasons. And we could not get the "Automatic user and groups sync" working. So 11.2 still in use. For 11.2 I have programmed a web app that makes use of the REST API to create the user accounts in Collaborator, assign them to Collaborator groups, and automatically send an email to the new users with instructions. Collaborator itself is configured for LDAPs auth, so with the web app the "sync" is only one step now - without user interaction in between. If somebody wants the source code, I can share.3.5KViews0likes0CommentsFilter on own comments
To improve the user experience of Collaborator, users would like have the possibility to filter on ones own comments when having to mark findings fixed. It would speed up the entire review process when a reviewer does not need to delve through all comments of other reviewers when looking for his/her own review comments.4.6KViews3likes1CommentRemoval of uploaded material of completed reviews
In a regulated environment the compliance with development processes need to be proved. An organization needs to be able to access all artifacts for about 10-15 years depending on the regulation requirements. Therefore version control systems are used to guarantee the access for all versions of saved elements. If there is the requirement to perform reviews prior to check-in of content, the review data like comments, status and review material must be available during the whole time. But the review material should already be stored in the version control system so that it's storage in the Collaborator cache is only needed as long as the review is not completed. Especially Office documents that are converted to images use a lot of space on disk. It would help a lot to have a button like "Remove uploaded material of completed reviews that are completed since xxx date".16KViews15likes12CommentsUser sync with AD group
Hi, the authentication via LDAP is a nice feature to organize the user registration in a world-wide environment by use of several AD groups that can be administered business-unit-specific. Unfortunately the user is not known in Collaborator until his/her first log in. This results in three steps: 1. Adding to AD group 2. User must log in 3. Project admin can add user to group Each step results in a latency and communication overhead between the admin and the user. It would be great to have a button in Collaborator's user management panel like "sync with configured AD group xy" (similar to RTC for example).10KViews9likes5CommentsMultitenancy or License sharing between instances
Hello, to use Collaborator in a big world-wide operating company with different business groups that each have their own workflow these improvements would make life much easier: 1. a license mechanism that allows sharing the licenses between various server instances. or 2. Multitenancy Let me please go into detail: To point 1: This way a Collaborator server can be set up and customized for each group individually but still users are granted access by requesting a license from a global license pool. In a world-wide scenario this license mechanism would allow a better flexibility in the sense that all users benefit from the different time zone that the other business units work. Exceeding the max license number during peak times can better be avoided. In addition, the use of standard license servers like FlexLM would give us sufficient reporting information that could be used for license purchase decisions, Nagios binding etc. to prevent the situation of license exceedance in advance. To point 2: As an alternative to point 1 it should be possible to isolate the various business groups: - there should be a new admin layer that allows a business group admin to customize only their project settings like review templates, review notifications, user-defined attributes etc. In Collaborator everything is global, which makes it very difficult. All changes need to be discussed in a global Change Control Board. In a first degree it would help a lot to have the possibility to assign review templates to review groups, because a wrong-chosen template happens most, and we need to guarantee that a group-specific workflow is used.3.3KViews1like1Comment