ContributionsMost RecentMost LikesSolutionsRe: SSO configuration Azure AD Check the contents of the SAML Metadata endpoint in the Collaborator server: https://support.smartbear.com/collaborator/docs/server/admin-tasks/single-sign-on/saml.html The EntityID is the URL of the Collaborator server. I believe the Reply URL is the ACS endpoint in Collaborator. The Azure AD (Microsoft Entra) docs https://learn.microsoft.com/en-us/entra/identity-platform/reply-url indicate that the authentication response coming from Entra should be directed to the Reply URL. The Collaborator ACS endpoint handles the authentication responses from the IdP. (This is only my understanding based on limited experience.) Re: Review Subscriptions & Role Changes Bit of background: A user can subscribe to a particular author's reviews and be added to the reviews in a chosen role. Every time there is a change made to the participant list in a review, Collaborator has to go check to see if there are any subscriptions from any users which now apply. You've subscribed to be an Observer but as soon as your role is changed it is immediately changed back to Observer because your subscription is in effect. "Review Subscriptions" are part of a user's preferences: https://support.smartbear.com/collaborator/docs/web-client/manage-acc/user-prefs.html#review-subscriptions You can change your role in the review only as long as the subscription doesn't apply. So, for example, if you change the Author of the review then you can change your role. But as soon as you change the Author back, your subscription will force your role back to Observer. Re: Saving review with comments & pins Check out the Archive Reviews article: https://support.smartbear.com/collaborator/docs/working-with/misc-tasks/archive-reviews.html The zip file can contain a PDF showing where the pins are, as well as a report showing all the comments. Re: Migrate Review Templates No, you cannot import/export review template definitions. There is no facility in Collaborator for doing that. You can export the definitions of customizable review reports (but that is reports and definitely not templates). Re: Collab 14.0.14002 : How to see what is blocking code review from getting Approval? It is not usually the author who has the responsibility to move the review from INSPECTION to COMPLETED. It is usually the reviewers with that responsibility. When you hover over the "Send to Completed" button for each of the author and reviewers, what does the tooltip say? If you are in the INSPECTION phase are there are open defects, the button will say "Send to Rework". If there are no open defects, it will say "Send to Completed". Once all participants (*who are required to*) click on "Send to Completed", the review is done. See the documentation about the workflow in the review: https://support.smartbear.com/collaborator/docs/working-with/concepts/phases.html Re: Annotating Attached Word Docs Make sure the file type of the document is *not* listed as a binary file type: https://support.smartbear.com/collaborator/docs/server/settings/general.html#file-types Re: JSON API not working to update reviewers Quite right! Thanks for the feedback. We'll get the docs fixed. Re: Collaborator 13.2 and 13.4 cannot login in the command line if the password contains a double-quote This isn't a Collaborator problem . . . it is a Windows CMD shell problem. You will have a problem with other characters as well (like caret ^ and ampersand & and percent %). There doesn't seem to be a simple clean way to do this. Re: Collaborator 13.2 and 13.4 cannot login in the command line if the password contains a double-quote Try surrounding the password with *single* quotes. Re: Collab "Cpu resources reduce" & "Version Upgrade" Problem For the first issue, use your system monitoring tools to verify what is using the CPU. Is it all Collaborator? For the second issue, "upgrade your database" refers not to which version of the Oracle server or Oracle JDBC driver you're using but rather to the fact that we have to upgrade (modify) the Collaborator database schema to work with Collaborator 13.6. The upgrade error *might* be a temporary problem in the internal DB upgrade process. Try restarting Collaborator. If that doesn't work, then the problem may be that you need the CTX_DDL package installed on the Oracle server. See this article: https://support.smartbear.com/collaborator/docs/server/install/db/oracle.html If that doesn't help, open a support case.