Sometimes I feel the need to work with indexes of lists in assigns and it would be nice if I could expand expression editor on the first element in a assign.Every time I need to do this, I must use the second element of the assign to use the expression editor and copy paste to the first one.To do something like this: MyList[index].record = 3

Not sure how recent this step is, but when opening an eSpace, I've noticed that my Service Studio hangs for 1-4 seconds in this step: It seems to me that "fetching possible entry modules for debugging" is only needed on the debug panel and can be done in the background without delaying the opening of the eSpace

The other day, I dealt with the Send Email action and noticed where there is an improvement opportunity that could be tackled with a small tweak. Unlike the selected Email screen, which includes a description, the Send Email action does not have a Description property. With regard to indicating the purpose of the email, adding a description Property to the Send Email action would help make the logic more straightforward, and therefore easier to understand and maintain.

When we have a personal email on our community profile and open a support case for a customer, it might be a bit strange that appear a personal email on the support case.It would be great to have the possibility to change the related email of that support case to our company email or even to our provided client email.Thank you,PS: Hermínio Mira (https://www.outsystems.com/profile/h1qpxpoite/) helped me on this idea.

Since Outsystems become very popular now a days, we should have the hard copy of Outsystems book and softcopy of the Outsystems books, book can be on separate Roles and Topic. Developers like me who are very conformable in reading books can buys these book from any platform Amazon or Outsystems portal.Developers, academic students can be benefited.This is very common thing among many programming languages like Java, .Net and many more.Like we have Head First Java, Spring MVC, Spring boot, Books on C# etc.Endorse by Outsystems will be more valuable

For example, have referenced web services in blue, permission actions in red, entity actions in green, etc. It would facilitate the semantic reading of code. However it could look like a rainbow or something weirder. OR it could just be a small icon overlapped, which would identify the type of action.

add medium link like LinkedIn link in profile

In one of the latest verions of OutSystemsUI the structure ErrorMessage has been added. This is in a nice default format for passing errors around the entire application. We also want to make use of this structure in our backend so that we can have one uniform error handler in the frontend. Both OutSystemsUI and our own actions all provide the same structure with the error information making it easy to consume and handle. But by doing this we create a dependency from our backend to a frontend component and that feels sniffy. OutSystemsUI could change in the future or even be replaced with something else. Better would it be if this structure would be moved to the System entity and by doing so both OutSystemsUI and our own components could consume that structure and in case of changes nothing is broken because the replacement could (and should) also reuse the ErrorMessage structure.

Tracing data updates requires some custom patterns. It should be simpler to trace end user operations to support security audits.

Factory configuration current design makes it very time consuming to apply setting to a large number of eSpaces, or even to your entire factory. It is also difficult to see what is or is not applied if you have a large factory. Suggestions: Allow user to select how many eSpaces user can see in the list. Currently limited to 10. Allow user to sort eSpaces by any of the columns on the table.