It is often that we would want to see how much of our Application Objects are already consumed. Yes, we had the numbers under Licensing. But wouldn't it be nice to have something that when you click a number it will show you the breakdown for each application? That is, count of screens, entities, web services and connectors. Would be helpful as well if listing of these criterias is provided.
This is very important in terms in design, budget and sizing of future projects.
Hi!
We don't have a clear picture when to ask OutSystems to upgrade our PaaS. Although we aren't facing any issues with our environments, it would still be nice to be sure that you aren't lagging too much - in worst case you could drop outside of the upgrade path, couldn't you?
So an advisor would be useful .
It would be great to have a test at the end of each "path" to verify if you miss something important. Also it would be great if that question will be at the same format as on the certifications exams.
An exposed REST web service is consumed by various applications (mostly external applications).
Since we do not have control over external applications consuming our REST web service - changing an existing web service will often break existing consumer applications, there is a need for versioning control!
Learn from www.stripe.com and add the ability to publish multiple versions of a RESTful web service, where multiple versions of a web service is able to operate all at once.
Current work-around solution: clone eSpace, make changes to new eSpace, publish eSpace as a new version.
In Service Studio, when you create a new application it prompts you which template to use when creating a new module. Afterwards, if you go to add additional modules to the application, it doesn't prompt you for template and create a minimal module. If you are adding a new module to an application that has only had an extension, it again creates a minimal module without authentication, etc. It would be helpful to select which template to use every time you create a module.
An entity foreign key attribute has a Delete Rule property which can be set to Protect, Delete or Ignore by a developer in ServiceStudio. A Performance Best Practice is to set this to Ignore, but that could lead to database inconsistencies. Therefore, during development, it is safer to use Protect. This means developers need to remember to set this rule to Protect during development and then to Ignore after testing has been completed and before deploying to production if they want to conform to this Performance Best Practice.
You can imagine this process is prone to errors. So how cool would it be if you could set a Platform Default Delete Rule per environment in LifeTime or ServiceCenter and then be able to select 'Platform Default' as the Delete Rule in ServiceStudio?
So, for example, in DEV & QA the Platform Default Delete Rule could be set to Protect and in PRD it could be set to Ignore using LifeTime or ServiceCenter. Then, when a developer chooses 'Platform Default' as the Delete Rule on a foreign key in ServiceStudio, the platform makes sure that the Delete Rule is set to Protect on the database when Publishing/Deploying to DEV and QA and that the Delete Rule is set to Ignore on the database when Deploying to PRD. So the platform automatically sets the Delete Rule on the different environments according to Performance Best Practices!
I understand why we don't have it for Attributes, but it would be REALLY helpful on Attributes, to decide if it can be removed or not.
J.Ja
It would be nice add, edit and remove data directly in aggregate details, at least in development environment.
In service studio versions prior to version 9 it was possible to select/deselect all differences to merge at once, by clicking on the top checkbox in the list of the Foreign eSpace. That checkbox is no longer present in version 9.
It would be great to have this feature back.
Hi,
There must be one action which can automatically delete/truncate the entities created by users not the system entities because sometimes while testing the application we used to create lots of junk data and after that if want to clean the environment junk data it takes lots of effort if, we have more than 100 relational entities. Do not delete the data from static entity, only from standard entities, So that environment got cleaned easily. I know that for production this function must be disabled otherwise it will be a problem.
Regards,
Manish jawla
It would be nice to have an option to clone/duplicate an application in Service Studio in the application detail view like we have the option to edit and remove.
And also it would be nice to have the option to do the same to the modules inside but as an option.
Era óptimo poder criar em Outsystems um robot, semelhante aos Programa mais utilizados (Uipath e BluePrism)
https://www.outsystems.com/blog/posts/robotic-process-automation-low-code/
Chrome autocomplete combobox, blocked calendar picker.
Would it worthwhile to add buttons to the widget tree to toggle editable / visible states?
This does not need to be much more than the options you have on the layers with applications like Photoshop. Also the visibility state is only applicable to the service studio, and does not affect the object properties: Display
I believe it can be useful to track changes, especially where more than one developer is working on a module, as well as situations where you have multiple webblocks, widgets or overlapping placeholders on a webscreen.
If I have a record selected for a static entity and press CTRL + N nothing happens.
I need to go to the Records node of the static entity and press CTRL + N there to get a new record.
I would like to add a new record created also when I press CTRL + N when I have an attribute selected.
Please add the CTRL + N Add Record also on the right click menu from a record