When we drag the output of a function it may create an assign in the content screen with variable 1 filled with the Output Var.
[Ideas] Drag of an output var of a function to the content screen creates the assign
[Ideas] [Timer] Set time schedule from ServiceStudio
On this way, when you set a scheduler for a timer in service studio, you also don't need to apply this schedule manualy on every environment when the oml/osp is first being published.
[Ideas] Order of "Find Usages"
[Ideas] GTE (Global Temporary Entity)
Create a private entity (per session basis) like Oracle's GTT.
https://oracle-base.com/articles/misc/temporary-tables
Sometimes a user wants to insert in a temporary table that other user cannot see.
regards,
IB
[Ideas] Simple query to advanced convertion
There could be some magic feature that would make this time saver feature. :-)
Then we could make a simple query to build the 'skeleton' of a query and then introduce the aditional rules that cannot be defined in a simple query.
[Ideas] Generate a structure from an entity
[Ideas] Make "Use NOLOCK" an option on queries
J.Ja
[Ideas] OML API/ accessing data
When are we gonna have a option to access the metadata from a OML file?
In my case i need to generate report for instance, all screens and their input/output parameters to a given Espace.
This information exist only in the OML file.
Therefore only the Service Studio is able to open it. Maybe some component which could translate it?
I think its important feature for enterprise grade Frameworks like Outsystems.
With best regards,
Slavi Popov
[Ideas] Make OAuth 2.0 a first-class citizen
A lot of people are using the IDP Forge component to provide authentication via OAuth 2.0 providers like Azure AD, Google or Okta. The problem with this is that it only has community based support, no build-in methods for protecting own build API's or being able to authenticate with external API Endpoints protected with OAuth 2.0.
I think we need to have IDP (or something alike) to be integrated within Outsystems and be support by Outsystems . It should also be made an authentication option for all assets that now can be protected with the build-in authentication methods (like screens and APIs). Also authenticating to other assets protected with OAuth 2.0 should be a native capability.
[Ideas] Mobile - New events to allow interaction on device with automatic eSpace update
To improve the mobile framework I consider interesting to add two additional events on "Logic - Cliente Actions" which allows gatter information and interacts with the automatic update processo that is fired after an eSpace publication.
The two new events may be:
- An event to occurr before the update process and that results to a boolean named "allow". If its value has been setted to "true", it would allow an update, and if it has been setted to "false", would not.
- An event to occurr at the end of the upgrade process. It could indicate the eSpaces and versions that were updated and if the update succeeded or failed.
The reason for both suggestions is to give to developer more control and information about the version of eSpaces that are installed on Android device or iOS.
Best regards.
[Ideas] Back Button for Back in Browser History
Sometimes we have to go back to a previous page.
We can do it in 3 ways:
1 - A button that has a specific link!
For example, I'm in a page with a List of Employees, and click in one of the Employees in the list, going to his Detail Page. There I have a button saying back that goes back to the list.
The problem of this solution is that If I can access the same page from a different place, when I click the back button I go to the Employee List Page and not to the page I was.
2 - A button that runs a Javascript!
I can have a button that runs the following javascript :
window.history.back();
return false;
This reproduce the back button web browser behavior.
The problem of this solution, are the Pop-Ups. If you open a Pop-Up in the page you are and run the javascript above, it goes back to the same page again. So in the end you stay in the same page.
3 - You can pass the Original URL as a parameter.
If you pass the Original URL as an input parameter of the next page you will access, you can always redirect the user to this URL again through a button or a link.
The idea is to make this a pattern!
OutSystems pages could always receive this Original URL input parameter behind the hood.
And could exist a component that would be a button or link that when clicked, redirects the User to this hidden URL.
This way we can always have the possibility to send the User back to the previous page!
[Ideas] Debug "Lite"
[Ideas] Public Variable
Maybe a nice alternativa to another idea that I released earlier:
http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=777
I hope it makes sense for you as it makes for me.
Cheers.
[Ideas] Output variables in WebBlocks
Add output parameters in WebBlocks so you can reuse the data on parent screen or block.
[Ideas] Publish and Subscribe
Build in a "Publish and Subscribe" functionality into the OutSystems platform.
[Ideas] Show Unused Attributes in Structures & Entities
Could be helpful to see what Attributes in an Entity / Structure are being used. Similar to Unused Local Variables but maybe with a toggle feature? Without having to go through every Attribute using Find Usages.
[Ideas] WSDL Import support for unbounded attributes inside other unbounded attributes
Many Integration platforms generates WSDL's with an unbounded attribute type inside other unbounded attribute type. Service Studio considers these pattern as an unsupported type and there's no reason for it, its completely possible to map this with outsystems structures.
Service studio supports this scenario if the child structure has more attributes than the unbounded one.
[Ideas] New feature: Don't let Service Studio Freeze and block so often
[Ideas] eSpace metatags
[Ideas] Best practices
- If there are any advance queries, replace that by aggregate
- Don't use foreach Loop in preparation
- Don't use if conditions in preparation
- i.e try to avoid if conditions in aggregate
- Apply pagination on list page
- Don't show more than 100 records on single page
- Move JavaScript webblocks to bottom of page
- Don't use preparation aggregates directly in screen actions
- Before using them in screen actions refresh them