Motivation:
A OutSystems Now App generator, that performce all the necessary steps to build a customized Now-app (like the London theme generator).
Perform the following steps
Download customized Android and iOS code.
It is possible to consume a REST API using the PATCH method, but it isn't possible to expose a REST API with it. PATCH is meant for selectively updating data (instead of all at once, like PUT). I would like the Platform to support PATCH for an exposed REST API as well.
However, PATCH is useless without being able to detect which fields (Attributes) have been sent by the calling party. Currently, if a consuming party doesn't send all the fields, the Platform will set them to the default value. This works for most cases, but not for a PATCH. Therefore, when supporting PATCH, there must be some way (via a runtime property) for the Platform to indicate which fields have been sent, and which were not.
Since a while (P11) it's possible to comment out code. Which is great, for development and testing. However, except for special circumstances, you shouldn't want to keep that code around forever. Therefore TrueChange should give a warning showing the location and ideally with the date/time and name of whoever commented that code, so it's easy to prune the "comments" when it's time to release the module.
We have Ctrl-D for deleting a variable+value pair from an assignment, but I'm often in want of a copy/paste option as well, or alternatively a drag/drop for a single assignment pair. Currently, I need to copy/paste the variable and value seperately.
I very often find myself scrolling through the trees in the various tabs to reach another section, e.g. Multilingual Locales on the Interface tab, or Integrations on the Logic tab, or Structures on the Data tab, etc.
It would be really useful if it were possible to directly jump to various sections, e.g. by hovering over the Tab icon/name on top, then getting a seemless dropdown list with icon + name of the section, e.g. "Structures", "Session Variables" etc. for the Data tab. After clicking the view jumps directly to the start of that section (and puts it on top of the screen, if possible).
Often I drag an Action statement from the toolbar, type in the name of the Action, only to find I haven't referenced it. Currently that means closing the pop-up (it's eSpace modal), clicking the "Manage Dependencies" button, selecting the right Action, double Clicking the "RunServerAction1" Action statement, again type the name (for the third time).
I'd love to have a Manage Dependencies button right on the pop-up, so I can skip all the above.
As it is, the browser back button produces some pretty serious issues with the platform. Outsystems pages can rely heavily on their preparations, and preparations don't run with the back button which can lead to outdated displays.
This could lead to a variety of issues, from wasted time using misleading data, all the way to potentially exposing sensitive data through the back stack.
There are ways to force-refresh pages using javascript, but as a low-code platform we aim to minimize the amount of custom javascript in a solution.
The addition of built-in handling to force (or choose to force) pages to refresh with the back button would be a very desirable change.
While talking to some work colleagues, I had an idea regarding the way entities are created and the process that ends up happening almost every time.
Regardless of the Entity about to be created, there are a few attributes that end up always being present, such as:
(...)
The idea here consists of a small menu that allows the user to create a default “Form” that will default the generic format of each Entity created on the module he's currently working on.
With this, any Entity (Non-Static) that gets created on that module automatically “Inherits” those attributes, already defined to the correct format, w/ descriptions etc.
This behaviour should be possible to turn On/Off with ease.
Any feedback would be appreciated,
Cheers!
OutSystem engineers are often replying to forum posts, and most of them I know by now. But for newcomers, and in case a lesser known engineer stops by, it would be very useful if next to their name there would be an indication (e.g. the OutSystems logo) to show this is someone from OutSystems.
Normal expressions allow booleans to be evaluated without comparison, and the not operator, e.g.:
if(not myBool, "hello", "hi")
In simple query expressions however, we need to explicitly check against True or False, and the not operator is not allowed:
Entity.Attribute = False
I'd consider that bad coding style in a normal expression. Why can't we use "proper" boolean expressions in simple queries?
In Mobile Apps, Service Studio shows what Screen is the Home Screen by a special icon. In Web Apps there is no such icon, so it can be a surprise what Screen is opened when pressing the blue "Open in Browser" button.
It would be swell if Service Studio would indicate what Screen is opened, with an icon similar to the Mobile one.
I often find myself wanting to paste a parameter as another type (e.g. input to output), and the only way is to go through the context menu. It would be handy to have a "Paste As" shortcut key (e.g. Ctrl-Alt-V or Ctrl-Shift-V).
With REST services, we can open the documentation from the context menu. With SOAP web services, we have to type the URL (which is not easy to find) to get there. It would be great if we had a context menu option "Show Documentation" for SOAP as well.
Seems that not all is OS11 is using the new webblock event and event handlers feature of OutSystems 11.
Would be nice if we do not have to fall back to the Deprecated Notify and NotifyGetMessage actions for popups in OS11.
I myself am listed 3 times as member. Actually its only me: 1 member.
I noticed this happens to many more OutSystems community members.
In my situation I only use 1 of the 3 accounts, the other two I created long time ago... and haven't use them for a long time.
1) Could we have an option to merge these accounts into one?
Simular to how it works on your mobile contacts list where you can merge contacts.
or
2) Option to hide/delete non-active accounts
This would keep the Community member page more clean and useful.
It would ease readabillity and avoid mouse clicks if all screen space is used to show as much of a filter definition as possible in the Filters tab of an aggregate definition.