Can we have the possibility to publish rest services with openapi3 definitions, alongside the current swagger definition?

When I click Skip while a BPT Activity is actively running, it redirects me to the error screen of Service Center.It's understandable that you shouldn't be able to simply kill an Activity when it's active. It can be hard to do so technically, as well (it might be trying to fetch some data with a bulky query etc.)However, I would expect that when I click Skip, BPT determines that this activity shouldn't run again in case of an error or timeout.So if it finishes without errors, then it's automatically skipped anyway.If it doesn't finish successfully, I expect it to be skipped automatically at the end of the current run since I clicked Skip.I imagine a new attribute for Activities such as ' IsMarkedToBeSkipped ' under the hood.If this is not possible at all, then I at least expect the Skip button to be disabled when an Activity is active, because it redirects to the error screen anyway.

Upon variable deletion, prompt the user with a confirmation message: 'Do you wish to remove all instances of this variable throughout the application?' This streamlines the cleanup process, saving time and effort while maintaining code integrity and preventing unexpected errors.

In Mobile Apps, Service Studio shows what Screen is the Home Screen by a special icon. In Web Apps there is no such icon, so it can be a surprise what Screen is opened when pressing the blue "Open in Browser" button.It would be swell if Service Studio would indicate what Screen is opened, with an icon similar to the Mobile one.

There should be a way to easily go to the most used screens within an e-space.

Allow users that downloaded a Forge component to tag the component with "successfully implemented". This can then be used to display the number and percentage (successful / downloads) of users that actually got the component working on the Forge. This could be displayed next to the rating.The success score could also be added to the filter. For example, show only components with a success score > 50%.Optionally, allow a user that successfully implemented a component to indicate he/she can be contacted for help. These people could then be listed under the support tab of the component.

I almost never want to use "DateTime_PrettyFormat", it's a big hassle to have to keep noticing it and deleting it. It should not be used by default on every date/time attribute that gets dragged onto a form.J.Ja

When migrating applications from OutSystems 11 to OutSystems Developer Cloud (ODC), static entities that originally used the IsAutoNumber feature lose this functionality. In ODC, every record in a static entity requires a manually assigned identifier, even if the entity was previously using AutoNumber in O11. This results in a time-consuming and error-prone manual process, where developers must assign IDs individually to each record in every static entity — especially painful when there are multiple static entities with dozens or hundreds of records.

On the Forums landing/list page we see whether or not the post has been solved. On the same landing/list page it would be nice to see the name of the person whose response has been marked as a solution.

Hello, Recently, one of my ideas was implemented, which made me really happy. I received a badge, which is great! However, unlike Forge downloads, implemented ideas don't contribute to your rank on the Community Leaderboard. Adding points for implemented ideas would motivate more people to submit valuable suggestions. So far, only 1,026 badges have been assigned, and awarding points could drive even greater participation and innovation. Thanks, Neha