On ODC Studio when you create a new agent, there is a configuration named Call Condition. By its description and behavior it should be called Stop Condition to avoid confusion: It is already there when you open the question mark icon:

 With reference to this thread: https://www.outsystems.com/forums/discussion/31032/analyitcs-mobile-apps-in-lifetime/Currently, lifetime Analytics only reports on web applications.Please, enable reporting for mobile application on the server and network tabs. It is understandable that the client side of the mobile application would be difficult to report.This functionality has been needed since P10 and is critical to delivering on the promise of platform analytics.There is also an expectation being set on lifetime Analytics when the "Network" tab is selected: "Data collected when applications are running natively on a mobile device"It would be great if the following information was made available:Device type (tablet, mobile)Network type (3G, 2G, the other G, wifi, slowfi)OS Type and version (the 2 usual suspects)Browser Type and version (webkit, blink, etc.)Initial splash load timeEverything else that is reported on the server side for web applicationsThanksOuen

Hello,Our community forum has become a good platform where lots of problems are getting solved every day. Almost every day I spend some time to look for an activity happening around the forum, and I literally learned so many things from reading it, replying it.However, I was wondering if we can have mobile app design for our community forum. I know we can access our forum site on Mobile since it’s responsive, But using a mobile app is different and quite handy. I hope you will with agree with me.Regards,Sachin Mahawar

 Problem: The procedure of changing themes in OutSystems is by and large a process of trial and error. Developers need to update styles and check each screen separately, which takes a lot of time. Enhancement: Introduce a live preview editor for themes that reflects changes automatically on all screens. Developers are free to change colors, fonts, and styles and they can even choose not to publishing or navigating between screens and yet see the result. Benefits: Time is saved as the user is not required to test and switch between screens constantly. The customization of themes is brought about in a quicker manner and with less effort. The look of the app is consistent throughout the entire ‍‌‍‍‌‍‌‍‍‌application.

Hi,i recently got aware of a c# library named Polly . Polly is a library where you can define policies to handle execution results and exceptions and perform conditional follow up actions, like retries, retries with wait and others.We would strongly benefit from having an analogous feature in OutSystems esp. when consuming REST APIs. Especially when in need of* Rate limited APIs - APIs where you get an error when you hit the endpoint too many times within a specified timeframe.* Poll based asynchronous APIs - APIs where you initiate a job with one request and need to periodically check the result until you can request the final result of the job.* Unreliable API endpoints - APIs that sometimes time out because they are not well scaled or for any other reason. Requests sometimes time out and sometimes not.It would be a nice feature if we could specify Retry, Retry with Wait and Timeout Policies directly on the REST consume action with optional conditions, e.g.:Retry - max 3 times when StatusCode = 408RetryWithWait - max 3 times, Wait 1,3,5 secondsConditions should be possible to match not only the HTTP Status Code but also the response body. Poll based APIs typically deliver a status request with a code of 200 and the job status als JSON body attribute e.g. JobStatus so a policy condition could look likeWhen StatusCode = 200 AND Response.Body.JobStatus = "Pending"Such a feature would drastically reduce the manual handling e.g. in BPTs asf.Thank you,Stefan

In aggregates when we pull an entity, if the platform thinks it should take other entities behind, it takes automatically, and also creates joins automatically. However, these "extra" entities are not always needed. So my idea goes through when we delete an entity from an aggregate, the joins that are created automatically, are also automatically eliminated. It makes it a lot easier to use.

Let's say that I want to sync Tickets, Ticket Types, Users and Queues. Tickets and Ticket Types are connected, so I want to join them in a first sync. Users and Queues are related, so I want to join them in a second sync. But, I want both syncs to start at the same time, so that I cut in half the processing time. Right now, even though the description of the TriggerOfflineDataSync action clearly states "Action where you can invoke OfflineDataSync asynchronously", the syncs run one after the other, as you can see in the browser network tab. Some of the syncs rely on endpoints that could take some time to respond, so not doing this concurrently makes our apps feel slow. Users will have to wait extra time to have data available to start working.

 Vision Develop a Corona Volunteer App to engage the citizen, researchers and authorities in anonymous  information collection with the common goal to increase knowledge of the Corona virus and provide estimated real time overview of the spread of the Corona virus* Enables new learning about the Corona VirusEngage all citizens of the country 18 years and older via an Android / iOS app in information gathering by allowing individuals to contribute input about themselves and their family's possible corona situation (symptoms) - Anonymously.Only birth year, postal code, and gender will be registered as personal information.Give researchers access to statistics and raw data from the voluntary workGive the authorities access to statistics from the voluntary workProvide registered citizen with statistics on the spread of corona down to the postcode detail level Gather daily health status from each citizen (including corona test result) with easy status and symptom selections.This may reveal possible hidden Corona infectionsProvide knowledge of symptoms throughout the illness periodGive the average length of the diseaseProvide information about incubation periodReveals unknow corona infection casesMake the authorities know the health status of people at home –Easier to know the effect of the current measures and to plan for future measures.The goal is to make this app available internationally  and to empower us all to participate in constructive work to fight the Corona Virus!Join the fight! *Cooperation with medical expert advisors has already been secured.

In ODC "Add Public Elements" should be similar to O11 "Manage Dependencies". Or, at least, the user should be able to choose between using the new "Add Public Elements" and "Manage Dependencies" with the O11 like visuals and functionalities. In ODC the information provided and selection of Public Elements it's time consuming and developers cannot have proper control on the overall picture. In O11 developers have more control when using Manage Dependencies and can quickly understand what is happening. ODC: O11:

In the OutSystems Community, it can be interesting to have a notifications bell in the header, between the search icon and the profile.We should receive a notification when we are mentioned in a comment, new comment in my post, kudos, etc etc. Also, the notification should have a redirect link to post/ideia/ etc.Like this:Thanks