I was just replicating a bug I found on the forum for a follow up with the devs. Once I hear back from them, I'll delete this thread again, just leaving it up until I know if they need it to check my report.
[Forums] Testquestion - please ignore
[Forums] Testquestion - please ignore
Why post if we have to ignore this post?
[Forums] Server Action About
Quite simple friend,
its enough to make the condition like:
OrderStatusId -> input parameter
OrderStatusId = NullIdentifier() or OrderStatusId = Order.OrderStatusId
regards
[Ideas] Show SS/SC/LT version number at the new features in the what's new page
Hello,
When looking at the whats new page (this one) there are a lot of features but you can't see in which version it was released. You can only see it when you navigate to the details.
So it would be nice if the service studio/service center/lifetime version number is also displayed in the whats new page. Have made an example for this:
Kind regards,
Evert
[Ideas] Right-Click + Export Entity / Structures
It would be helpful if we could right-click an entity or structure or anything in the "Data" tab and export it as JSON or to an Excel.
[Ideas] Test an Action like "Test query" (for unit testing)
Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.
[Ideas] OFFSET and NEXT ROWS part of an Aggregate
Looked at the Large List Navigation Sample in the Forge today, I think this should be part of the Aggregate for faster lest memory intensive data fetching.
[Ideas] In service module API should create automatically like scaffolding entity in screen if we drop entity.
Hi Team,
In service module,If i drop entity in REST or SOAP by using scaffolding all the standard method need to creates like the same when we drop entity in main flow.
Thanks!
[Ideas] Open screens i had open in last session.
My suggestion is to save the opened files per user.
[Ideas] Service Center: Producers Catalog
In large factories it can be time consuming to find out which producer and if there is any producer with the action / web block / ... we intend to use. It would be very helpful to have a page where we could search for existing components
[Ideas] Password policy settings
[Ideas] Property Cache in Minutes set with a variable
[Ideas] Allow community member discussion threads on a training video page
It would be nice, that community members can start/read discussions on each training video page on the outsystems.com/learn site.
So what I have in mind is a the page where the video is to have a discussion thread at the bottom of that page.
[Ideas] Simple query boolean expressions: allow checking without true/false
Normal expressions allow booleans to be evaluated without comparison, and the not operator, e.g.:
if(not myBool, "hello", "hi")
In simple query expressions however, we need to explicitly check against True or False, and the not operator is not allowed:
Entity.Attribute = False
I'd consider that bad coding style in a normal expression. Why can't we use "proper" boolean expressions in simple queries?
[Ideas] Resolved Posts
when a post solves a problem in forum should be marked as resolved.
[Ideas] 'Title Case' Built-in Function
A new text built-in function added to Service Studio that formats any input string into title case format.
Examples:
- this would be a useful function ; This Would Be A Useful Function
- paulo rosado ; Paulo Rosado
[Ideas] Vote in specific idea comments that we think better qualify idea refinements
It would be great to be able to vote on comments that better align with solving the idea proposal.
Many times we see any sort of solutions that may create a lot more problems that the one the idea proposes to solve.
And as sometimes we have experience on identifying the better solutions/proposals we can collaborate marking the ones we think are better solutions, and of the same form we can vote down the ones that we see can cause more problems.
[Ideas] Built-in Unit testing capabilities
Service Studio should have new, separate "Tests" tab.
This would enable integrating tests to any eSpace and would minimize required overhead for testing any action, including private actions.
Why?
- Testing your code is more professional than not testing.
- Unit testing should be minimal extra effort for developer, because otherwise tests are usually not done.
- Publishing new code could be controlled - you cannot publish untested code, or code which has some failing tests, for example.
- Test code should never go to Production environment.
- Testing is good.
How?
- Tests are integrated to eSpace/module oml file.
- During code generation process, actions from "Tests" tab would create a separate .NET project and this project would be a friend assembly (internalsVisibleTo attributes configured) for main project to compile.
- 1-Click Publish deployments with tests could start from (currently underused?) personal area (or another IIS folder), where tests would be run.
- Depending on how tests go and how is decided in additional configuration, deployment would continue to Public area or show an error in Service studio.
This way, creating unit tests would be as effortless as when creating unit tests in any other modern programming language - just few clicks away. There could be also accelerators to generate unit test actions or "system events" to initialize/teardown test runs.
Currently, writing any tests to private actions is also either impossible or exposing some unwanted/test related code to production environments.
It's a big change, but from discussions with makers/experts @ ODC I've learned this should not be too far-fetched idea to implement. Maybe for P12, please?
Another, possibly the simplest way to enable testing / production code separation without massive modifications to existing compiling process could be a capability to define another espace as "friend" espace. This per-espace setting could reveal internal (=OS private) actions to the another espace marked as a friend and thus enable referencing these otherwise out-of-the scope actions for testing purposes.
If done like this, feature could be achieved using small amounts of .NET reflection trickery or previously suggested InternalsVisibleTo attribute (that has been around since 2002 release of .NET 2.0).
Security-wise, there should be no problems either, (albeit a bit more work during compilation) as friend assemblies can be defined as signed assemblies, too.
Personal opinion, but this topic is really heavily connected with OS small book #2, #5 and #7.
[Ideas] Consistent Versioning between Development Environment and Release Notes
Hey there,
Problem
Since Outsystems 11, the versioning on the release notes web page changed to show the Release number instead of the Version number:
But if we look at the version of our Development Environment, we see the version number:
There is no way to know (at least that I know of) the match between Version and Release numbers other than downloading a Release version, installing and see what is that version belongs.
Idea
Show on the Release Notes and Development Environment both Release and Version Numbers
[Ideas] Remove the auto margin-top of 10px
Title says it all.
It would be great if the auto margin-top of 10px that appears any time you add a component was removed or could be turned off.
Needless to says it is insanely annoying. If I want margin I will add it trough a proper css class, I don't see why it should be forced on us.
Disclaimer : this was a rant.
Sincerely,
David