Basically I am an Front End Developer , When I Was Look Into The Guided Path They Have Only Short Course Available , Kindly Make It As Much More Detail By Adding Some Stuffs in Front End Course.

From what I’ve seen online, the main barrier preventing many companies from starting to work with OutSystems technology is the price of entry. I’d like to suggest introducing a new licensing tier with limited resources, but sufficient to run a real application in production. The goal is to enable smaller companies to deploy a fully functioning app, not just for testing, but in a live, real-world environment. This would make it much easier to demonstrate the true value OutSystems can bring to a business. Even with reduced resources, no high availability, and community support only, the ability to run a production-grade app could help change the perception of the platform and significantly increase adoption, especially among smaller companies and innovation teams.

 Issue: The Table Grid component in OutSystems is currently missing several helpful features found in the Data Grid, including the column picker. As a result, developers frequently resort to the Data Grid solely for offering column customization features, even though the Table Grid would be more suitable for less complex scenarios. Moreover, the Table Grid lacks a native feature to establish row gaps (spacing between rows), which would enhance readability and visual aesthetics in numerous situations. Concept: Upgrade the Table Grid feature by incorporating: A column selection tool enabling users to dynamically display or conceal columns. A row gap feature to manage spacing between rows for improved visual appeal and readability. Advantages: Lowers the necessity to utilize Data Grid for straightforward use cases. Enhances user experience via personalization and improved layout management. Maintains lighter pages that are simpler to manage while providing increased flexibility.

We found certain queries coming from clients and timers get stuck in IIS indefinitely, despite having timeouts. These queries were sitting in IIS without any way to know this until our environment was inaccessible and we had to reach out to support to resolve the issue. While this clearly is a bug, support stated they would not be resolving this issue and thus we should create an 'idea' for it. Truthfully, not an idea, a bug that needs to be resolved because it results in OutSystems environments slowing down over time, eventually leading to them becoming inaccessible, and customers don't have visibility into IIS. Additionally, as part of my 'idea', I would suggest the OutSystems website to reflect the fact that this can happen as statements like "Every web request done to an OutSystems application takes its time to process by the application server (IIS) and is ruled by a Request Timeout that prevents the existence of everlasting web requests", are false. Obviously such a change would only be necessary in the short term as ideally, this issue would be resolved, but until then statements of this sort on their website are lies.

More and more data is shared between teams in JSON format in addition to Excel. It would be great if we can get a new option to import/bootstrap data into entities based on a JSON format.I would expect the same functionality as the "Import New Entities from Excel..." option but then a JSON file as source.

Add a field Timeout on the tab Integrations on Service Center, this way I don't need to publish by Service Studio and Deploy the module to another environment.

Able to bookmark Documentation, Tech Talk, Dev zone Articles under My Profile.

As a developer, I would like the training platform to remember I removed the "subtitles" options, so I don't have to keep removing it every time I watch a new video.

Add a Basic Data Type named Timestamp that retrieve time in milliseconds, this way it is possible to calculate time or date time with milliseconds.This is very useful in audit or logs, or even in a transaction level situation when having multiple users using the same entities or records.There are some forge components to do that, but that will imply a server call, or extra logic to fetch this type ofdata.

Quality of Life Improvements in the ODC Deployment Cycle Dependency Overview, when deploying an end-user application, it’s helpful to see a detailed overview of dependencies that might compromise the deployment. While this is a valuable feature, it could be even more effective if it allowed direct interaction with those dependencies—such as clicking on them to initiate their deployment or making the process more seamless. Currently, if multiple core applications (e.g., 8 or more) must also be deployed, you need to manually track and list them, which can be cumbersome. Navigation During Deployment, if you decide not to proceed with deploying a specific application after selecting a revision, it would be useful to have an option to navigate directly back to the application selection screen via the left-side menu. At present, the process involves either restarting by going back to the “Deployments” screen or clicking "Back" multiple times, which is not ideal for efficiency. Improving Feature Toggle, managementFeature toggles are essential for enabling parallel development and hotfixes, aligning with best practices recommended by OutSystems. While it's possible to organize feature toggles using folders in the development studio, this structure doesn’t carry over to the cloud interface, where you manage toggle values. Improving toggle management in the cloud would significantly enhance deployment workflows, as it directly impacts the flexibility and control required during deployments. A last one that also goes hand in hand with the deployments are the secret settings that you might need for API's (just an example). Whenever you make use of a new settings or app that uses an existing api you will need to fill in the setting its value. Because they're secret and always filled in with a default prompt you can not tell that its value is already filled in and if it's filled in that it's correct. Obviously this is intended but it can make big deploys with multiple applications hard to manage. An easy way to fix this could be an 'updated on' field that shows when the value was changed if changed at all so you can easily see if you have already updated the value. Thanks in advance for all already made improvements. Kr, Owen