Given how REST API/SOAP Web Services still have “callbacks”… aren’t they basically the same as the built-in events we now have on screens and blocks?Why not provide consistent names ( Built-in Events and  Event Handlers ) and UI to them in Service Studio (and eventually in Service Center reporting)?Makes life easier for everyone if similar things have similar names!

While reviewing some BPT documentation recently I realised Processes still have “callback actions”… aren’t they basically the same as the built-in events we now have on screens and blocks?Why not provide consistent names ( Built-in Events and Event Handlers ) and UI to them in Service Studio (and eventually in Service Center reporting)?Makes life easier for everyone if similar things have similar names!

First off, when setting an entity as Public can the platform default the Expose Read Only to True following the best practices of the platform. This applies for other settings too and should be defaulted based on best practices.Please make provision for the platform to auto generate default wrapper action when an Entity is set as Public and Read Only as this takes much time and repetitive.

Hello everyone and the OutSystems team.I had a problem and posted it on the forum. There was a person who would like to make a Zoom call to help me. By the time he sent the message I had already resolved it, but I think that although he had taken a noble action to help me by holding a meeting, maybe it wasn't possible because I didn't speak his language.Just as OutSystems has been translating certifications to expand and make OutSystems accessible to people who don't speak English so well.My idea is that in the forum we can have a Tag with the languages we speak. That way we could see if a meeting with that person would be possible to solve the problem.I think this interaction with the members on the forum is cool. OutSystems doesn't have to be responsible for which meeting tool we use, everyone uses what works best for them. However the tag warning the language can help. Even in terms of filters. For example, if I know someone speaks Portuguese, I can respond in Portuguese and he will understand better in the native language.

Hello everyone,As I'm a new user here and Outsystems continues to grow its number of users I think that lots of people already desire to use the platform, manuals, videos and its transcriptions and etc in native language. A friend of mine started a guided path this week but he needs tools to help him learn in his native language.As Duolingo did, it would be great to have communities/groups to collaborate with translations.Would it be possible?Thanks for your time

A filter in the application page to find out which all application has some broken reference or warning.

Hi,If we are creating an index in a table with a lot of values (millons of records) and the table have a lot of usage (it´ s a core table and have a lot of actions reading and writting), the deployment fails creating a index with timeout error, and all the deployment it´ s aborted on stage 2.Also during the creation of the index the table have blocks and the users can´  t work.If the index include "online" attribute in the creation, all this problems desapear.Regards

Hi,It would be great if when create and index of a table we can chose the order of tenant_id column.Depends of the volumen of the data, the information (columns) and the filters you need, the order of the column inside the index it´ s high important. Sometimes, the better approach it´´  s put tenant_id in first place and we don´ t have this option (or we don´ t found).If we can select the order, performance is greatly improvedRegards.

Currently, the USER table does not enforce any required or uniqueness constraints except for creation date, is_active, and Id. It would be nice to enable mandatory or unique constraints on fields such as username, email or external_Id.Not having this ability makes it difficult to avoid creating duplicate users whenever someone has the same name as another user or returns to the organization after a period of absence.I understand that some customers consider duplicate usernames as a feature, especially in cases where a user can occupy multiple tenants. However, an option in the configuration tool, LifeTime or Service Center to add or remove these constraints in the database would be very helpful.

Currently, the following limitations exist for logging changes to user role assignments on the USER_ROLE table out-of-the-box.Making changes to the USER_ROLE table directly are not logged, nor does the table contain any columns useful for auditing such as 'CreatedBy', 'CreatedOn', 'UpdatedBy', 'UpdatedOn', or 'Is_Active'.Assigning or revoking roles using role actions built into the Users module generates logs in the General Log tables, but the message is string that requires additional parsing to extract information, such as the usernames of whomever assigned the role and to whom it was assigned.Changes to assignments in the USER_ROLE table should be logged automatically in a dedicated logging table, regardless of source. Adding additional audit columns to the existing table would help too.