简体中文
EnglishHow to Get Help with Visual Paradigm Issues on the Forum
Updated
The Visual Paradigm community forum at forums.visual-paradigm.com is where you can search existing threads, post a question in the right category, and get answers from other users and Visual Paradigm staff. It works best when you first search for your issue, then post with your exact version, build number, steps to reproduce, and any error text or screenshots. The forum is a discussion board, not a live support channel, so response times vary by topic and how specific your report is.
What the forum covers
The board is organized around product areas and problem types. From the visible topic list, the active categories include:
| Category | What it's for | Example thread from the board |
|---|---|---|
| Bug Reports | Reproducible defects, crashes, display errors | "Formatting Note on sequence diagram", "Unable to launch Visual Paradigm Community Edition Version: 16.1" |
| How To | Usage questions with a known answer | "How to import a Swagger (yaml file) in visual paradigm" |
| UML modeling | Diagram-specific modeling questions | "Linking attribute of class in an UML class diagram" |
| General Questions/Discussions | Broader product questions, licensing, performance | "How to use > 2G max memory", "Will Visual Paradigm support DMN any time soon?" |
| Feature Suggestions | Requests for new or changed functionality | "Is there a plan to support SysML v2?", "Diagrams in MS Office editable form" |
| ChangeLog | Release notes and version changes | "Visual Paradigm 18.1 ChangeLogs" |
Each thread shows a reply count and view count, so you can gauge whether a topic gets attention before you post.
Before you post: search first
Many questions are already answered. For example, the board shows a thread on importing a Swagger YAML file with 18 replies and nearly 5,000 views, and one on the 2 GB memory limit with 13 replies and over 3,800 views. Searching those first saves you waiting for a reply.
Search by the exact error message or the feature name, not a paraphrase. If you find a thread that matches but is unresolved or old, add your details to it rather than starting a duplicate — that keeps the context in one place.
Choosing the right category
- Something is broken or behaves differently than documented → Bug Reports. Include the version and build number, as in the existing thread "Unable to launch Visual Paradigm Community Edition Version: 16.1 Build number: 20200601".
- You want to know how to do something → How To.
- The question is about a specific diagram type → the matching modeling category, such as UML modeling.
- You want a capability added or changed → Feature Suggestions. Existing examples include SysML v2 support and editable diagrams in MS Office.
If you pick the wrong category, the thread may still get read, but the right one reaches people who watch that area.
What to include in your post
A report that gets answered usually contains:
- Product and version — for example, Visual Paradigm 18.0 or Community Edition 16.1, plus the build number if you have it.
- What you did — the exact sequence of actions, step by step.
- What you expected — the behavior you thought you'd get.
- What happened instead — the actual result, including any error text copied verbatim.
- A screenshot or file — for visual problems like the thread "Cyrillic characters display as ?????? in Postmania web interface", an image makes the issue concrete.
- Environment details — operating system, and whether you're on desktop, Visual Paradigm Online, or a server product, since the board covers all of these.
Vague posts like "it doesn't work" are hard to act on. A post that names the version, the steps, and the error is something a reader can reproduce.
After you post
- Watch your thread for replies and answer follow-up questions — responders often need one more detail before they can help.
- Mark or state the solution once it works, so the next person searching finds a resolved thread.
- Don't bump repeatedly. If there's no reply, add new information (a log, a test on another machine) rather than just "any update?".
- Keep one issue per thread. Mixing two problems makes it hard for others to follow and for you to mark an answer.
Common pitfalls
- Posting without a version number. The board has threads spanning versions 16.1 through 18.1, and behavior changes between them. Without a version, no one can tell if your issue is already fixed.
- Assuming a reply is official. Both community members and Visual Paradigm staff post. Check who is answering before treating a response as authoritative.
- Expecting instant turnaround. This is a forum, not a support ticket system. Threads with clear reproduction steps tend to get faster, more useful replies.
- Posting the same question in several categories. It splits the discussion and can be seen as noise.
If your issue is urgent or account-specific, the forum may not be the fastest route — but for reproducible product questions, it's a searchable record that often already contains your answer.