In modern mobile applications, notifications are key to user engagement. The Proposal: I suggest introducing a comprehensive Advanced Notification Management system directly within the Low-Code environment of OutSystems. Key Features: Rich Media Support: Ability to easily include images, videos, and icons within push notifications directly from the Service Studio. Interactive Action Buttons: Adding custom buttons within the notification itself to allow users to take actions without opening the app. Advanced Scheduling & Throttling: Built-in tools to schedule notifications based on user time zones and to limit frequency (throttling) to prevent spamming. In-App Notification Center: A ready-to-use, customizable UI widget that acts as an "Inbox" within the app to store and manage past notifications. Why it matters: This feature will empower developers to create more engaging and interactive user experiences. It will be especially beneficial for apps where real-time updates and quick actions are critical for success.

The Forge component page should include more details, that allows one to judge the impact on and OutSystems factory without needed to install it first:Number of Application Objects (AO's)Number of integrationsPaid license required for a third party integrationExternal integrations overview (some components have APIs just to collect usage, this should be more visible.If it bootstraps data on publish (some components generate users, etc.)If applicable version of OutSystems UI used (OutSystems UI has a high rate of updates and deprecated functionality/breaking changes)Regards,Daniel

If a developer uploads a forge component, that has dependencies for other forge component, and that component is owned by another developer. When changes is applied to the dependencies like: discontinuing the consumed version, uploading a new version to fix issues, ... etc. Let the consumer know that changes had been made, to upload new version of their asset if needed.

The OutSystems UI should provide a moveable popup element. It could be the same existing element, but with the following features:A placeholder for the title and a placeholder for the main contentBeing able to change the position of the popup by clicking on the title and draggingOption to have or not a close button in the upper right corner (with customizable icon)Option to close on click out of the popup

Let's say that I want to sync Tickets, Ticket Types, Users and Queues. Tickets and Ticket Types are connected, so I want to join them in a first sync. Users and Queues are related, so I want to join them in a second sync. But, I want both syncs to start at the same time, so that I cut in half the processing time. Right now, even though the description of the TriggerOfflineDataSync action clearly states "Action where you can invoke OfflineDataSync asynchronously", the syncs run one after the other, as you can see in the browser network tab. Some of the syncs rely on endpoints that could take some time to respond, so not doing this concurrently makes our apps feel slow. Users will have to wait extra time to have data available to start working.

When dealing with mathematical calculations or complex queries it's easy to lose track of parentheses.Check the attached image for an example of highlighted parentheses on Notepad++.

The <span> that gets added around items in ListRecords causes a lot of issues with jQuery and other things. For example, we tried using a div with display: table-cell and it did not work because of this. J.Ja

The use of ReactJs in mobile applications not only allows a quick refresh of the screen but also makes the development process simpler, since it is not necessary to perform ajax refreshment explicitly. It would add value to Web applications

It would be helpful to be able to create multiple plans and schedule when they are being published or add them to a publishing queue.Our company has a large number of applications and we are running into the situation where we have so many applications its taking a long time to publish.  If we can split up the applications being published and schedule it to run in off-hours it would improve performance.Another case is we have multiple developers trying to publish to the same environment. Sometimes we forget to go back so the QA spends time waiting for all of the changes to be published for testing.

The OS Traditional Time Picker UI Pattern has the option to set an Interval The OS Reactive Time Picker UI Pattern does not have this option and defaults the Interval to 5 minutes. Adding in the 'Interval'-input to the Reactive UI Pattern as well will give us more control over the functionality of the pattern so that we can tailor it to our needs.