What the Visual Paradigm Forum Reveals About Updates and Feature Requests

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.