Visual Paradigm’s floating license environment allow teams running in mixed editions of Visual Paradigm. User can launch Visual Paradigm in specific edition according to the availability of license in license server. To do this:
If your Visual Paradigm license is covered by active maintenance, you will be eligible for an upgrade to the latest version. But sometimes, you may find your license remains not upgraded even though the maintenance is active. Why is it so?
The license used by John Doe is not upgraded even though the license is covered by active maintenance.
On macOS 11 Big Sur open the diagram or model specification dialog may cause the application hang. The root cause is the Big Sur changed some behaviour on handling of non-modal dialog when application is run in full screen mode and this change affect most of the Java applications including Visual Paradigm. The following patch build solved this problem by turning the specification dialog to become modal by default.
Read moreBy setup VP Server as system service it will automatically starts when the machine boots. This avoid the VP Server need to manually start by user before using it. In this article we will show you how to setup the VP Server as Windows system service.
I do have a valid license but being prompted I’m not entitle to upgrade to newer version:
Visual Paradigm Update complain user not entitle to run new version
VP Server providing the update server module which helps to host the product update. The update module will constantly check for update from Visual Paradigm’s download site. By configure user’s Visual Paradigm client performing update via the update server, the colleagues are guarantee to be running the product on the same build. But for some company they want their colleague run on a fixed build rather than the latest one, you can then follow the procedure below to configure the update server only provide update on specific build number of Visual Paradigm. Read more
When trying to establish reference between projects it complains user is trying to establish reference to itself.
Try create project reference but complained reference to the project itself
Error was show when trying to enter non-English text to Customer Journey Map (CJM), no matter within Visual Paradigm Desktop application or Teamwork Server’s web interface.
Fail to edit Customer Journey Map (CJM)
There are lots of similar stereotypes being created in our team collaboration project. How can we avoid this problem? In Visual Paradigm you can grant edit stereotype permission to specific user/group, or allow particular user/group to edit the stereotype just on specified projects. In this article we will teach you how to configure your repository to achieve this.
When import a project from VP Desktop client to repository (VP Online or on-premises Teamwork Server) it complains the project already exist, even the same named project already being deleted in repository…
Same named project already deleted in repository but still cannot re-create it
