Great article! \o/
↧
[Forums] OutSystems UI Framework: Past, Present, and Future
↧
[Ideas] Tag someone in comment
It would be very good If can add someone's name to the comment of post/idea by typing @(Or any other way).
Once typed @, It should list all the people who are in touch with that post/idea.
So, That person will get notified that it is relevant to him.
↧
↧
[Ideas] New LifeTime Infrastructure Permission to control usage of the Forge Update Notification widget
It would be nice that there is a setting in LifeTime role that steers if platform users with given role are allowed to update components listed under the notification widget.
In enterprise environments we don't want any time of platform user just being able to install an update.
↧
[Ideas] More prominent location of the "Refresh all open consumers"-option
The option "Refresh all open consumers" is a great shortcut to refresh dependencies, but since it is a little bit hidden under the menu-item 'module', a lot of people don't know about it or simply forget that it is there. It would be great to have an icon appear somewhere in sight when this is relevant, like in the picture attached.
If this is not an option I'll settle for the keyboard-shortcut that is proposed in the idea below :)
https://www.outsystems.com/ideas/2976/keyboard-shortcut-for-refresh-all-open-consumers-aka-offline-refresh?IsFromAdvancedSearch=True
↧
[Ideas] Allow Reply-To Address parameter in the plataform's emails
The platform should allow for the Reply-To Address to be set when an email is being generated.
↧
↧
[Ideas] Basic Authentication to Consume SOAP Web Service
I have a web address that requires a username and password to access the WSDL. (Basic Authentication)
Therefore, I cannot consume the SOAP Web Service directly within OutSystems (Integrations -> SOAP -> Consume SOAP Web Service)
I have to create a local copy of the WSDL and save it locally including EVERY XSD within the WSDL. I then have to manually map the WSDL to the local XSD's.
Then I consume the LOCAL WSDL and all works.
Extremely time consuming for large WSDLs.
We want to use the 'Consume SOAP Web Service' and simply pass in the username and password (optional)
↧
[Ideas] Make 1CP (One Click Publish) live up to its name!
Many years ago, when I used to program in C (!), I could make a change in some source code buried deep in an application and run "make". It was smart enough to only compile the required code, so I could just go and grab a coffee and when I came back it was ready to test. Same applies to many modern build tools (e.g. "grunt/gradle"), in fact they even monitor file changes, so you don't even have to explicitly run a command.
But with OS, if I make a change in a deep espace I either have to work out which consumers are affected and manually publish them one by one in the right order or run an "all content" solution which will take ages. There is a "Publish all consumers" option, but it is "dumb" and just publishes the entire dependency tree, regardless of the nature of the change, so can end up being little better than an "all content". Then when I come back (from lunch, because I can't drink that many coffees), I have to wait for first load delays to finally see the results of my change...
I suggest this:
1. If I make a change, for example, inside an action, then 1CP should work out which espaces use THAT action and only publish them, while ensuring that nothing else needs refreshing for me to actually see the result.
2. It should then (optionally, but automatically) precompile them so there are no first load delays. I don't mind being offered a list of entry point consumer espaces to limit the scope, as long as this is shown at the start - so I can go a get my coffee.
Now THAT is One Click Publishing!
↧
[Ideas] Set "Default" button programmatically
Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If.
J.Ja
J.Ja
↧
[Ideas] ListSplit
I'd love to have a ListSplit System Action, that performs a ListFilter, but also outputs all the other elements in a second list. So say I have a List with an Attribute "Value" and the input to ListSplit is "Value > 1000", I'd get two lists, one with all Values upto 1000, and one with all Values above 1000.
↧
↧
[Ideas] AntiSpam button properties
Property true/false to avoid multiple click button/links
↧
[Ideas] GetEntity(Id)
Does not throw exception if Id not found. return empty record instead.
↧
[Ideas] Faster Solution Publish - Large Factories
Hello Guys,
It would be great if solution publish process could be enhanced to be faster. Our project has many modules and takes longer than we require in our continuous integration process to publish a solution.
Just to give a bit of context with an example - in our daily continuous integration process, we publish a solution against our DEV environment and, if everything goes well, we push it to the next environment for next day QA testing. The issue we face is that with the time it takes, if anything goes wrong with either of these solution publishes, we can have a hard time to react on time to fix the problem and to try again, on the same day.
↧
[Ideas] Mobile App - Customize Error Screen
Hello,
I would like to make the error screen multilingual (I use the Outsystems R&D component Multilingual Mobile Component). In the documentation provided by you about Customize the Errors Screen this seems not possible at the moment.
I would suggest either to customize the screen HTML structure on Extensible Configurations or to have some kind of configuration for messages to be compliant with Multilingual Mobile Component.
Thanks
↧
↧
[Ideas] Start one department in support to answer tickets of Forge components
Hi
I'm not sure if I should give this feedback here but I didn't find any other option.
Whenever we create a support ticket where Forge component is used, support says that we can't provide support because it is not supported by Outsystems.
Please note that we have downloaded the component from Outsystems web site and Outsystems should take responsibility to resolve queries related with that component if the owner of component is not answering the questions.
Support people should be able to read the code provided by us and try to debug what is going wrong. If you don't have enough bandwidth, please start one department for such tickets because customers are ready to pay for it.
Also, if support people can't solve that query they should check if my company has OnDemand implementation license and if my company has that license they should forward my ticket to that department which will save time for us.
Thanks and Regards,
Suraj Borade
↧
[Ideas] Custom reminders before interacting with any kind of element in Service Studio
Hi,
I got this Idea from an ERP, that I think perfectly fit in Low Code methodology, adapted for Developers using Service Studio.
It would be a good feature to add and manage custom reminders that will Pop Up every time a developer add, edit or view a new kind of Element in Service Studio. This reminders would be by application.
Every developer would be able to access and manage every reminder, adding a new one, edit ou delete.
Every time a developer add, update or delete an element, Service Studio will show every Reminder stored for this element, and developer would be able to mark it as completed.
Examples:
Before creating a new Server Action, we want to make sure developer know the naming convention. We could create a reminder, something like "Name should be [Domain]+[Action]+[Verb], Pascal Case"
Before creating a new Screen, we need to put a known Server Action in Preparation for Auditing proposes: "Don't forget to add Server Action 'ScreenAuditLog' to Preparation"
Before creating a new Role, something like "Role Name should begin with 'ROL_' so it will synchronize with legacy SingleSignOn.
Before a Module Name "After changing Module name don't forget to change every JavaScript and CSS URLs hard coded with Module Name".
This is just a starting point for something that could be great. It will improve team collaboration and communication, minimizing distance and time barriers.
↧
[Ideas] Show an error or warning when adding mobile plugin eSpaces to an Application
According to https://www.outsystems.com/learn/courses/104/build-a-web-app-in-2-hours-outsystems-11/, "You must wrap each plugin in its own dedicated module and application, meaning that if you want to use several plugins you must create an application for each plugin, each containing a single wrapper module."
Missing this little bit of information caused my team a very significant amount of time attempting to identify why our mobile application was building successfully but would not work. Ultimately, OutSystems Support was able to identify the issue.
Please consider adding an error, or at least a warning to Service Studio to inform people of this issue.
↧
[Ideas] Add the ability to consolidate screen or webblock css in the app theme
While testing an app it is easier to add CSS directly in a screen or webblock in order to quickly test it (becomes more relevant in scenarios using the 4layer canvas and having the theme being share in different modules).
After this process it could be interesting to quickly cut and paste the css from those specific screens or blocks in the application theme currently in use.
According to the dev best practices we should reduce inline css to avoid the load of additional css files and this could help in that task.
↧
↧
[Ideas] create entityties using a SQL create table script
Sometimes it's quicker to define a lot of entites using a sql script. The new excel thing looks perfectly but doesn't garantee all field types and specially sizes will be correct.
So add a menu option on the root of the entities containing the text "Import from sql script", only simple types can be used.
So add a menu option on the root of the entities containing the text "Import from sql script", only simple types can be used.
↧
[Ideas] Notification of new published version in service studio or auto download
If New version has published in server let notify on service studio.
or better auto download of new version into system.
↧
[Ideas] Make "Refresh Data" and "Ajax Refresh" needless and automatic
Just like you can rename identifiers (entity names, I/O/local variables, etc.) and have all their usages throughout the code be renamed instantly (from the point of view of the developer), identifier value changes (i.e., changes in variables, aggregates, etc.) could also be tracked when an action finishes on the same screen.
When this is the case, any parts of the screen that were rendered with variables, aggregates, etc. that were changed in the action should be AJAX-refreshed automatically. Aggregates refresh automatically if the primary keys that were changed are now on screen / are in the scope of the aggregate.
Tracking could occur either with a "dirty" flag for each variable/aggregate, or be performed after the action finishes on the same screen, comparing all screen widgets' variables'/aggregates' current values with the new values after the action finished (a bit like AngularJS v1 did).
I'm sure this is not as trivial as what I'm spelling out here, but this is the basic idea.
Eliminating these two ("Refresh Data" and "Ajax Refresh") would (IMHO) remove another roadblock for the "citizen developer" who will likely not be accustomed to being alert to disparate display/data refreshing requirements.
When this is the case, any parts of the screen that were rendered with variables, aggregates, etc. that were changed in the action should be AJAX-refreshed automatically. Aggregates refresh automatically if the primary keys that were changed are now on screen / are in the scope of the aggregate.
Tracking could occur either with a "dirty" flag for each variable/aggregate, or be performed after the action finishes on the same screen, comparing all screen widgets' variables'/aggregates' current values with the new values after the action finished (a bit like AngularJS v1 did).
I'm sure this is not as trivial as what I'm spelling out here, but this is the basic idea.
Eliminating these two ("Refresh Data" and "Ajax Refresh") would (IMHO) remove another roadblock for the "citizen developer" who will likely not be accustomed to being alert to disparate display/data refreshing requirements.
↧