Hi guys, I've got a small idea that I'm hoping would help both Companies looking for experienced certified Outsystems developers and unemployed Outsystems Developers looking for new challenges and opportunities. Case Study My name is Munyaradzi Kandoro and I am a certified Outsystems Developer and Architecture specialist with over 4 years of experience and currently open to work. At the moment, companies looking for experienced developers on the market would not be able to find people like me. If they are looking for people like me, they will have to rely on the services of LinkedIn where they will need to filter through unwanted information in order to find the right talent. I believe it would be a good idea to bridge the gap between these 2 parties by providing Companies/Partners with a Dashboard/list to view and be able to reach Outsystems to Certified Outsystems Developers. Please let me know what you think. Thanks

In Service Center, it could be useful to have the Module Type in the module detail page.Also in the modules list screen, it could be useful to have a filter option on Module Type.

Forge needs more collaboration features, so that changes can be submitted easier. The only interaction possible is to post a question in the forum or apply to be a team member. The other option would be clone the component and submit a new updated component to the forge.Allow users to submit changes, that would be approved by the component teamAllow users to explicitly fork from existing component, there would be a visual indication of the "source" componentBasically make Forge a bit more dynamic and github-ish.

In the screen shot below, I'm trying to quickly see where in the Screen Action/ Server Action the variable named LeadBroker is being used. I'd like to click on the variable name so that it is selected on the right and then each node in the left where the variable is referenced would highlight on the screen so I can quickly see how/why it is used there.Find Usages here works well, however if there are many usages on the screen, it can be difficult to quickly see all the nodes.This feature will save a lot of time when we want to assign another property of a variable or something like that.

I'd like to see a checkbox/property on Simple Queries to allow them to use the NOLOCK hint (or Oracle equivalent) for those who are willing to accept the possible consequences. The majority of our queries could be done without locking and this would be a big performance boost. J.Ja

We are using OutSystems with Remote connection in a client. When we click on Modules Tab in Service center we need to write the right name of the module if not the format of the modules page stays broked. Please improve this page to be more user friendly and have a good experience for OutSystems developers. Thank you very much! Best Regards, Paulo Russo. www.paulorusso.pt

Currently, entity actions in OutSystems update all columns of a record, even when only specific attributes need to be modified. It would be highly beneficial to introduce an entity action that allows updating selected columns only, similar to an SQL UPDATE statement. For instance, if I need to update only a user's mobile number, I should be able to pass the user ID and the new mobile number alone, without requiring the entire record. This approach would: Simplify the implementation. Improve performance by avoiding unnecessary updates to other attributes.

 Nullish coalescing operator (??) is a logical operator that returns its right-hand side operand when its left-hand side operand is null or undefined, and otherwise returns its left-hand side operand. This is widely supported and a great productive boost for those of us writing javascript in OutSystems. The problem with using this in OutSystems is twofold: the javascript editor considers it as a syntax error it is not possible to publish a solution that includes a module that has a javascript using this operator Could this be improved? Thanks, Tiago

I'd like to be able to generate a REST API automatically from an entity.  The API should support search/filter, sort, pagination and CRUD operations. Once the API is generated, I'd like to use it with scaffolding patterns to create web screens. This would make implementing a three tier application architecture much easier.

Currently interaction with other forum users is not a chat style like social media, but sending individual messages.In the same way a floating chat icon exists for support (image below), a chat feature with other users would be a great add to the community.