forums.visual-paradigm.com

The forum at forums.visual-paradigm.com is where Visual Paradigm users track version changes and push for new capabilities. Two boards matter most for this: ChangeLog, where release notes are posted, and Feature Suggestions, where users ask for things like SysML v2 and DMN support. If you want to know what shipped in a given release or whether a feature you need is on anyone's radar, those two boards are the fastest places to look — but you should read them as a record of what users asked for and what was released, not as a committed product roadmap.

Where version updates actually get posted

The ChangeLog board is the forum's release-notes channel. From the visible activity, it carries entries such as:

Two things are worth noting about how this board works. First, each major version gets its own thread, and replies accumulate inside it — so the 18.0 thread with 18 replies is a longer, more discussed release than 18.1 with 9. Second, view counts are modest (109 and 470), which tells you this is a reference board people consult when they need it, not a high-traffic discussion area. If you're checking whether a specific fix or feature landed, read the thread for your version rather than searching the whole forum.

What the ChangeLog board does not give you

It is not a comparison table, a migration guide, or a compatibility matrix. It's a changelog thread. Treat it as a pointer to what changed, then verify behavior in your own build.

What users are asking for in Feature Suggestions

The Feature Suggestions board is where forward-looking requests live. The visible threads show the range of what gets proposed:

• Is there a plan to support SysML v2? — 2 replies, 178 views. Tagged sysml.
• Diagrams in MS Office editable form — 3 replies, 96 views. Tagged modeling.
• Additional default format for UML modelling in black and white — 2 replies, 107 views.

A pattern emerges from these numbers: feature suggestion threads get a handful of replies and low-to-moderate views. That's normal for a suggestion board — most requests don't become long debates. The SysML v2 thread is the clearest example of a standards-support question, and it's the kind of request where the answer depends on Visual Paradigm's own release planning, which the forum itself won't settle.

Requests that show up outside Feature Suggestions

Not every "will you support X" question lands in the suggestions board. Two examples from the general boards:

• Will Visual Paradigm support DMN any time soon? — posted in General Questions/Discussions, 8 replies, 3,780 views.
• Version of Hibernate & Spring Datasource Support — also in General Questions/Discussions.

The DMN thread is instructive: 3,780 views against only 8 replies means a lot of people were watching that question. High view-to-reply ratios on "will you support X" threads are a useful signal that a capability gap is widely felt, even when the thread itself is short.

How to read official responses

The forum is titled "Discuss the Visual Paradigm," and the excerpt shows a mix of user-to-user threads and staff-adjacent announcements (the ChangeLog posts). When you're evaluating whether a feature request has traction, weigh these signals:

1. Reply count — more replies usually means more back-and-forth, which often includes a staff answer.
2. View count — high views with few replies means broad interest but no resolution.
3. Which board it's in — a request in Feature Suggestions is filed as a request; the same question in General Questions/Discussions is being asked, not formally proposed.
4. Whether a ChangeLog thread later references it — a suggestion that turns into a release note is the only hard confirmation that it shipped.

None of these signals is a commitment. A staff reply saying "we'll consider it" is not a delivery date, and a popular thread is not a roadmap item.

How to participate or submit your own request

If you want to add your voice or file something new:

1. Check the ChangeLog board first for your version — your request may already be addressed.
2. Search existing Feature Suggestions threads before posting, so you're adding to a request rather than fragmenting it.
3. Post in Feature Suggestions if you're formally requesting a capability; use General Questions/Discussions if you're asking whether something is possible or planned.
4. Tag your thread with the relevant area (the visible threads use tags like sysml, modeling, database, code-engineering) so others can find it.
5. State your use case concretely — "I need SysML v2 because my team models [specific thing]" gives staff something to evaluate, whereas "please add SysML v2" does not.

A realistic example

Suppose you need DMN decision modeling. You find the existing "Will Visual Paradigm support DMN any time soon?" thread with 3,780 views. You read the 8 replies to see whether anyone from Visual Paradigm responded and what they said. If the thread is unresolved, you post your own concrete use case in Feature Suggestions and tag it. You then watch the ChangeLog board for your version — that's where you'd first see it confirmed.

What you can and can't conclude

