Hello everyone!
As we announced a few weeks ago, we are currently revamping the OutSystems UI framework by changing its code architecture, rethinking experience inside Service Studio and introducing new powerful APIs.
In this new version, we converted further 6 patterns.
With the evolution of the component, some of its features needed to be deprecated.
If you are currently using any of the following patterns, we highly advise you to migrate them to the new implementation to ensure that you are using our current stable version with bugs fixed and better performance.
New version of the ProgressBar block with the new architecture. [Learn how to migrate]
New action added to change the value of the ProgressCircle (SetProgressCircleValue)
New version of the ProgressCircle block with the new architecture. [Learn how to migrate]
ProgressCircleFraction was merged with ProgressCircle. Now you can cover the same use cases by using the new ProgressCircle.
New version of the Gallery block with the new architecture. [Learn how to migrate]
New version of the Rating block with the new architecture.
New version of the RangeSlider block with the new architecture. [Learn how to migrate]
New action added to change the behavior of the OnChange event (SetRangeSliderChangeOnDragEnd)
Now, Pips parameter is the new TickMarksInterval and has a new calculation method.
New parameter to add a floating label above the handler.
New version of the RangeSliderInterval block with the new architecture. [Learn how to migrate]
New action added to change the behavior of the OnChange event (SetRangeSliderIntervalChangeOnDragEnd)
You can expect news from us soon, as we continue to revamp the architecture of the framework. In the next releases, we'll gradually launch new versions of our patterns.
These patterns will be deprecated and new versions will be released in a near future (next 6 months):
Check more details about the new release in the Release Notes and download the latest OutSystems UI version.
Thank you for all the feedback you have been giving us. Keep it coming! 💪
Hi Jéssica.
When will the deprecated versions of these widgets be removed from OutSystems UI? Is that 6 months, a year, longer? I need this information for maintenance planning so we know what to expect.
And is there an easy way or report available that will show us all the locations where we are using deprecated widgets and actions from OutSystem UI? We have a good grasp on where we use what widget but in our 20+ application environment searching manually for deprecated elements is a huge hassle.
Greetings,
Vincent
Hi @Vincent Koning!We are not planning to remove the deprecated components. We can guarantee that the deprecation or limitation of the usage of components will not be done without a migration plan and advance notice.At this moment we don’t have any report that will show you all the locations where you are using deprecated components and we don’t have a timeline for that feature. But this is something that will keep in mind for future improvements.Thank you for your feedback!Best regards,Jéssica
Hi,
It's importante to keep the pace in evolution, but like @Vincent Koning write above, we need more information for planning the migration and accelerators to do the job.
I hope OutSystems will take this in mind.
Regards,
Pedro Oliveira
One more step. Thanks.
Thanks
In addition to normal controls, this version offers two special control types: tabbed and accordion. These are used to display grouped sets of data. To get started, add them to the list of available controls. Then just simply define how many items should appear per row and what styles should be applied.
Thats great.. improvement... keep going.
That's really great
Thanks..that's great!
Impressive!
Always looking for this kind of revamping for Frontend development.Thanks.
Cool Its great...
Hi Jéssica,
Thats great, I like time piker most.
Looking Great!