Add an option to include a disclaimer message in the email body if the e-mail was sent with Redirect Emails To Test List: TrueIn some use cases the default sender is not empty, so is difficult to understand if email received, was sent to the redirect email test list.

It would be great if you had the possibility to download an application (.oap file) directly from Service Studio, with no need to enter Service Center:

Since early 2023 we have support for using multipart/form-data, as a result of this idea . Helps us to handle multiple documents in REST services. It would be great if we can also expose a REST service that takes multiple documents as input parameters. Currently Service Studio is blocking that. After adding the second parameter of type Binary Data , we get an error (see screenshot). It would be nice to get support for multipart/form-data in exposing REST API's, so we can also build API's that handles multiple documents using our favorite development platform.

Hi Team,It will be better if we can add Stacked Icon  in Reactive Web and Mobile apps.Thanks & Regards,Ramesh Sirvi

 Problem: Separately listed demo/sample Forge components can be mistakenly used by developers in production and dilute the visibility of the actual core component. Solution: Integrate demos/samples as sub-listings within the parent component's Forge page. Benefits: Improved discoverability, reduced confusion, streamlined experience, better organization, and easier maintenance.

The user should be able to copy multiple property names for documentation porposes.ie: select multiple properties from a structure (using something like ctrl + click in each property), and then have a context menu option to just copy the property names as text.That way, the name of the porperties can be pasted in a text editor so we can document their functionality. Example in the screenshot attachedThe only workarounds i can think of are: - Copy paste each property individually (Very time consuming when you have a lot of structures/entities/variables)- In the case of entities, query Outsystems' System tables to get the property names (It really isn't that user friendly for something so simple)

Despite the availability of model question papers, many candidates find them insufficient for robust preparation for OutSystems certification tests. To better equip candidates, OutSystems should provide extensive MCQ samples, such as a set of 1,000 solved questions. This extensive practice would allow candidates to: Thoroughly Understand Question Types: Candidates can familiarize themselves with the variety and format of questions typically asked in the certification exams. Improve Problem-Solving Speed: Regular practice with a large number of questions helps candidates develop the ability to solve problems more quickly and efficiently. Identify Areas for Improvement: Candidates can recognize and focus on areas where they need more practice or deeper understanding. With ample practice, candidates can approach the test with confidence and increase their chances of passing on the first attempt. Providing such resources demonstrates OutSystems' commitment to helping their users succeed in their certification endeavors.

I have an 011 Screen Aggregate where I join with an employee Entity from another (HR) module. I only use the employee name Attribute on the screen. Although all other Attributes returned are set to Null in the XHR response (which is great), all the attribute names are present. This exposes the data model of this other HR module, and also that sensitive data is stored there such as the employee birth date and employee address. So the sensitive employee data is safe, but the (application) data model is not. I would also like the unused part of the (application) data model to be hidden.

Create the system actions ListSum and ListAverage. The input could be the name or index of the column I want to sum or calculate the average.More util actions like ListFilter and ListAny

From Service Studio, directly from the tables, there could be the option of creating an API exposure (REST or SOAP), with all the necessary methods from the server actions (CRUD) associated to the tables. In this way, the creation and exposure of APIs for data access is accelerated.