You can learn which versions have changelog threads, what users are requesting, and which gaps attract the most attention (DMN's 3,780 views is the standout in the visible data).

You can't treat any thread as a delivery commitment, infer pricing or licensing terms from the forum (the excerpt shows a "New free version?" and a "Licença Starter Marca de Água" thread, but no pricing details), or assume a suggestion will ship. For anything binding — pricing, licensing, support terms — go to Visual Paradigm directly rather than relying on forum threads.

forums.visual-paradigm.com is the discussion community for Visual Paradigm, the UML and modeling tool suite. It is a place where users post questions, report bugs, suggest features, and discuss modeling topics such as UML, BPMN, SysML, ERD, and code engineering. If you use Visual Paradigm and want to troubleshoot an issue, request a feature, or see what other users are dealing with, this is the site to browse or post on.

What the forum covers

The board is organized around product areas and topic types. From the visible topic list, the main categories include:

• UML modeling — class diagrams, sequence diagrams, activity diagrams, and related notation questions
• How To — step-by-step questions about using specific features
• Bug Reports — reproducible problems with the software
• Feature Suggestions — requests for new capabilities
• General Questions/Discussions — broader topics like memory limits, licensing, and AI features
• ChangeLog — release notes for Visual Paradigm versions
• Code engineering / database — DDL generation, ORM support, and related tooling

What you can do there

You can read any topic without an account. To post, reply, or start a thread, you register and log in. Typical actions:

1. Search or browse existing threads before posting — many common questions (memory settings, import formats, diagram rendering) already have answers.
2. Start a new topic in the appropriate category, describing your Visual Paradigm version, build number, and steps to reproduce.
3. Reply to existing threads to add your experience or ask a follow-up.
4. Track activity — each topic shows reply count, view count, and the last activity date.

What kinds of questions appear

The visible threads give a sense of the range:

This mix shows the forum is used both for practical troubleshooting and for forward-looking product discussion.

How it relates to Visual Paradigm

The forum is the community-facing discussion space for the Visual Paradigm product line. It hosts official release information (ChangeLogs) alongside user-generated questions and answers. It is not a documentation site or a support ticket system — it is a threaded discussion board where users and, at times, staff or experienced community members respond.

When to use it

Use the forum when you:

• Hit a bug and want to check whether others have seen it
• Need a workaround for a specific feature or configuration
• Want to gauge interest in a feature before requesting it
• Are looking for release notes and version changes
• Want to see how other users handle modeling or code-engineering tasks

If you need guaranteed vendor support or a formal response, a discussion forum is not the right channel — but for community knowledge and peer troubleshooting, it is the place to start.

The Visual Paradigm forum at forums.visual-paradigm.com is an open discussion board for anything related to Visual Paradigm's modeling, code engineering, and product usage. Based on the visible topic list, discussions fall into four broad areas: UML and other modeling notations, code engineering and database work, product usage and troubleshooting, and feature suggestions or version updates. You can post questions, report bugs, or propose features in any of these areas.

Modeling and diagramming

This is the most active category. Topics cover both specific diagram types and general modeling questions.

• UML class diagrams — for example, how to link an attribute of a class within a class diagram.
• Sequence diagrams — including formatting issues and notation questions.
• Activity diagrams — such as initial and final nodes appearing white or invisible, and interruptible activity regions.
• ERD and database modeling — including synchronizing roles to a class diagram.
• BPMN — for example, default tagged values not being applied to tasks imported from BPMN 2.0.
• SysML — including whether SysML v2 support is planned.
• Textual analysis and glossary — questions about the workflow between textual analysis and glossary, and how Synonym/Ignore behaves.

If you are unsure which notation fits your problem, posting in the UML modeling or General Questions/Discussions section is a reasonable default.

Code engineering and database topics

The forum also hosts threads on generating code and database artifacts from models.

• DDL generation — for example, generating DDL for BigQuery.
• ORM and framework support — such as questions about Hibernate and Spring Datasource versions.
• API import — for example, importing a Swagger YAML file into Visual Paradigm.
• Synchronization — changing from a role when synchronizing to a class diagram.

These threads tend to be practical: you describe the model or file you are working with, the tool version, and what output you expected versus what you got.

Product usage, installation, and troubleshooting

A large share of activity is about getting the software to run and behave as expected.

• Installation and launch — for example, being unable to launch Visual Paradigm Community Edition (Version 16.1, Build 20200601).
• Login issues — such as logging in with Google not working.
• Memory configuration — for example, how to use more than 2 GB of max memory.
• Display problems — Cyrillic characters showing as ?????? in the Postmania web interface (Visual Paradigm Server 18.0).
• Editor behavior — selecting an element and opening the specification editor in VP Online.
• AI features — questions about the AI model privacy policy.

When reporting a bug, include the exact version and build number, your operating system, and the steps that reproduce the problem. The visible bug reports follow this pattern, which makes them easier for others to confirm or answer.

Feature suggestions and version updates

The forum has dedicated sections for forward-looking discussion.

• Feature Suggestions — for example, editable diagrams in MS Office form, an additional default black-and-white UML format, and SysML v2 support.
• ChangeLog — release notes threads such as Visual Paradigm 18.1 ChangeLogs and Visual Paradigm 18.0 ChangeLogs, where you can see what changed in each release.
• General Questions/Discussions — broader topics like DMN support, a possible new free version, and licensing questions (for example, a Starter license watermark thread).

How to choose where to post

Before posting, it is worth searching the forum for your version number or feature name, since threads such as the memory question and the Swagger import question have accumulated many replies and may already contain your answer.

The Visual Paradigm forum at forums.visual-paradigm.com is the official community space for users of both the free Community Edition and the paid editions (Standard, Professional, Enterprise). Threads there show a consistent pattern: Community Edition users hit specific walls — watermarking, feature gaps, and licensing terms — while commercial users discuss configuration and workflow questions. If you are deciding between editions, the forum is a useful record of what actually breaks in practice. Note that the forum itself does not publish a pricing table or feature comparison; those details live on the main Visual Paradigm site, so treat forum threads as experience reports rather than official specifications.

What the forum structure tells you

The forum organizes discussion into categories that map directly onto edition differences:

• Bug Reports — problems that appear in specific builds, often Community Edition
• How To — usage questions, frequently about features that exist only in paid editions
• Feature Suggestions — requests for capabilities not yet available
• UML modeling / General Questions — design and methodology discussion that applies across editions
• ChangeLog — release notes for each version

The category a question lands in is itself a signal. A question in "How To" about a missing menu item usually means the feature is edition-gated; a question in "Bug Reports" about a crash usually means a build-specific defect.

Community Edition limits visible in forum threads

Several recurring threads point to concrete Community Edition constraints:

Watermarking. A thread titled "Licença Starter Marca de Água" (Starter License Watermark) asks about watermarks appearing in output. This is one of the most commonly cited reasons users move to a paid edition — diagrams produced for external use carry a visible mark.

Version lock-in. "Unable to launch Visual Paradigm Community Edition Version: 16.1 Build number: 20200601" shows that older Community Edition builds can fail to launch, and users may not be able to simply upgrade within the free tier. The thread accumulated thousands of views, suggesting it is a widespread experience rather than an isolated case.

Memory ceiling. "How to use > 2G max memory" (13 replies, ~3,890 views) is one of the most-viewed threads on the page. Users trying to raise the JVM heap beyond 2 GB run into a limit — a practical constraint for large models.

Feature requests that imply gaps. "Is there a plan to support SysML v2?" and "Will Visual Paradigm support DMN any time soon?" (8 replies, ~3,780 views) are both long-running requests. If your work depends on SysML v2 or DMN, the forum shows these were still open questions as of the thread dates.

Login friction. "Why loginning from google doesnt work" (Bug Reports) and "AI Model privacy policy" suggest that account and AI-feature questions also surface in the Community context.

What commercial-edition users discuss

Threads from paid-edition users tend to be about how to do something rather than whether it is possible:

• "How to import a Swagger (yaml file) in visual paradigm" (18 replies, ~4,852 views) — a workflow question typical of Professional/Enterprise use
• "Generate DDL for BigQuery" — database engineering, a paid-tier capability
• "Version of Hibernate & Spring Datasource Support" — code engineering integration
• "How to change from role when synchronizing to class diagram?" — round-trip engineering between UML and ERD
• "Default Tagged Values are not applied to Tasks imported from BPMN 2.0" — BPMN import behavior

The pattern: commercial users are integrating Visual Paradigm with external tools (Swagger, BigQuery, Hibernate, Spring), which is where the paid editions add value.

How to choose, based on what the forum shows

Practical steps before you commit

1. Search the forum for your specific feature before assuming it is included. Use the site search with your feature name plus "Community Edition."
2. Check the ChangeLog threads (e.g., "Visual Paradigm 18.1 ChangeLogs," "Visual Paradigm 18.0 ChangeLogs") to see what shipped recently and in which edition.
3. Read the reply count and view count on a thread. High views with few replies often means the issue is unresolved or has no official answer — a signal to verify independently.
4. Post your own question in the appropriate category with your exact build number, edition, and OS. The "Unable to launch" thread shows that build number matters.
5. Confirm pricing and edition features on the main Visual Paradigm site, not the forum — the forum does not carry a pricing table.

Common pitfalls the forum exposes

• Assuming a feature is broken when it is actually edition-gated. Check whether the menu item exists in your edition before filing a bug.
• Upgrading a Community Edition build without checking whether the new build still launches on your system.
• Expecting AI features to behave the same across editions — the "AI Model privacy policy" thread shows AI behavior is a distinct concern.
• Relying on a feature request thread as a roadmap. "Is there a plan to support SysML v2?" had replies but no committed timeline visible in the excerpt.

The forum is most useful as a negative signal: it tells you where users get stuck. For positive confirmation of what each edition includes, use the official product pages and release notes.

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:

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:

1. Product and version — for example, Visual Paradigm 18.0 or Community Edition 16.1, plus the build number if you have it.
2. What you did — the exact sequence of actions, step by step.
3. What you expected — the behavior you thought you'd get.
4. What happened instead — the actual result, including any error text copied verbatim.
5. A screenshot or file — for visual problems like the thread "Cyrillic characters display as ?????? in Postmania web interface", an image makes the issue concrete.
6. 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.