Hi,If we are creating an index in a table with a lot of values (millons of records) and the table have a lot of usage (it´ s a core table and have a lot of actions reading and writting), the deployment fails creating a index with timeout error, and all the deployment it´ s aborted on stage 2.Also during the creation of the index the table have blocks and the users can´  t work.If the index include "online" attribute in the creation, all this problems desapear.Regards

I would like to select a bunch of site properties and, when I right-click on them, have an option to generate actions to expose their values.My rationale is, knowing that site properties are not public, if we want to expose their values to be used elsewhere in the factory, we have to create a public action for each one of them. If we have several site properties to expose, creating an action at a time is very time-consuming.

 Background : Family Planning Association (FPA) India is a Non-Government Organization (NGO) that runs 40 clinics across India providing reproductive services including pre and post-natal care. With the onset of the pandemic, most of these clinics are now at the frontlines providing essential care along with reproductive health services. Idea : Create an app that will allow service providers in these clinics to conduct screening and counseling of walk-in clients as well as offer these services remotely to the high-risk population such as pregnant women registered with FPA India and their families, including elderly population above the age of 60, those with pre-existing conditions and those with symptoms or a history of exposure to an infected individual. The app could be implemented by partners in India and they will have access to the (Subject Matter Expert) SME from FPA India. Impact : These 40 clinics along with more than 100 outreach units will reach out to a population of 400,000 from the poor and vulnerable communities in as many urban, peri-urban and rural locations across 18 states in India. They are supported by a team of 800 trained medical and paramedical personnel and community-based volunteers. (Even with the reduced staff due to the countrywide lockdown, these clinics served nearly 29000 patients in the last two weeks.)

Hi,It would be great if when create and index of a table we can chose the order of tenant_id column.Depends of the volumen of the data, the information (columns) and the filters you need, the order of the column inside the index it´ s high important. Sometimes, the better approach it´´  s put tenant_id in first place and we don´ t have this option (or we don´ t found).If we can select the order, performance is greatly improvedRegards.

We frequently have problems with our database CPU being over-utilised by one or two resource-heavy queries and then our users experience poor performance and time outs because the database can't keep up with demand. We don't think one or two queries should be allowed to bring down our whole database, even if they are resource-heavy. Could I suggest some functionality which would allow us to cap the resources consumed by an individual query, please? Or something which reduces the resources allocated to a particular large query if there isn't enough resource available for incoming requests? Perhaps the Resource Governor available on SQL Server?

 gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. https://grpc.io/

When we are submitting an asset to the forge we have this helpful checklist of things that we have to follow so that our asset can be sent to review. From experience, assets are rejected if they do not have a " Try now ". I think it would save everybody's time if this was included in this checklist. It would be nice to also have it mentioned in the docs . Cheers, Tiago

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

This idea is a suggestion for OutSystems UI but also for an improvement on Service Studio. Add support for a dark theme in OutSystemsUI. This version of the theme would be similar to the viewport simulation approach, with classes in the body tag displaying which type of device the user has. The new classes would be "dark" and "light". Add a ThemeSwitcher Pattern to OutSystemsUI. This pattern would be responsible for managing the theme, keeping the user's preference in local storage/client variables. Add a dark theme simulation in Service Studio Again, similar to the viewport simulation that lets the developer see the page in 3 different screen sizes, there would be an option to see the page in dark or light mode. The dark theme is a great modern addition to any app, because it lets users choose which theme is best for their condition. Having it integrated both in OutSystemsUI and ServiceCenter would allow OutSystems developers to have an implementation of this feature that is both universal and officially suported.

When using the Columns widget, it’s hard to control vertical alignment of the content in each individual column. The common workaround, wrapping each column’s content in an extra Container to attach classes doesn’t always behave well. My proposal is to add an ExtendedClass property on each column placeholder inside the Columns widget. These classes should be applied directly to the column wrapper element that encloses the placeholder’s content.