Users that are allowed the "Reuse & Monitor Applications" permission through Lifetime aren't able to list applications within Service Studio, the only way they can list them is by clicking "Open from Environment...".
From my point of view, they should be able to view the list of applications, their icons, and have the ability to search them. This seems like an incongruent approach.
Thanks,
Márcio Lima
Hi,
when we are changing attributes from entities, removing static records we have to do the mapping ourselves and take care of all stuff.
We should not be able to deploy this without having a sepcial action in place for this.
I think Outsystems got enough information available to create a special Mapper-actions for these kind of cases, so we only need to choose how to map/convert data.
This will prevent lots of conversion-scripts and speed up changing the application.
The new JavaScript editor for mobile apps, is great, but the autocomplete could use some work :)
The feature catches comments and strings at the moment, see below.
It would be great if we could for instance look for a search term only within queries, or only within assigns or parameters.
Hi Everyone,
Is there any problem to make automatically makes child structures to be public whenever we do are making parent structure as public.
Here is the case
A
B
C
A is parent Structure and B,C are Direct child's to A. assume now B,C, A have public property as "no"
So when i try to make A structure as public , Service studio through's error saying to make B,C as public. in order to re solve the errors and making A as public.
Assume where we have more n more child structures. then it will take quite amount of time to make all of them as public.
If there is no critical problem to develop this. Please consider this idea. If not provide a alternative way.
Thanks,
Ramakrushna Rao Seera
Just a simple (really small) improvement, I would like to see the size used in lifetime in the same format as the maximum allowed. When the maximum size is 150GB why show 132440MB as used size. I don't really care about the number of MB's when the max is 150GB.
Example picture:
It would be great if there was some way expose process events for entities in the (System) espace.
At the moment, they're either hard-coded on or off, so you're fine if you need to start a process on the creation of a User entity, but if you wanted to do an automated code-review, for example, there's no way to start a process based on the create of a new Espace_Version record.
It would be great if there is a clear indicator on the MVP's avatar or in their profile summary so that they are easily identifiable when reading posts on the forum.
It would be great if you had the possibility to download an application (.oap file) directly from Service Studio, with no need to enter Service Center:
When we try to run an Advanced Query, in the test button, to see if the query is having the expected behavior, it happens that sometimes we have errors and the error message is never clear (eg: after ')').
From what I suggest in continuation to my previous idea, of putting the numbering of the lines in the Adcanced Query, also indicate in this error message the line where we are failing. What do you think of this idea? It could help a lot.
Nuno Miguel Verdasca
Outsystems Certified
I know there is an inline edit widget in the forum, but I would like an intelliwarp editable grid standard built in in AgilePlatform, with images for save, delete, edit in the left column. Proper edit widgets acoording to the type of te field (input, combobox, textarea, etc). Would make apps great and development much easier.
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