It would be nice if we could expand or collapse any directory, flow, etc...
Just a right click on mouse feature...
It would be nice if we could expand or collapse any directory, flow, etc...
Just a right click on mouse feature...
Sometimes forge plugin is missing information, which operating systems are supported. (Android/IOS). Also there has been cases, when new device OS version is breaking plugin functionality. If Forge upload page would have reserved fields to supported operating systems and also their version(s) used in in testing, then users could be forced to include that info too. (At least for one OS version. Also it would be great if others could append that info afterwards when new version/results available, like "Validated in IOS 12.0.1 or IOS 9.3.5)
Every user hopes that whenever they open a web page the top-first input available is focused.
At least on "scafolded" web screens it would be very simple to implement, but with an UX improvement with a huge value for the end-user
Hi, is important create a folder tree in Logic tab.
Just like "Action's" folder allow user to add folders to the Entity and Structure tree.
Hi,
In user profile we can see how many components, kudos and posts in forge a people developed but not possible going to and see this information.
For example, when I access the profile of a member of the community I realize that he has already developed 19 components in Forge (as in the image below).
But since the labels are not links I can not click and see what components this member has created. I think that would be quite interesting.
Thanks!
For mobile apps, we frequently leverage in the use of local storage to gain in speed and traffic exchanges.
With no Advanced Queries in local storage we cannot do complex queries. I'm limited to the functionalities of the Aggregate.
I often need to add translation / change a translation from feedback of the users.
If you have a bigger application it's hard to find the correct line in the list of translations. Be able to go to that line from the UI saves me a lot of time. (minimum 3x faster XD).
If it's visible in the property inspector, we don't have to go to the translation screen, also nice.
It's now possible to double click on a line in the translation list to go to the screen / object, so the link is already there ;), i hope this is a quick fix.
Currently platform events can only be dispatched when associated with a block, this makes it harder to integrate with cordova plugins, for example, where in order to expose plugin events we need to use a block to register listeners for those events and in turn dispatch system events by executing a client action on the block that dispatchs the events defined on the block.
This has the following problems:
The idea would be to give the ability to send custom events that aren't necessarily bound to a block much like Systems events "On Application Ready" and "On Application Resume".
I like the user friendly display of the DateTime_PrettyFormat function, however it's not useful if the date is not in the same timezone as the server time (which I believe defaults to UTC).
It would be great if the function could take another optional argument being a timezone offset and the Pretty Format would return the correct value in that given timezone.
The login action in the users module contains a brute force protection (which is great). This mechanism can be adjusted (trough the users site properties) and also set off.
But if you want some kind of hybrid (a login that uses the brute force and a login that doesn't uses the brute force) this now isn't possible (only trough the user login action from the system but that gives a warning the users login should be used).
The case for this is when you have 'internal' services (rest with basic authentication) where you don't make use of the internal access (or can't) which are called to push or get a lot of data. With the 'normal' user login service to much brute force logs are made which isn't needed. So the authentication for these service schould be done with a login action which doesn't has brute force.
Kind regards,
Evert
It would be nice to have a setting either in Service Center or lifetime that we can use to manually set the Android Version Code. We recently ran into the situation where we were re-writing a mobile application we already had in Outsystems. In order to publish the new Outsystems application to google the Version Code needed to be incremented by quite a bit. The only way currently to increase this number is by putting in a service ticket with Outsystems Support.
Please add a magical button to retry a failed deployment.
It would be a time-saver to not have to create a new staging, validate the plan again and re-deploy.