The Users Module is constantly getting packed with new features like Brute Force Protection, external directory integrations and many many more.
I think its about time now the R&D team sit down and do something we hate the most (document). We seriously need some sort of a document to guide us through this mountain of features.
When I was looking at the download page, I noticed two version naming systems are currently in use:
For the IDE, on the downloads page we see the release "tag" (eg: "Development Environment 11 - Release 12").
But then, on studio, we see the version number (eg, "11.0.406.0")
Again, with platform server and lifetime this scenario repeats: on the download page the tag, on the software the version number. This creates a bit of confusion when one is trying to understand, e.g., which version of the platform server to download.
By looking into this article detailing the version naming system and this article detailing the release lifecycle, one can reach the conclusion that the tag on the download page refers to the release life cycle (the when) and the version number details the type of changes on the release (the what).
My suggestion is first and foremost to use a single naming system both on the software and the website, to avoid confusion. But going a little bit further, I would suggest adopting a simpler system where version number is based solely on the release (which in the end is the only thing the user cares about). If as the article I previously linked suggests, there is predictability on the release cycle, then similarly to Ubtuntu, one can even make the date part of the versioning system, naming both the release and the version after the date, and if necessary, additional numbering for minor patches.
Additionally, it would be really, really nice if we had exactly this page, but with the download links on the tables.
Thank you for your time,
Filipe
Inside of an app context, have the possibility to move an eSpace into an app.
At this moment, exists the possibility to move an espace by passing over the eSpace and then clicking on "move to", but if we have an option to select an eSpace to move from an eSpaces List, i think it will be more developer friendly.
Hello there,
It would be nice to open multiple eSpaces in Service Studio by pressing shift from the top to the bottom (or vice versa) when we go through the "Open from Environment" option.
Also it would be good that, when opening the eSpace the cancel button would work.
Thanks.
It should be possible to change in Service Studio the name of an eSpace without having to open it, change it and publish it.
I suggest the possiblity of add comments in expression editor
Add tools to allow the enhanced organization of application icons in the user's environment in Service Studio. Filter, Sort, View mode (List, thumbnails, ..), ...
Many REST services implement sending files, documents etc. by having a body with multipart/form-data. There are many questions on the forum about this, e.g. here, here and here. Unfortunately, the OutSystems Platform lacks native support for this, leading to workarounds like this Forge Component or "manually" modifying the request data in the OnBeforeRequest, which leads to things ugly code like this:
(Yeah, that's mine :).)
So it would be a great addition to the Platform if it had native support for multipart/form-data for REST services, at the very least for consuming them. That would make our lives just a tad bit easier!
Enable to Test an Action giving new input parameters.
Usually there is a requirement in applications to support various date formats different from the one used by server for storage. This typically involves conversion from server format to user preferred format and vice-versa while storing user input. The TextToDate built in function does not support any format other than these : YYYY.MM.DD, YYYY-MM-DD and YYYY/MM/DD. It does not even support the date formats which are available under Environment Configuration in Service Center. This limitation becomes a hurdle and forces developers to find alternatives or use extensions.
It would be really great if future release of Outsystems can support more formats in TextToDate probably by adding more arguments to function to properly understand the provided formatted date text and convert it to date.
Buttons in a buttongroup in a mobile app are rendered by default without a type attribute.
By default they behave as buttons with type="submit"
When a user presses the Enter-key the first option of the buttongroup is selected even when a different option is selected first.
As a workaround I have added type="button" to every button in a buttongroup but I think this shoud be done by the platform.
I have to write JavaScript expression in order to implement indeterminate checkboxes. I think it is very useful the indeterminate state is controllable by an expression of its property.
And the indeterminate checkbox styles for Silk UI web template supported by OutSystems are also expected.
Please bring Service Studio to macOS. That would be great for 2018. Make that a reality please. :)
Gede wrote:
Hi dekker,
I experience the same, it is caused by installing Dublin application before SilkUI application. I fix this by republish the Dublin template in Application Management.
regards,
indra
just in case anyone is still experiencing the issue.... this helped me. i would mark it as a solution if i could
Hi Andy,
It's not about any Role, but about the user with username "admin". I explained it above.
Hi Sai,
Please refer the Link. Its has preview and download functionality. Let me know if it works for you.
-Hitesh-
I have the same issue. Even with the role SuperUser and UserManager, I'm not able to change the password of another user. Is there any reason why this is not allowed?
Thanks
I have tired this and it is showing only running and stopped status on the server with the help of mentioned command. So it is not showing warning status over here.
i would like to know how to link the service center warning symbol over here in the server side