We are expecting a solution, to not take dependency of source application but it will have only pure code with errors.In this case we can avoid unnecessary dependencies. Or we can ask user as a confirmation when paste the code like,  "Do you want to copy only code or with full dependency?".This will solve many problems.Thanks.

Currently, when dragging a table to create an interface using scaffolding, two screens are generated: one for the record list and another for editing. This results in the use of two application objects. Would it be possible to support a master-detail pattern using a single screen for the record list and a popup for editing or inserting a record?

As the community grows, we get an increasing number of inactive users.As natural as that is for any social network, that also means we'll have an increasing number of outdated Forge components .I believe that goes against the goals of helping the community with brand-new, cutting edge components.Whenever I find a component that I'd like to use, but it's old and/or deprecated, I try to convince their authors to add me onto their team so I can update it. A recent example is the CodeMirror component , which stopped receiving updates since platform version 7.However, that does not always work. If the author of a given component went inactive, his/her component lays there forever and nobody else can update/improve upon it.An example is the TinyMCE component, for which I tried to contact its author asking him to accept me into his team so I can update it ; since I didn't hear back from him, I had to upload a separate component named InputToTinyMCE, ultimately splitting the same plugin into two components and forcing the community user to decide which of the two should be used.I have a couple of suggestions to overcome this situation which I expect to become more and more common in the future years.Disable components (so that a new one can be created with the same name) that do not have a version compatible with the latest 2 major platform versions (e.g. P9.1 and P10) -- after giving a prior notice to its author(s).Allow other users to join teams whose components haven't received new versions in a while (maybe taking into account a minimum required community rank or forge score for security reasons).If items 1 and 2 are not applicable: any other mechanism that allows new users to contribute to "dead" components that may clutter Forge in the long run.

Currently, in MultiLanguage OutSystems applications, exporting Excel files in the correct language requires workarounds. The issue arises because structure labels are fixed and not stored in Multilingual Locales, making dynamic translations difficult. Current Problem Structures support only a single label value, preventing automatic localization. Labels are not included in the translation system, requiring manual mapping. Developers must create custom solutions, increasing complexity and maintenance efforts. Proposed Solution Link structure labels to the translation system: Store column names/labels in Multilingual Locales files Dynamic export support: Automatically select the correct translations based on the user’s language setting. Benefits Reduced complexity: Eliminates workarounds for translation management. Improved maintainability: Simplifies language handling in exports.

Looking at: https://success.outsystems.com/Documentation/11/Reference/OutSystems_Language/Logic/Built-in_Functions/Math#Roundmeans that when you round in the code versus round in an aggregate you can have different output.This is horrible to work with.Therefor I suggest to add a optional parameter to Round to provide how you want to round, so we can make the aggregate and code consistent without having to build some weird workarounds.

 https://www.outsystems.com/ideas/2555/Unused+variables%2c+actions+or+functions+should+give+a+warning+on+TrueChangeFollowing up this idea, it would be expected to have the same behavior on unused Session Variables  and Site Properties

Sustainability and green IT is becoming more and more important for our customers and it's our responsibility as a company to help them build more sustainable applications and reduce the carbon footprint of the applications.According to this Forrester report "It’s 2020, and the industrial sector can no longer ignore the mandate for environmental sustainability. This is especially true for technology."There are many ways to do that but one possibility is to detect and report bad practices (or areas of improvement) in Architecture Studio. Several articles describe how to improve the carbon footprint of the app: https://gr491.isit-europe.org/en/ https://greensoftware.foundation/articles/10-recommendations-for-green-software-developmentEven though a lot of recommendations are pertaining to the organization, methodology, specification, etc. there are several elements we could try to detect:size of the images, videos, too big compared to the actual size of the area where they are displayed on the screenunused pieces of logicdetect unused screens of featuresdetect unused data (aggregate that retrieves data that are not displayed)etc.

When I'm calling with Outsystems support I always hear the same music Although the piano concert when i'm on hold is OK, it can use some variation.Perhaps cello or violins for a change?

It would be nice if there was a native way to call screen actions from JavaScript.Currently the best way to do this is to create a hidden button with the intended action and then clicking it from the JavaScript.I was thinking this could be achieved by creating a JavaScript function call attribute of the screen action. Similar to how Widgets have a .Id attribute, actions could have something like a .JSFunction attribute that could be included in JavaScript that would then start the screen action.

Dropdown Tags widget puts a margin at the end of the selected value, in order to create a buffer between the value and the action in the end. However, in pages with right-to-left direction, the margin is not reversed, it remains the same. It may cause an issue of the selected value overlapping the widget actions. Here is an example of LTR & RTL pages: English Arabic