Home > Forum > General > WEBCON 2025 Changelog / Release Notes - What's your favourite?

WEBCON 2025 Changelog / Release Notes - What's your favourite?
0

MVP

As 2025 version have been released, we've got a new changelog to read through: https://webcon.com/wp-content/uploads/2024/11/Changelog_2025_1_1_23_EN.pdf

What are your thoughts on changes? Which ones are yours favourite? :)

For me - ALL TRUE, and ANY TRUE operators sounds great! So many nested boolean logic to update ;)

MVP

If I have to name one favorite than it's the form rules to determine the visibility of item list row actions, while the phases and actors are just behind.

But it's really hard there are many interesting changes.
Therefore I put together an "excerpt" which is of course subjective. :)
https://daniels-notes.de/posts/2024/webcon-bps-2025-change-log


@Mansoft
The first version of anything will always have some flaws, but we need to start somewhere. Of course, you are free to wait until those are addressed, but if you don't want to mention them, then some of those may get unnoticed and they will still be there, when you test it the next time.

But I have to comment on this "You've put your fingers in something you shouldn't have changed. You don't change a good horse when it's winning."
This is your subjective impression as a WEBCON user. As a partner I can offer a little more "objective" feedback. During the last year we got a regular comments regarding the (out)dated UI. This even forced us to create our own theme, which we can now get rid of / need to review. Yes, existing users will have to get comfortable with the new UI and I agree that a the screen "real estate" has been reduced even further, but a change had to come. At some point you need to switch to a fresh horse, even if it hasn't has any race experience yet. The old one was slowly but steadily dying.

MVP
In reply to: nobody

.

I'm sorry that I did not get across the reason, why I used "objective".
I used this word, not because we are a partner, because we already spend hours to modify the UI because we received numerous negative feedback. So, I used "objective" in quotes from a quantity perspective.

That's the only reason I used this word. Even if this my sound strange, but I wouldn't have minded keeping the old "UI" alive. I'm more focused on functionality than "looking pretty". Which I heard complains about more often than not. :)

I'm also experimenting with a "full screen" functionality at the moment because I don't like how much space get's lost, which I also voiced using another communication channel. So, yes while I'm definitely biased I also point out flaws or things I don't understand.

Quote from my blog post about the change log of 2025:
New Workflow designer
"Hidden no longer means hidden :( At least in this version, let’s cross our fingers."

While I agree with some of the mentioned issues, I haven't verified others, at some point a version needs to be released. This is also something everyone of us here propagates when building new processes/applications. Create the first working version, and build up on it afterwards.

Off topic:
I have the feeling that suggestions from customers are more likely to be heard than those of partners. We don't pay the bill. This is also something I voiced in some discussions and I never got a response. So I may be right. :)

In reply to: Daniel Krüger (Cosmo Consult)

I'm sorry that I did not get across the reason, why I used "objective".
I used this word, not because we are a partner, because we already spend hours to modify the UI because we received numerous negative feedback. So, I used "objective" in quotes from a quantity perspective.

That's the only reason I used this word. Even if this my sound strange, but I wouldn't have minded keeping the old "UI" alive. I'm more focused on functionality than "looking pretty". Which I heard complains about more often than not. :)

I'm also experimenting with a "full screen" functionality at the moment because I don't like how much space get's lost, which I also voiced using another communication channel. So, yes while I'm definitely biased I also point out flaws or things I don't understand.

Quote from my blog post about the change log of 2025:
New Workflow designer
"Hidden no longer means hidden :( At least in this version, let’s cross our fingers."

While I agree with some of the mentioned issues, I haven't verified others, at some point a version needs to be released. This is also something everyone of us here propagates when building new processes/applications. Create the first working version, and build up on it afterwards.

Off topic:
I have the feeling that suggestions from customers are more likely to be heard than those of partners. We don't pay the bill. This is also something I voiced in some discussions and I never got a response. So I may be right. :)

.

MVP
In reply to: nobody

.

I will also only add one comment, because I asked someone via LinkedIn, what's his opinion:

Quote: "
My Boss is delighted, i updated my personal dev
a lot more possibilities to create more modern start pages for apps

like it also as we all working on office365 and design is familiar
i showed it to my friend and he told me that it looks almost like dynamics 365 :)

"

@All
After Mansoft and I went off topic, please focus on Maks question. :)

Dear Maks,
Thank you for sharing these ideas; they both look very promising.
Personally, I believe the simpler features also hold significant value, such as adding more content options on the application page—like text blocks, graphics, embedded elements, or HTML code.
These additions could enhance flexibility and improve user engagement.

MVP
In reply to: Adam Hatak

Dear Maks,
Thank you for sharing these ideas; they both look very promising.
Personally, I believe the simpler features also hold significant value, such as adding more content options on the application page—like text blocks, graphics, embedded elements, or HTML code.
These additions could enhance flexibility and improve user engagement.

I would also add to this the new possibilities for customizing the menu and the dashboard filters. Although the new way, from a dev perspective, may seem a little more confusing at first, it now allows for a much more intuitive and friendly UI/UX.

The new functionalities have added some complexity for the developers but much more flexibility for the customer's needs. It's way easier as a dev to screw it up, but if done properly the customer will end up with better results. We need to revise our internal development processes and practices now, but if we can offer more value, we don't mind.

MVP
In reply to: Razvan Ogrezeanu - ENCORSA Romania

I would also add to this the new possibilities for customizing the menu and the dashboard filters. Although the new way, from a dev perspective, may seem a little more confusing at first, it now allows for a much more intuitive and friendly UI/UX.

The new functionalities have added some complexity for the developers but much more flexibility for the customer's needs. It's way easier as a dev to screw it up, but if done properly the customer will end up with better results. We need to revise our internal development processes and practices now, but if we can offer more value, we don't mind.

I have to agree that Dashboard level filters are something that i've been really missing (I've some experience with Tableau where it is an obvious feature).
It closes the gap to BI system, and allows to achieve more in WEBCON itself which is great for smaller companies not having BI tools.

On the UI change offtopic though - I get why many people might be upset about it, especially when applications have a lot of UI customizations.
This is why i always try to avoid it as much as possible - it's the platform that decides how things should look, we are paying for not having to deal with it.
UI / UX designers should deal with it, and delivering Fluent 2 designed by Microsoft is from my perspective really smart, as it aligns perfectly with Windows 11 UI, and all the Office apps stack which is still default in most corporations.

MVP
In reply to: Razvan Ogrezeanu - ENCORSA Romania

I would also add to this the new possibilities for customizing the menu and the dashboard filters. Although the new way, from a dev perspective, may seem a little more confusing at first, it now allows for a much more intuitive and friendly UI/UX.

The new functionalities have added some complexity for the developers but much more flexibility for the customer's needs. It's way easier as a dev to screw it up, but if done properly the customer will end up with better results. We need to revise our internal development processes and practices now, but if we can offer more value, we don't mind.

@Adam
The elements you mentioned have "always" been there. I mention this just in case you need to use them in an older version. ;)


Yes the new options we have to define in the navigation is really great.
I added my first idea for "migrating" to the new one. Maybe we can share our ideas regarding a good "default" navigation structure. As Razvan mentioned, we need to define new guidelines now and a joint effort may help everyone.
Regarding the navigation grid: There's currently an issue with the translation, old ones may get lost, if you update the translation of a single element.

I also like the the option to define multilingual texts on the dashboards. Another workaround we can now scrap. :)