Hi,We work in a highly regulated industry and have an on-premise installation of OutSystems. It seems unlikely in an environment like this, any security department would open firewall connections and allow probes to send (unknown) data outside the organisation.Because of this, it would be wonderful if there could be an on-premise version of AI Mentor.I understand that this might lag behind the cloud version, but a version that got updated every month say would be very helpfulThanksRichard

Like we have the possibility to import from several sheets, it should be possible to export to several sheets of an excel file. There are widgets in "Component Downloads" tab that do this, so it could be easy to reuse it and integrate with Service Studio. Cheers, Nelson Freitas

We are facing many blocking issues trying surpass the default limitations of rest api on exception handling and standardization of responses.I have related all the scenário on this other idea where I'm suggesting to free some of the blocking issues we are facing. https://www.outsystems.com/ideas/6943/add-exception-handling-on-exposed-rest-apiTo be more precise here I will paste some of the content, as all of issues are blocking some solution.The lack of not having an error handler on exposed rest api block us on having a decent exception handling on rest api.In our case we are trying to implement and harmonize the behavior of our web apis on many platforms in many ways as:The standardization of responses and exception handling not only to status codes but the standardization of json structure of validations and error handling.Said that, we tried many things, all finding any sort of Outsystems limitations. PS:  We don'twant to do manual validation on all our actions and raise exceptions after manually change the status codes and duplicate the exception messages. It open for many breaks to standardization and falls in the message duplication of exceptions in OS as stated below. The exception approach: Exceptions in OS:Can't be public and can't be referenced between modules;Need to specify a exception message on all raises, causing non standardization and duplicationNeed duplication and I think duplicated one aren't caught on specific handlers with same name, only generic ones;Almost ten years ago Gonçalo Borrêga already suggested changes on this: https://www.outsystems.com/ideas/100/Allow+custom+Exceptions+to+be+public+and+referenced+from+other+espaces?IsFromAdvancedSearch=TrueThe default built-in exception handler of rest api returns almost all time a status code 500. Not the more adequate. Second try:Tried to use exception handlers in OnResponse rest api handler:But when it runs, the exception handler never runs;I made some helper actions on a helper module to get the standardization of status codes.With the helper centralized actions I could standardize the status codes at least, but can't make any sort of data validation exchange between action and handler, as there is no way to pass data do the handler nor made any changes to response out of the OnResponse handler. Then my Bad Request scenarios are not solved by this approach.At this point I can't detail to the client of my apis what not passed the validations.To complete this, the use of structures as parameters on api doesn't have mandatory and data type validations!I will cover all of the lacks on individual ideas and a forum post with all of it.Hope someone else can converge on need for some changes on this.Márcio.

In a Environment, we have System applications (Service center, Sample DB, Outsystems Maps) and User Created applications. I was looking for parameter to filter out system applications from User created application. I need a column in {system}.{application} Entity to find out this. Same applies to ESpace Entity also.

I would like to have the ability to filter errors based on their exception names, making it easier for me to identify and analyze specific types of issues in my application. Currently, we can define a Module Name when using the log message action. It would be beneficial if exceptions could inherently possess a similar capability by associating with their own names. This way, I could efficiently locate and address, for example, all Security Exceptions within my application.

 Hi, I am currently working on an espace with tons of warning/errors because of some refactoring. there is no way (afaik) to sort the messages on columns like priority/message/description/webscreen etc. filter on warnings only etc. that would be nice if we can do that. furthermore I would like to see that the last row "errors found" is always visibile instead of having to scroll down everytime

The current implementation of the available AWS Forge components from the OutSystems Platform Team only supports IAM user account credentials (Access Key and Secret Access Key) aka Basic AWS Credentials.With a growing consumption of AWS Services in OutSystems applications this can lead to either having to maintain (rotating keys asf) multiple IAM User account credentials or to an overpowered (in regard to permissions) single IAM user account. The AWS Forge Components developed and supported by OutSystems should support Temporary Credentials (Session Credentials) besides the now available Basic AWS Credentials . This will allow to use assumed role credentials. Using roles instead of dedicated IAM user account credentials is also recommended by AWS as best practice.The changes are very minimal as this would only mean adding an additional Property to the extension SessionToken and dependant on if it is set or not either use BasicAWSCredentials oder SessionAWSCredentials. Here is a snippet from our own custom integrationsinternal static AWSCredentials GetCredentials(string acccessKey, string secretKey, string sessionToken = "")        {            if (string.IsNullOrEmpty(sessionToken))                return new BasicAWSCredentials(acccessKey, secretKey);            else                return new SessionAWSCredentials(acccessKey, secretKey, sessionToken);        }Thank you,Stefan

While taking some course, I think it would be a good idea to have the possibility to "Flag" any lesson we think it's important enough to revisit in the future.

I made an idea some time ago, had someone (Vasco Pessanha) replied to it and when I get the email about the update and try to see what was written I get the followingWhy can't ideas be visible even though they may not be considered for whatever reason?I cannot see the answer or try to make a point if I don't agree, explain otherwise, , they cannot be searched to see if anyone had the same idea and it was not approved, etc. ...Doesn't this makes sense?Best regards,PC

The idea is to allow users to directly create a Light Process in Service Studio, without having to create a Process and then go to Service Center to enable Light Processes.This could be done by simply creating a separate folder from the Processes, named Light Processes, and we would then have validations in place just for Light Processes (e.g. no more than 1 activity).Additional to this idea, it would be nice to be able to launch Light Processes without having to link it to a database create event, and just launch it normally as we can do for BPT.