It would be helpful to be able to search for errors on specific modules. Now it's only possible to select 1 module. By having a multiselect, it is possible to check on 2 or more modules that you are interested in at the same time. The other way around, you can "select all" and then deselect a module that is having a lot of errors (which is troubling the error logs) to be able to find the errors you are interested in more easily. The same would be for the application search. Same request is useful for applications dropdown

In the forums, it should be forbidden to post answers that only state that the OML file has been modified. A textual explanation of what has been fixed in the OML file should be mandatory. This way, people can learn something without having to search through the source.

There are currently 3 ways (that I remember) of deleting assignments in Service Studio: Variable assignments can be deleted with CTRL + D Unused inputs can be deleted with Delete Events can only be deleted by deleting the text I think the same shortcut should work for all three.

Libraries always seemed to me like a good place to upload some resources like images and fonts. When trying to place fonts, I ran into a problem of not being able to set the deploy action to "Deploy to Target Directory", as the option is blocked. Could this restriction be lifted?

Many web service specifications display its CURL calling command.It would speed up the process to consume these REST calls in OutSystems if there was a way to given a CURL command, OutSystems will generate the REST API web service consumption in Service Studio (similar to the "generate structure from JSON" feature).

So that's pretty much what's on the title. If I create an attribute named Is_Active or IsActive (which will, by default, be a boolean value), set that as the "Is Active Attribute" property of the entity.Maybe the same for the Order By  - if we create an attribute named Order.For Label, it doesn't seem very straightforward so I'll keep that out :)

If I want to create an auto refreshing dashboard, I define a "setInterval()" using a JavaScript node that targets a client action that refresh a DataAction or an Aggregate, to simulate auto refresh behavior. We can add input to DataActions or Aggregates that contains the time interval for auto refresh to do said behavior.

This idea suggests an automatic logic narrator that translates server actions, conditions, and flows into clear, human-readable explanations. This would help non-technical stakeholders, new developers, and auditors understand what the application is actually doing without diving into implementation details. It would also serve as living documentation that stays in sync with the application logic.

An entity foreign key attribute has a Delete Rule property which can be set to Protect, Delete or Ignore by a developer in ServiceStudio. A Performance Best Practice is to set this to Ignore, but that could lead to database inconsistencies. Therefore, during development, it is safer to use Protect. This means developers need to remember to set this rule to Protect during development and then to Ignore after testing has been completed and before deploying to production if they want to conform to this Performance Best Practice.You can imagine this process is prone to errors. So how cool would it be if you could set a Platform Default Delete Rule per environment in LifeTime or ServiceCenter and then be able to select 'Platform Default' as the Delete Rule in ServiceStudio?So, for example, in DEV & QA the Platform Default Delete Rule could be set to Protect and in PRD it could be set to Ignore using LifeTime or ServiceCenter. Then, when a developer chooses 'Platform Default' as the Delete Rule on a foreign key in ServiceStudio, the platform makes sure that the Delete Rule is set to Protect on the database when Publishing/Deploying to DEV and QA and that the Delete Rule is set to Ignore on the database when Deploying to PRD. So the platform automatically sets the Delete Rule on the different environments according to Performance Best Practices!

There are some requests regards Time related actions should support timezones, but I think the changes should be more radical, the DateTime date type itself should be updated in two ways:Support Offset or Timezone informationSupport Milliseconds for more accuracy