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

In the version Version 11.54.82 / Build 63748 there is a new warning, Unused Resource, Resource 'Resource' is never used. Consider deleting it. and the warning points to Resources->MyResources.zip. This resource is part of a mobile application, and the zip file contains all the icons (logos) used by the app. I recommend removing this warning, as an inexperienced developer might mistakenly delete it, causing future compilations to generate the application without its logos.

 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/

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.

OutSystems is powerful, but some of its best features are hidden from developers. This forces us to create complex workarounds for standard patterns like Publisher/Subscriber (Pub/Sub). Pub/Sub is essential for modern apps, allowing different parts to communicate without being directly connected. While debugging the application in client side, it has been discovered that OutSystems already has a built-in Publisher/Subscriber functionality. This feature is powerful and works perfectly, as demonstrated in this Working demo - PubSubDemo This internal API can be accessed with a simple piece of JavaScript: require(['OutSystems/ClientRuntime/modules/PubSub/Publisher'], function (Publisher) { window.Pubsub = new Publisher.default("DemoApp"); }); By adding this as a required script to a module, we can unlock a native Pub/Sub instance, allowing different blocks and components on a screen to communicate with each other without being directly coupled. This is a game-changer for building complex, modular, and responsive user interfaces. The existence of popular Forge components like "PubSubEvents" clearly demonstrates the community's need for this exact functionality. My idea is simple: Elevate this hidden Publisher/Subscriber functionality into an official, documented, and fully supported feature of the OutSystems platform.

Add a new client action for System event for when the mobile app is updated (through dehydration).This way we can add specific logic to treat properly this situation (toggle features, start sync, improve user experience, add analytics, etc...)

Some public elements remain stagnant on applications even though they are not being consumed anywhere. A warning on architecture dashboard to cleanup these elements would be helpful.

That's about it.Add output parameters in WebBlocks so you can reuse the data on parent screen or block.

Create a Built-in Function Switch, under the Miscellaneous tab. It makes it easier for developers to understand the intended behavior than having several if's chained. It may cause fewer errors, since it is not necessary to check the same variable/condition several times.

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.