Visual Paradigm version 15.2 Enterprise Edition support customization on the built-in TOGAF ADM and Project Management guide-through process. This include altering the process navigator, phrases, activities and deliverables. In this article we will show you how to customize on the guide-through process.
Starting from version 15.2 Enterprise Edition users can perform customizations to the TOGAF and Project Management Guide-through process, which include modifying the workflows also define custom deliverables. In this article you will learn how to customize the deliverables in the guide-through process.
After upgrade VP Server to new version then the backup script become fail to work with following (or similar) error.
[message] java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory [message] at v.bsr.as.<clinit>(:15) [message] at v.bsr.az.<init>(:783) [message] at v.bsr.bk.<init>(:253) [message] at v.bsr.bk.a(:94) [message] at v.sj.bz.a(:252) [message] at v.sy.c.a(:164) [message] at v.ayi.e.c(:267) [message] at v.ayi.e.a(:99) [message] at migration.ExportVPServerMain.<init>(:266) [message] at migration.ExportVPServerMain.main(:24) [message] Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory [message] at java.net.URLClassLoader.findClass(URLClassLoader.java:381) [message] at java.lang.ClassLoader.loadClass(ClassLoader.java:424) [message] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) [message] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) [message] ... 10 more
Customer Journey Map (CJM) is a powerful customer experience (CX) tool which helps to study customer experience by visualize their thoughts and feelings though the touchpoints. It helps businesses understanding the behaviors, thoughts and feelings of their customer. In Visual Paradigm the CJM is not a standalone tool, it can further link up with other diagrams such as system design diagrams, business process diagrams, etc…, or further drill down by another CJM to elaborate in details.
When perform software update you may receive error complain didn’t have sufficient permission to perform software update.
When working with a large scale project with numerous diagrams, there may be some performance difference. It is only natural as huge projects impose more demanding resource allocation. Fortunately, Visual Paradigm offers ways to gear up for better accommodation. Basically, there are 3 practices we would recommend:
- Close unused diagrams before closing the application
- Use hierarchy to organize objects (avoid a flat structure at root level)
- Modularize diagrams (avoid giant diagrams)
For details, please visit Performance tune up for your large project.
On the note of resource allocation, some tasks are more memory-intensive than others, such as document generation which needs to process most of the elements (if not all) within your project. The default memory size is set for popular computer configurations but can be increased to speed up the process when needed.
Layout of diagram is a resource intensive action. By default Visual Paradigm set the limit to handle maximum 300 connectors in single diagram when perform layout. If your diagram got more than 300 connectors then the following message will be shown when you try to perform layout.
Changing product edition is particularly necessary when you want to test the functionalities supported by different editions of Visual Paradigm during evaluation period, or reserve license in particular edition for your teammate when running in floating license environment. This article will show you how to switch the edition of your Visual Paradigm software. Read more
Starting from Visual Paradigm 15.2, a new work item authoring mechanism has been introduced, which makes the entire authoring process more seamless and effortless. It is recommended that users who upgraded from earlier versions start using the new Work Item Composer for authoring. Below we will walk you through the details.
Some Mac users may experience problem on unable to enter non-English characters into story map. To solve this problem: