I can understand not wanting the value to be blank for key values, but for text values, it's a bit strange to have a non-blank "blank".
Preferably, though, it would have been nice to have the Values be expressions (like "" or NullIdentifier(), even if it converted it to text) instead of straight text.
Hi there, if i have two applications with BPT, say it A and B, for a given user in those applications, if i open an application A, the TaskBox also show tasks from application B. Isn't it a good idea just to show tasks per application basis, not peruser basis?
regards,
Tan
Today platform only allows SOAP 1.1 but many time there are services in SOAP 1.2 and sould be good to support it.
Please, make a combo box to show page numbers in pagination. This is pretty usefull if we want to go to a specific page of records. For instance, if my query returns 1000 records and my table records only show 10 records for each page, we will have 100 pages. Now imagine i want to go directly to page 50. I have to drill down the pagination until i reach page number 50. This can be pretty frustrating. With the combo box, i can go directly to page number 50.
Expression Editor in version 9 often opens up scrolled all the way down to the bottom. That means that when you open a multi-line expression, you only see the last line and need to scroll up to see the remainder of it.
J.Ja
When you're working on the OS PaaS environment, the time that is displayed when a module is deployed is the server time. I would be nice to have a setting in lifetime where we can set our own timezone so for our company the correct time when an application is deployed is shown.
In some cases we need to check when something was deployed and we need to 'calculate' when it was deployed. Als when people don't know it's a different timezone the will be some communication errors.
It's that small thing that make life easier (-:
Outsystems Consume REST functionality already interprets underscore casing, to Pascal casing and vice versa - the same should be implemented for Outsystems expose REST functionality.
Most of outsystems developers use pascal casing to build their application; However when an external application and external developer consumes an exposed REST service, the de facto standard naming convention for REST is to be used, that is the underscore naming convention.
Example
ClientId would be Interchangeably interpreted as client_id and vice versa
ThisIsAnExample would be Interchangeably interpreted as this_is_an_example and vice versa
yetAnotherExample would be Interchangeably interpreted as yet_another_example and vice versa
Developers should be able to build their app as they normally would with outsystems platform using Pascal casing naming convention for REST Input/output parameters and JSON request/response structures - and outsystems would be able to convert between pascal/camel casing and underscore casing.
Request:
Developer could enable an option accept "underscore casing" compatibility or outsystems can build this in by default.
Response:
REST response could response back with either Pascal casing or underscore casing (there should be an option to enable this OR at least add a "OnAfterResponse" action to let the developer manipulate the REST service method response.
I would like to do a search (and replace) on the selected part of an action,
When I click on an action or entity and press delete, sometimes the name of that action/entity is deleted and not the action/entity itself. I have to right-click on it and select delete from the menu. I am not sure when this happens, a lot of the times the delete button does work.
This is especially annoying when I want to copy-paste something with the same name. I'd want to delete the old action/entity first, then paste the new one with the same name to keep all the references working.
Too change the name of an action or entity I can already use F2.
In order to build semantically correct web pages it is critical to have these elements. The platform should support these elements natively in the Web Screen Editor.
Whenever we are on the viewing the widget tree of a page or Webblock, if we click on the "Go to <insert element here>" we continue on the same widget tree view mode and need to click again on the widget tree icon to finally see the element we selected as demonstrated on the gif below.The rationale is that if we are using the "Go to" context menu, 9 out of 10 times we want to open the original module to inspect/change the element selected.
It would be nice that when we use the "Go to <insert element here>" context menu it would change to the view that actually allow us to "go" to that element
When I click the field for, in this example, the List to clear in the ListClear Server Action, OS grabs a lot of lists for me to Suggest, but as I type, that list is not filtered to those lists starting with what I have typed:
If I double click List, the Expression Editor box appears and I can hit CTRL-SPACE for it to suggest a filtered list for me, like so:
That's awesome. Can we just move this filtered autocomplete behavior up one step to the screen I shotted above?
It would be interesting to have an internal forge for the company, it may be necessary for the company to create plugins and for reasons of intellectual property it is not possible to make it available in the public forge, so having an internal forge would be a very welcome feature.
When selecting multiple objects, I often need to know how many did I select, this is something that I've seen across other IDE's and feels very natural to have.
I created an example with the number below:
It would be nice if extra output parameters are added to the Excel To Record List to check if the conversion from excel to a record list was done successfully. Currently you can catch these errors with a All Exception handler. But if you are able to check the output parameters of the action, you can set a custom exception.
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