Update The Old Video Tutorials in Outsystem Guided path. For example in outsystem traditional guided path -> Master Class on Javascript and jquerytutorials videos are published in 2016 - kindly update that New video , Some time old video unable to understand . It will take more time to understand .Thanks in Advancekishorevijay

When developing mobile app, you can use static entitities.However they are not available if your application is running offline.Most mobile apps we develop are based on offline first principal, making usage of static entitities useless.

At this point of time it is not possible to select multiple resource file during import.

OutSystems currently provides local storage only for mobile applications, but adding this feature to reactive web apps would bring significant benefits. Store frequently fetched data locally to prevent server calls. E.g. static entities always could be stored locally. This is already an idea: https://www.outsystems.com/ideas/3497/support-static-entities-in-mobile-app-as-offline-data/ Improve user experience with partial offline capabilities for certain use cases. Please let me know whether there is another solution possible to decrease the amount of server calls then having local storage available for Reactive.

Inconvenience:If a user is having multiple accounts, they can very well able to link their primary account with their secondary accounts, but their community ranking doesn't get linked. because of this the ranking gets disturbed.Idea:In order to maintain proper ranking, Outsystems can provide an option called "Merge Ranks". By using this, the rank of the primary account will get reflected in all the linked accounts. So that, the secondary accounts won't disturb the ranking order. If user is not interested in merging their ranks, then they won't opt for it.

It would be nice if we could maintain in the Architecture configuration a "whitelist" of self-explanatory names  that don't need a description.This list could have default already have the most common names like:*IdNameLabelDescriptionCreatedByUpdatedByCreatedOnUpdatedOnThe code analysis pattern Missing description on public element",  should then use this list and exclude reporting elements with names that are on this list.

Sometimes I want to pass only a small feature from one environment to another and when I merge them I have like 20 different devs with a check box to unselect. If there was an option "Select All" on each side, i could easily take all out and select the only one I want to merge. Ex:

When working in Service Studio whenever we need to create a new application we need to either select a color for our application or upload an Icon, however in big factories there are usually specific Icons to identify different groups of applications or different domains, it would be great if we could select from the existing icons in the factory to avoid needing to go search for the icon if it is another person creating the new application.

With the quiz being added to the Web Develop Web Application course, I would love to see one for the Mobile course as well. It really helps validate your understanding of what you just learned. And of course this is a really nice way of getting a glimpse of the questions you can expect when going for the certification.

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).