Right now, debugging the code extensions seems to be impossible, unless I am missing something. This really needs to be improved somehow. J.Ja

I find my self many times in a scenario that I have to find an specific list element and delete it... or have to do a for each to check some condition to delete or not that element. So will be very hand an action(client and sever) that delete list elements that matchs a condition. ListDeleteByCriteria

I need a combobox inside aggregate that show all attribute that is hidden, and when I select the attribute it shows in the return. There are cases that have a lot of attributes hidden, and I need one attribute to show, and I need open all until find out.This implementation help with agility.Example:

It would be very nice to have Service Studio automatically generate the necessary screens and logic to manage data over any given entities - and also it could be smart enough to detect basic entity relations - The Scaffold Style! This would be a major head start on projects and a real first or even second sprint blaster, allowing teams to start focussing on business value since day one!

When using the "Find and Replace" feature we are presented with the options: "Replace" which replaces all occurrences found and "Find" which lists all occurrences before replacing.But currently when you use the "Find" option there is no way to select which occurrences from the list you want to actually replace and which you want to keep.It is just a way of seeing what will be replaced if you selected the "Replace" option on first hand.It would be nice to have a way to remove occurrences of the replace list before replacing all of them.

I would like to bring this into your notice that every time I attempt for an Outsystems examination via pro proctor portal I have to face multiple issues as well as my colleagues face the same . This results in exam abandoned, other hurdles in exam as follows.Question Paper will not loadInaudible prometric voiceProctor ask to rejoin without any reason and many more unnecessary issuesAsk to connect proctor team or Outsystems teamEven After following all the instructions of proctor they don't allow to resume or retake exam It creates lot of confusion and waste lot of timeProctor is never on scheduled time and some times we have to wait for hours to complete check in processAt the End we will lose all the money spent to schedule the exam without appearing the exam due to their inconsistency

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.

To prevent very old posts/ideas, say older than 1 or 2 years, being bumped to the top of the recent list, prevent commenting on these, for example .The content may still be relevant though, so you can reference the post/idea in a new one thus linking back to the old post/idea.Also, when viewing the initial post/idea, perhaps show any referencing posts/ideas so that users can navigate to the latest conversation around it.

Currently, OutSystems allows exporting the BPT Process Flow as an image, which is very useful for documentation and communication. However, this export only shows the high-level activities and does not include the logic implemented inside each activity. Adding the ability to export the internal logic of BPT Activities as an image would complement the existing Process Flow export, allowing developers to capture both the high-level process view and the detailed activity implementation.

When a Lifetime administrator has to set up a new user, he always has to create a new user account and define a password manually.After creating the account he needs to go to his email client and write an email with the user credentials, the environment URL and ask for the user to change the password once he logs in.There should be an easy way for a Lifetime administrator to invite a new user just by inserting the user's email.The system could then send an automated email inviting the new user with the environment URL. The new user would just need to follow the URL and define his password.This way, the provisioning of new users would be faster, with less manual tasks for the administrator, and also more secure since no passwords would be exchanged by email, no one but the user would have access to his password, and there wouldn't be the risk of the user not changing is password on his first login.