Everywhere in the world, people with symptoms are being advised to call a specific line before going to the hospital. In Portugal this line is SOS 24. This happens because by going to a hospital, people with symptoms who are infected might contaminate others and, if they're not infected, they might become, just by interrupting the quarentine.Lines are clogged with calls from people who either have symptoms that do not match COVID-19 ones, or others who ask just plain stupid questions ( https://observador.pt/2020/03/14/a-que-horas-fecha-o-norteshopping-as-chamadas-que-entopem-a-linha-saude-24/ ). People with real symptoms might have to wait for hours on end for their calls to be picked up, which might accelerate their panic and lead them to visit the hospital.On twitter these last few days I've seen many portuguese doctors, nurses and pharmacists offering to answer questions posed to them there, to stop people from calling SOS24 unless their symptoms are 100% matching COVID-19 ones. Each person thinks their situation is very unique: "i don't have fever, but I have a cough, am I infected?", etc.My idea is: a platform where doctors, pharmacists and nurses would put their profiles - ideally with a link to somewhere online which proved they really are what they say they are (hospital webpages, or CVs, of linkedin - and allow people to reach out to them in order to ask questions that they would otherwise call health lines to do so. I think people will always try to call health lines, but if they're waiting in line ~4hours for their call to be picked up, they might as well post a question on this website and see what a certificate health professional has to say.I think this should be easy to build: first, a simple page with "I'm a doctor who wants to help" and a "post a question" for random users. Then, we would either round-robbin the questions that came via each professional in the platform or we would allow people to ask specific profiles of professionals available.

When I set a description to a timer in service studio, I can't read this description at the timer in service center. It would be nice to being able to read the description of a timer in service center so that I don't need to open the eSpace to see where the timer was used for.

Make the Documentation parameter (yes/no) of the exposed service customized by environment and/or require authentication.An easy way to do this is if the documentation parameter can be configured with a site property, then we can disable/enable it for each environment, or another solution would be to disable documentation in the serviceCenter.Another good feature is the possibility to define some authentication action to access this documentation.

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

When deploying applications with DevOps Pipelines using the LifeTime API, the deployment started with the API will skip the "Configuration or confirmation" step and will assign the modules automatically to the "(Main)" catalog causing a lot of manual rework in Service Center assigning the correct catalogs. When exactly the same deployment plan is executed with LifeTime the deploymet stops at the "Configuration or confirmation" step. With this idea, we suggest to apply an option to activate the "Configuration or confirmation" step when a deployment is started via the API. It is not desired to assign the catalogs via the API, however that could be a great additional functionality but it is not desired to get "our" pipeline problem "fixed".

In order to better help other community members in finding solutions to their problems, I would like Outsystems to remind forum posters to either reply or mark answer as solution to their posts.I come across a lot of posts that are unanswered by their poster while they seem to have potential solution answers posted.

I often face this issue that I copy any widget from same or other action and wanted to use that somewhere but when I paste it, it pasted somewhere else in the action like I'm in bottom of action but it will be pasted in top/middle. Why it cannot be pasted in the place where my mouse cursor is or where I right click? If its difficult so it can be implemented to paste where user click. I believe, if service studio can offer widget in exact place on drag and drop, a copy paste can also be implemented.

Hey guys,I updated the demo of one of my forge components and I wanted to upload this.However I was required to also reupload my component itself, I even had to increase the version number! Even though the component itself wasn't updated.I'd love to be able to upload a new demo file without having to update the component itself.

When using "find usage" to carry out analysis, it is not possible to track your navigation or open multiple tabs. I am doing role analysis of a very large application and I am using the CS module of this application to find the roles of this module in other modules. This way, I can access each screen and components where each role is used. However, when I reach a "Check Role" within an action and do the "find usages" in that "check" I lose where I left off in the first "find usages". From there I have to open "find usages" through the CS module again and look in the list where I had stopped. This makes the work of large analyzes more tiring than it already is. So I believe you can create several tabs for each find usages that we do or create a breadcrumb within the same module so that we can follow the path we took and be able to go back.

We adopted Google BigQuery as the central database for storing, processing, and analyzing large volumes of information. Currently, the integration between OutSystems and BigQuery depends on custom solutions (via APIs or external drivers), which leads to: Increased development and maintenance effort; Risks related to data security and governance; Loss of efficiency in delivering critical business projects. A native integration is essential to ensure alignment with market best practices, simplify development workflows, and enable the scalability of ongoing digital solutions. Proposed Technical Requirements Authentication and Authorization Support for OAuth 2.0 (end-user consent via Google Identity). Support for Service Accounts (server-to-server integrations, preferably with temporary credentials). IAM Permission Management Compatibility with the minimum required roles (roles/bigquery.dataViewer, roles/bigquery.user, roles/bigquery.jobUser). Connection Layer Consumption of official APIs (REST/gRPC). Alternatively, support for official JDBC/ODBC drivers. Query Execution Synchronous and asynchronous queries (jobs). Result pagination handling. Monitoring of running jobs with jobId return. Data Type Compatibility Support for primitive types (STRING, INT64, FLOAT64, NUMERIC, TIMESTAMP). Complex structures (STRUCT, ARRAY) with JSON fallback when necessary. Network and Security Connections via HTTPS/TLS 1.2+. Support for Private Google Access and VPC Service Controls. Limits and Quotas Handling Retry with exponential backoff for transient errors. Configurable concurrency control. Monitoring and Auditing Logging of integration events. Compatibility with Cloud Audit Logs. Expected Impact For Equatorial, the availability of this functionality means: Reduced effort and development time in critical integrations; Increased security in accessing sensitive data; Improved performance in analytical queries; Assurance of compliance with established governance and regulatory practices. Our ask is for a native connection, same way we have in the Connections tab in the ODC Portal, to connect with the Google BigQuery database.