<wsdl:definitions xmlns:s0="http://www.outsystems.com" ...............targetNamespace="http://www.outsystems.com">
<wsdl:definitions xmlns:s0="http://www.outsystems.com" ...............targetNamespace="http://www.outsystems.com">
On the right hand side of the screen in service studio you find the tabs Processes, Interface, Logic and Data. Almost all items in those tabs can be extended. This makes this list cluttered and makes me scroll to find the things I’m looking for. A button [Collapse all] would be nice and save me some valuable annoying scrolling time.
GraphQL is an API standard that provides a more efficient, powerful and flexible alternative to REST web services.
Source: https://graphql.org/
After discuss ( Post ) and explore an issue i have i think you can improve User_login action on Users ( system components ).
The Audit_Login_Error, should only log if all LoginAttempts fails, if you have a successfull logged in, you shouldn't recived error log.
Best Regards.
It would be great if the templating functionality could be extended so that it works with more than just espaces. For example being able to set a template for the entity creation could pre create certain fields and pre create the crud operations with appropriate common logic allowing us to then just add the missing details.
Creating templates for things such as creating structures, entities, screens, webblocks, rest producers, actions etc would significantly improve development speed and consistency in large projects that have multiple developers. Would also allow us to use our tier 1 devs to build a lot of the templates and framework and less experienced devs then to put together the details whilst knowing they are following the base standards by default.
A good example is that we build detailed versioning into every one of our entities. Another would be to include preset exception handlers in actions and so on.
I will be good to have a show-hide ability in column structure.
Scenario-
I have used four column structure. inside each column, I have put dashboard boxes. And all these boxes are the role-based boxes. for admin, all 4 will be visible. for another role, only the first column and last column will be visible.
So here I am facing the issue at the design level. in the center two blank column is visible.
If the column structure will have this ability like hide the column if it is empty will be good.
When you drag a Destination node over an End node in a client action, a screen pops up as below asking you which destination you would like:
To match the New Client Action and New Server Action nodes, there should be a button in the bottom left-hand corner where you can create a new screen and have it be set as the destination of the node at the same time.
Hi everyone,
We have been facing an issue regarding the solution publish
Nowadays, the solution will stop at step 11 waiting for a user to press "Continue" or "Abort" the solution publish.
Now in small factories, its easy to control the users that will perform this action.
In my case, sometimes we have more than one person doing the continue.
What we found is that the "Continue" option doesn't validate that the solution is already "on going", ending up on a large locks, on espaces, from one solution to the other, and in consequence a timeout will appear ending the solution publish.
Add tools to allow the enhanced organization of application icons in the user's environment in Service Studio. Filter, Sort, View mode (List, thumbnails, ..), ...
I know this is very ambitious and I also know that this not fits the platforms current architecure and structure, but it would be so freakin' awesome if you could test things locally without the need for a cloud (server). Publishing sometimes seems like the only thing we're doing, the waiting is annoying and most of the time takes just a few seconds to long (bad UX). Just saying but hope the day will come the we can run (maybe stripped versions) locally.
I should be able to right-click a GetXYZ Action in a workflow (or cut/paste as Aggregate) to convert it to an Aggregate, and then the code should refactor to use GetXYZById.List.Current instead of GetXYZ.Record.XYZ
J.Ja
- Say, there are two REST API methods exposed from an Outsyestems server (X) that is consumed from another Outsyestems server (Y)
- If we add another method in X than we can refresh in Y such that the third method is also shown in the IDE that consumes the X
It is often a pain to write or update structures that are required for use in SQL queries so would be ideal to be able to write the SQL and as long as it is valid, be able to create a structure off of the Select statement. The update may be more of a challenge but if done well it could ensure consistency between columns in structures vs query.
Hello,
When Page loads Table record displays first 10 row of aggregate but I checked in prepration aggregate fetched 11 row from database id anyone having any idea why aggregate fetching 11 rows first time and when click on next page then it fetching 11+10= 21 rows, It means first time it is fetching Line Count of Table Records +1=11 row.
As per my understanding if I click on page number 5th then aggregate will fetch 51 records in this way there will be performance issue when record count is large so my suggestion is it should be handled in way no matter in which page number user click aggregate/advance sql will fetch only that page data from database to improve performance.
Regards
-SK-
One of the barriers to implement business processes in OutSystems is having to redo all your processes (already designed/implemented with common BPMN tools/engines), with a different syntax and in a different, lower-level IDE like Service Studio.
Providing a robust import of BPMN files and export of BPT diagrams to BPMN would eliminate this barrier, make it easier for organisations to fully migrate to BPT (using robust OutSystems controlled template patterns for the BPMN concepts).
On top of this, if this process can allow for round-trip export-import (upgrading existing BPT process definitions from an updated version of a BPMN diagram), business users can continue to use tools they are familiar with and are industry standards to design the processes, with guarantees that it would correctly reflect on their OutSystems implementation.