joseph_michaud
StaffJoined 14 years ago
User Profile
Staff
User Widgets
Contributions
Re: Microsoft Sensitivity Labels block uploads
ngohara , We've had a couple requests for this and it is in our list of enhancement requests. We're tracking this as COLLAB-12504. The difficulty with this is that using sensitivity labels causes the document to be encrypted. Collaborator would have to be tied into the Microsoft Purview system in order to decrypt the document. There are also considerations with (not) caching page images that would have to be taken into account. I've added your interest to this enhancement request.2Views0likes0CommentsRe: Replicating GUI function with CLI
When you 1) use the GUI client and perform "Add Git Diffs..." and specify two file revisions or 2) use the CLI to perform "ccollab addgitdiffs" and specify two file revisions, you will get a Review Materials entry with no commit hash. When you 1) use the GUI client and perform "Add Commits..." and specify a commit or 2) use the CLI to perform "ccollab addchangelist" and specify a commit, you will get a Review Materials entry with the commit hash you specified.98Views1like1CommentRe: Can a TestComplete license be used with TestExecute?
To be certain, go back to the License Manager on your bare-metal physical machine and verify that your licenses are still present. If you expect to run TestExecute then (naturally) you should have an active TestExecute license. (Note that the HASP-based TestExecute licenses were always floating, never node-locked). Then reexamine the base image used to create your Jenkins images. There should be no licenses activated on it and it should be able to see your License Manager machine, and be able to access a TestExecute license from the License Manager. (Note: If you activated a license in your base image those licenses will not be valid in any cloned images derived from the base image. ) If you can manually run TestExecute on your base image, try manually running TestExecute in a cloned Jenkins image on the machine where your tests are run. Perhaps the problem is that the local License Manager in your Jenkins image cannot find the network License Manager (the one serving the licenses). Maybe you need to configure the local License Manager on the base image (and cloned images) to explicitly specify where the network License Manager is. The License Manager software is always installed. If you have a license activated on the machine, then the License Manager serves the license. If you don't have a license activated on the machine, then the local License Manager acts as a broker and checks the network for a machine that is serving licenses. Check the License Manager docs for more info on how to configure it: https://support.smartbear.com/testcomplete/docs/licensing/key-based/how-to/license-manager/index.html41Views0likes0CommentsRe: 'Failed to open result JSON file' error with PDF.GetTextContent and PDF.ConvertToText
Also, how do I open a support ticket: The link https://support.smartbear.com/testcomplete/message/ doesn't seem to work anymore? The chatbot should automatically show up now. Use the chatbot to "Create a case".124Views1like1Comment