Currently, when we end a screen action, it is possible to end it with a destination widget, open a new screen, in the same tab.It would be great a new option in this widget that, when set as true, it would open the new screen in a new tab.

When modeling the database or simply creating entities, it would be great if the platform suggested the creation of basic auditing fields, like CreatedOn, CreatedBy, UpdatedOn, UpdatedBy.Of course it shouldn't mandatory, and the platform should be smart enough to understand when the entity is a good case for these types of fields. That's why I'm categorising it as in AI/ML.Apart from that, it would be great if the platform set CurrDateTime() default value for CreatedOn.Some sort of integration with another popular idea around custom wrapper actions would be appreciated too.

I think it would be really nice to be able to have our user actions separated be categories, just like the built-in ones are. This would really help when you are creating big projects or when you're trying to consume from a project with which you are not completely familiar.

This aim of this idea is to propose a proactive, dual-layered security framework for O11 & ODC to ensure PII (Personally Identifiable Information) requirements on data model. The Manual "Is Sensitive" Flag Introduce a high-visibility Data Governance section in the Attribute Properties pane. Developers can manually toggle an "Is Sensitive" flag for attributes. Result: Data is automatically encrypted at rest using AES-256 and masked in all ODC Portal logs. The AI-Powered "PII Sentry" An integrated AI agent monitors the data model in real-time to catch human error. Pattern Recognition: When an entity is created or data is imported via Excel/CSV, the AI scans for sensitive patterns (National IDs, Credit Cards, etc.). Automated Action: The AI interrupts the workflow to suggest: "This field appears to contain PII. Should I enable the 'Is Sensitive' flag for you?"

Picking an Icon on mobile applications is really simple and visual. Can you please make it just the same on web applications?ThisInstead of this

Hi everyone, It would be great if we could text search a css class in the CSS like we do on adobe reader. With this I believe a lot of time could be saved. cheers.

Good afternoon, Everyone, I'm sharing a practical experience that can help those who work with sending emails with images in OutSystems, using Forge's CKEditor for Outlook and Gmail. Problem The CKEditor saves the image in the database and generates a link in the format: /Download.aspx?GUID=1234... In Outlook, this link was identified as a potential security risk (because of the .aspx) and the image was not displayed. An alternative would be to convert the image to Base64 and embed it directly in the HTML, but in this case Gmail does not interpret it correctly and the images do not appear. Solution I created a Friendly URL (alias) in the Service Center to expose the images in the format: /CKEditor/image/{GUID}.png I adjusted the CKEditor's JavaScript to save and retrieve images using this new handler. In the Download handler, I configured the FileName, Mime-Type, and left Save to Disk = No, ensuring that the images are displayed inline.

The Object data type can be used to communicate data to and from extensions, but isn't much of use otherwise. Furthermore, it is not possible to use an Object as attribute in a structure, and I'm not sure whether Objects should be possible in a List (they are, but kinda via a workaround, even as attribute). Also, many Forge components dealing with generic data force the user to use RecordLists, as there's no other way to alter data in an extension. My proposal:1) Allow structure attributes of type Object;2) Officially allow Lists (and Record Lists) of type Object;3) Have a FromObject function that reverses ToObject (and throws an exception when incompatible types are used), so extensions that manipulate generic data (e.g. XML Records) can output Records as well as Lists.An Object will never be a "first class citizen", but they have their uses, and the proposals above would make the life of the advanced developer a little bit better when dealing with abstract data.

Service studio's messages should have a timestamp. When we publish an eSpace and we make some changes and then save it, we can't know by the messages list if we already published it or not.

I'd like to be able to remove some attributes or connections from the Diagram without affecting the database. Only to make them more readable.Example: I'm analyzing entities related with User and all of them have an extra connection because of the CreatedBy field. I'd like to remove the field or the connection from the screen to make the diagram easier to read, but not to really delete it.I hoped this Hide/Show attributes in Diagram was what I was looking for, but I need more.