Hi everyone!We use cloning modules for developing features that after get merged into the original module.When publishing a cloned module, Service Studio publishes it to the application "Independent Modules". We then need to go there and move it to the correct application.It would be helpful that when publishing a cloned module, Service Studio would ask in which application the cloned module should be placed.--Tiago Bernardo

It would really save time if there was the ability to navigate from a widget that uses an action as an event handler straight to that action rather than having to look at the widget for the name and then find that action manually on the screen. Some sort of button or double click functionality to be able to click on that action in the widget and then that takes you straight to the scree/client action.

It would be helpful to have a system where if a user asks a question and it remains unanswered for 7 days, an email notification is sent to the user asking if their query has been resolved. If it has, they can mark it as solved. If not, they can seek further assistance.

 On version 8.0 you have the 2-Stage Deploy option and configuration on the Environment Configuration:It would be nice to have one setting available when you are about to publish one solution to ignore the 2-Stage Deploy for the respective solution or vice-versa.This would be very useful if you only want to apply this feature for a specific solution or project.It would be nice to have a setting per solution to apply by default the setting defined on the environment  configuration, or to set for always make use of the 2-Stage Deploy  or to never use the 2-Stage Deploy  for that solution.

Create a dashboard in OutSystems that responds to voice commands using the browser-based Web Speech API or other third party voice libraries to control UI navigation, form inputs or logic actions.

Hello, I would like to suggest about sending email to the poster of a post on forums that doesn't get any answer for a period of time for example 2 weeks. This email may suggest for the poster to either edit his post and explain his issue in more details that may help community members to understand the issue more and contribute for a solution, or if he got his issue solved he may add answer to his post about how he was able to fix it. Otherwise this post can be closed automatically after 2 more weeks.

 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

(It is different, but alike to https://www.outsystems.com/ideas/10924/improve-crud-wrapper-generator/ )When working under architecture, we work in different modules which inherit. (E.g. BL inherits CS). This is mostly done using wrappers, which have to be made by the developer.As far as I understand @João Melo wants a right click option on the Created CRUD action of an entity. Which helps speeding up development on that part.But when working in multiple architecture layers, you still have to create actions in the other modules by hand.It would save a huge amount of time when we could select a function in a referenced module, right-click on it, and select an option "Create Wrapper Action". Which would trigger a wrapper function with the same input/output and include the original action.This is not limited to Entities, etc. But could be used on any Action/Function/Service Action/etc...It would be even greater if we could create the wrapper with a selection of optionsCreate Action WrapperCreate Service Action WrapperCreate Rest Service Action Wrapper (kinda more difficult because of the existence of the producer settings)Bonus Idea(Not limited to the wrapper, but also on input/out parameters of inherited types):When we inherit or use an existing item, Architecture dashboard want public action, input/output parameters, etc to have a description. The descriptions can be defaulted based on the action, and when available, why not copy the original description. An EntityId description is usually the same as the input parameter description of the instance. You can change it, if it is different, but 99% the original description (and the name) are fit for business

Continuing on the good pattern of Service Studio warning about unused elements, also address the unused private web blocks.

I find it very useful to have "Previous Screen" as destination on Mobile. But why don't we make it level? Make it available on Web too.