I would like to have a sort of a screen in the Service Center where all this information would be centralized and displayed, and where it would be possible to list all APIs and to navigate to the API edit screen from there.It is not the first time where I am in a project where it is used a middleware for APIs management inside the organization. And a problem that always happens when, for some reason, the middleware changes its DNS, so from xyz.whatever to azurexyz.whatever, is that to make the changes in all the currently used APIs I need to go espace by espace (or module by module) in Service Center, assuming that I don't need to go into SS to see where all APIs are located and I don't miss any of them and change one by one.I know it is possible to have this kind of list looking into the system entities, but I believe this should be part of the product because it seems to be commonly necessary.This would also help, in cases like the example, I described above, to make sure that we don't forget any API where the URL basis needed to be changed.

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

Allow multiple users to work on same project at a time to decrease development time and will be easy to work with big projects.

We would like to document everything in our code so we have descprion field everywhere.Also for variables in actions etc but not for parameters in the javaScript widget.So you can't specify what the purpose is of the variable.Please add the description field to the parameter field in the javaScript widget just like for normal variables.Kind regards,Johan den OudenOutSystems MVP

Service Studio prevents creating foreign keys that reference a static entity defined in a Library module.This makes sense for Protect and Delete rules, because the static entity defined in a Library module is not backed by any database tabe.However, IMO nothing is preventing us from using a foreign key with Ignore rule. These foreign keys will not have any database constraints, and will just be syntactic sugar to their underlying type (Integer, Long Integer or Text) but with the additional type checking and suggestions we come to expect from Identifier types.For example, it should be possible to define static entities that augment the capabilities of OutSystems UI by using this pattern, as described in https://medium.com/@leonardo-monteiro-fernandes/extending-static-entities-part-1-bec8b3b7631cThis would also allow values obtained from SOAP enumerates (which are mapped to non-persistent static entities) to be stored in database entities, without discarding the type information.

OutSystems did an awesome job with redesigning the icon system which is used in the Hybrid version of Service Studio.However I think some icon designs got worse, mostly noted the input and output parameter icons:In the old design the arrow in and out are very clearIn the new design:Regards,Daniel

 The BaseTheme used in Outsystems, as like most of the designers in the market, use the   multiple of 8  rule to create sizes for margins, padding, font sizes, grids... So, if BaseTheme uses the same rule for variables for everything why not use it in the Style Tab too?   Benefits : Less maintenance , Easier for the Develop team to match mockups margins and paddings. Less frustration,  Help experience between the Develop team and the Ui/Ux/ FrontEnd teams easy and softly. Less work for the FrontEnd team finding wrong margins and paddings. Apply best practices , (One-click change everywhere) , Even if there is inline CSS (which isn’t the best practice) when the variable is changed on the theme, the value is automatically updated everywhere. CSS learning ,  Make the Develop team more familiar with the CSS variables.

Hi,The use of domains is essential when doing factory governance, but this concept is stuck only in discovery. This concept is also essential in Architecture Dashboard, Service Center and Lifetime analytics.- ArchitectureThis is where it's more important because domains are the top of our architecture and we need to have this vision. It will facilitate domain technical debt control and facilitate reports.- LoggingIn service center and in Lifetime Analytics it would be great if we can filter all data by domain also, because this is our top level on our architecture and we need to have this top vision (errors, page accesses, general logs).In Lifetime analytics it will be great also if we can see the performance by domain an then we can start drill down, but this top level architecture vision is important.

The Quickly add a dependency in any module is a great accelerator.A way to improve this feature would be to add a checkbox to allow us to add several dependencies in the same step.

Hello Community,My team and I developed a BPT process and executed a load test. As a result, We triggered the circuit breaker and had some unexpected errors and, the result has more than 100 processes that were "Active with Errors".After having to open over 100 new tabs to click the "Retry" button, the idea came to my mind of having an option that would allow users to perform the retry and skip option in bulk for a process.I hope to hear some feedback from the community.