When dragging dropping a aggregate to a page in order to create a form, the problem I face is that sometimes the lenght is large and it doesn't fit into a input properly.Service Studio could create instead of input a textarea when the Max. Length is above some value (eg. 50)

Several times happens I need to copy a user action and make a few changes, but when i notice i am making changes on the original action and have to undo it all...It would be nice to be automatically redirected to my new created action....Does this happen to many of you also?

Would be nice to convert local variables, input variables, or output variables into a structure. Something like this:

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).

On my entity I have some auditing fields like ModifiedBy and CreatedBy. When you generate a screen by dragging the entity on the MainFlow you don't want to have these fields such as ModifiedBy and CreatedBy generated as fields on the screen. Just like the Id attribute is not generated on the screen. It would be nice to have an option when declaring an entity attribute not having this field generate on the screen. For example if you have an audit field like ModifiedBy or CreatedOn.

When I'm calling with Outsystems support I always hear the same music Although the piano concert when i'm on hold is OK, it can use some variation.Perhaps cello or violins for a change?

I would like to suggest a logic clarification (or modification) to the training for the archiving. It's possible there has been an oversight, or the training may lead to a dangerously wrong solution, or I'm just an idiot. (More than one option may apply.) https://learn.outsystems.com/training/journeys/web-developer-exam-2993/data-archiving-best-practice/odc/7017 Here is the current logic in question: Text below it it, whole section pasted for clarity: Set Archive Threshold - Sets the number of records to archive by iteration. This threshold can be defined using a Setting, so it can be adjusted without redeploying the app. Set StartTime - Sets a local variable with the current time when the execution starts. CheckRecordsToArchive - Validates if there are records left to archive, according to the conditions defined using the control columns. Has Records to Archive? - Validates the output of the previous query and executes the archive branch if there are records to archive. MoveIntoArchiveStorage_InBulk - Executes a bulk INSERT INTO SELECT statement from the primary storage to the archive storage, combined with a clause to limit the amount of archived records (using the Archive Threshold set in 1). It implements the archive condition. MainStorage_SetArchivedFlag_InBulk - Executes a bulk UPDATE to set the IsArchived flag of the records archived in the previous step. Can Process More? - Validates if the current execution duration is approaching the Timer’s timeout (using an expression like DiffMinutes(StartTime, CurrTime()) < 15, for a default timeout of 20 minutes). If there’s still time, it continues checking for more records to archive. This approach helps prevent the Timer from timing out and having to repeat work. CommitTransaction - Commits the transaction to make all changes permanent in the database. WakeArchiveData - Re-wakes the Timer to check if there are still records to archive. My suggestion it that something should be added to step 6 " MainStorage_SetArchivedFlag_InBulk " to explicitly clarify that they should not use the exact same logic (where clause) used in step 5 to select items in step 6, because the data may have changed , leaving the data in query different. This will result in the wrong records being flagged as archived, and subsequently getting deleted by the clean-up process. They need to do some sort of check (inner join?) against the archive table. I understand this is an edge case, but we all know one in a million edge cases tend to happen within a week of functionality going live. Maybe there is an assumption that someone will know to do it this way, and I'm just being dumb, but the wording of the guidelines would tend to lead to someone reusing the same query logic, especially as an inner join query would be assumed to be much slower....? Does anyone from OutSystems training, or in fact, their business processes team, have any thoughts on this. It this a flaw in the training content, or in the archiving logic that was envisioned? Or am I just barking up the wrong tree here? (I'm guessing this scenario is used in the exam as well.)

Whenever I search something in forums, It shows as "{Search Keyword} - Search posts in Forums".Instead, we can suggest at least top 5 posts relevant to that keyword. So that, the users can find of what they're looking for.

Service Studio doesn't have any compatibility with the horizontal scroll MX Master 3 Mouses (previous models also).We need to click the horizontal scroll bar to scroll, but the vertical works fine.For long flows, Advance SQL queries, Javascript, etc, that can grow vertically and/or horizontally, it's a bother to switch between a scroll and a click on the bar.

As a developer building Reactive Web Apps, I often find myself writing the same basic logic to format data (e.g., converting a Decimal to Currency, or a Date to a specific local string). I propose adding a 'Quick-Format' dropdown or right-click menu directly within the Expression Editor. Instead of manually typing FormatCurrency (Product.Price, "$", 2, ".", ","), beginners could select a preset that auto-generates the function. This would speed up frontend development and reduce syntax errors for those new to the platform.