When you are using Visual Paradigm Teamwork Server (Teamwork Server) or VPository and find a problem, feel free to contact Visual Paradigm to seek for assistance. Remember, the more information you give us, the easier and faster for us to identify the problem, fix the problem and provide a proper solution. In most cases, the steps to produce problem, the log file and a screenshot illustrating the problem are sufficient for us to identify problem. It would be even more effective if you can send us the local project, server revisions as well as the server database (for Teamwork Server) so that we can reproduce and fix the problem accordingly. Read more
When you are using Visual Paradigm, and find a problem, feel free to contact Visual Paradigm to seek for assistance. Remember, the more information you give us, the easier and faster for us to identify the problem, fix the problem and provide a proper solution. In most cases, the log file, project file, steps, screenshot and product information are essential for us to identify problem.
When you report an issue to Visual Paradigm, you are encouraged to provide the build number of your Visual Paradigm product installation. By knowing your build number (and other details provided), Visual Paradigm technical support team can take appropriate measure to your problem. Let’s say if the issue you reported has already been fixed in a newer build, we will suggest you to update to the latest build. Otherwise, we will fire an issue report to our team to fix it.
In this article, we will show you how to identify the build number of your Visual Paradigm installation.
Visual Paradigm is always committed to deliver the best possible service to users. When users experience issues that seem to be too complex to diagnose over emails, users could send over their project files for us to better understand their problems and come back with a solution faster. However, we also understand that users might be concerned with passing along project files which contain sensitive or even confidential business information. To address this concern, we have developed the Project Anonymous Tool for users to hash their project data into meaningless information and make it safe to send in for diagnosis.