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.

Build a Solution Architect Agent to suggest High-level architecture design with project estimations based of requirement provided.

Allow creating an action from the selected section of a flow. The action would get the required inputs and outputs, and the flow from where it was extracted should automatically fill the action parameters with the local variables it was using

when you upgraded or install a new platform server..- you have to install .net framework manually- configure iis manually- use the configuration tool- do a commandline command updatedb- start services- do a commandline scinstall- update recheck licence.why can't we have this all in 1 wizard and/or unattended install with a config-script.

Title says it all. :)J.Ja

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.

It would be great to have a small “Neo Insights” section within our forum profile. This section could display how often Neo has helped us, its response accuracy, and even suggest learning materials based on our previous questions. It would make Neo feel more like a personal learning assistant that evolves alongside each developer’s journey.

When a developer opens an aggregate window or popup in Service Studio, the platform automatically enables the 'Publish' button, even if no changes have been made to the code or other application elements. This can be confusing, as developers might assume they have unknowingly modified something, prompting them to publish the application unnecessarily. I propose that the 'Publish' button should only be enabled when actual changes have been made to the application—whether in logic, UI, data models, or any other relevant components.

When we add non-mandatory attributes to structures (for example input/output structure of a Service Action), there will be no impact on the consumer modules ONLY if the added attribute is a basic type. You can read this in the documentation Handle Changes in Exposed Functionality , 'The following changes made in the producer do not have impact on the consumer modules: ' Add an optional Attribute (basic data types only) Structure In my perspective, there should also be no impact on consumers when adding non-mandatory composite/complex attributes like adding a record, or a list, or list record... Here is a scenario we are facing right now. We use Service Actions instead of internal REST API's to promote a loosely coupled architecture. There is benefit in using Service Actions as the platform handles the security and findability of Service Actions, whereas with REST API's, you have to do it yourself. All our Service Actions communicate with input/output Structures. When we want to add a non-mandatory structure to the output structure of the service action, then the consumers are impacted. Now both applications have to be deployed together, which complicates loosely coupled deployment strategies. Here is an screenshot to describe the issue.