Quantcast
Channel: OutSystems Community
Viewing all 1476385 articles
Browse latest View live

[Ideas] Allow additional application metadata in Service Studio

$
0
0

We would like to be able to add additional metadata to applications in Service Studio. You can now only enter an application name and a description. We would like to be able to also add:

- Owners (free format field to enter one or more names; alternatively a real list)

- Suite (free format field to enter a name for an application grouping)

These fields should also be searchable (separately).

Preferably, the system would remember the names entered and offer a drop-down that allows to select a previously used name or create a new one, but just some text fields would do for starters.


[Ideas] Show number and percentage of successful implementations of a Forge component

$
0
0

Allow users that downloaded a Forge component to tag the component with "successfully implemented". This can then be used to display the number and percentage (successful / downloads) of users that actually got the component working on the Forge. This could be displayed next to the rating.

The success score could also be added to the filter. For example, show only components with a success score > 50%.

Optionally, allow a user that successfully implemented a component to indicate he/she can be contacted for help. These people could then be listed under the support tab of the component.

[Ideas] Foreign Key Platform Default Delete Rule per environment

$
0
0

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!

[Ideas] Local Application Testing

$
0
0

Hello everyone,

Can we create an option to test your outsystems application in a local browser without publishing the code on server?

[Ideas] Query RecordLists

$
0
0

the possibility to query a record list (ie. local/input variable) would rock!


instead of querying/manipulating one/multiple entities multiple times, untill you have all relevant data together.

why not query a record list already available? even if it consists only of structures


this would seriously increase performance and reduce complexity.


specially since you dont need those loops with an IF anymore, that simply skip all records untill youve reached the one you want.


thanks for liking!

[Ideas] Paginate "Open other version" list

$
0
0

It's too painfull when you have to open the list of previous version for an espace when you know there are thousands of previous versions. I know we can always delete previous versions, but improving that screen would help a lot. Not only pagination, but also improving search filters.

[Ideas] Improved tooltips for widgets

$
0
0

Text tooltips provide limited help most of the time, specially when we're talking about visual components like widgets, Service Studio could have some tooltips on steroids like these ones:


[Ideas] Remove OLD ideas from the ideas list...

$
0
0

Some ideas are already 3 or more years old and never made it into the product. From a client perspective: having a requirement that is not implemented for 3 years is bizar. especilally in an Agile/Scrum environment with 2 weeks sprints. 


I understand that ideas are not requirements. However I presume that everyone hopes it will make it at least to the requierement list sometimes and if not then that should be clear.


It is not very motivating to see even popular ideas not picked up for years and years. Personally I don't add any new ideas to this list for this reason.


My proposal is to have a quicker turnaround; is an idea interesting enough then it should move on, if not then remove it or place it on the not-to-be implemented list. You could do something with levels and voting.


Please do something about this. The state the idea list is now in is not to be taken seriously.





[Ideas] Make "Refactor" supported component

[Ideas] RecordListToExcel widget column export order

$
0
0

It would be nice to be able to set the required order of columns when output in the excel file.

We've had various requirements/complaints about the column ordering in exported files that make life harder than it needs to be for business users.

PS: I am eager to assist in extending the widget ;)

[Ideas] Outsystems Community - User Profile - User Ideas

$
0
0

On the community site, if we click on our login name on top we go to our profile page.


On the tab ideas, appears all the ideas that we suggested.


when i idea is marked as done it still appears on the list.


I can suggest some kind of  filter for that list to exclude by default the ideas that have been done. 

Like a status for something like on going ideas and ideas marked as done. Ideas that still "open" can appear as default.

[Ideas] Input Parameter Invisible

$
0
0

Hi Guys, We could tell (in the properties) if the input parameters of a Web Screen whether is or not it is visible in the URL.

[Ideas] [ServiceStudio] Convert XML to Structures and Entities.

$
0
0
Enable the ability to import a XML file and convert XML to a Structures or an Entities.

For example, you import the following XML file

<?xml version="1.0"?>
   <Structure Name="User_AuthRequest"><Attributes><Attribute Name="Username" DataType="Text" /><Attribute Name="Password" DataType="Text" /></Attributes></Structure>
 
ServiceStudio will create a structure "User_AuthRequest" with attributes "Username" and "Password"


[Ideas] [ServiceStudio] Display physical database table name for a given entity.

$
0
0
Sometimes you might want to verify if the correct data has been inserted into a table, or would like to insert records into a table manually. It be good to know the physical name of a given entity.

[Ideas] Default Feedback Message, List and Detali Screen Messages and other Texts

$
0
0

The idea is allow developer to set the default texts generated by scaffoldings:

  • Feedback Messages in Detail Screen
  • "Save" and "Cancel" buttons text in Detail Screen
  • TableRecords Empty Message (List Screen)
  • New Record button text, "Search" and "Clear" button text in List Screens.
  • And other automatically generated texts

[Ideas] Be able to collapse Mapping assignments

$
0
0

Since P10, we can use Mapping assigments when assigning two structures of different type (which is great!). However, when there are many of them, it would be nice if they were collapsable so to hide the details of the mapping. A black triangular arrow on the grey "Mapping" bar would be ideal.

An example of when this would be useful:

[Ideas] Categorize User Actions

$
0
0
I think it would be really nice to be able to have our user actions separated be categories, just like the built-in ones are.

This would really help when you are creating big projects or when you're trying to consume from a project with which you are not completely familiar.

[Ideas] When we are debugging and we stop at Aggregates or Advanced queries fill test inputs

$
0
0

Hi,

A lot of times when we are debugging and we are going to check what is wrong with a query what we do is copy one by one the values on debug to the aggregate or advanced query.

So it will be nice if they are empty, we fill them automatically when we open them.

Thanks 

[Ideas] Get out of the widget tree view when clicking on "Go to "

$
0
0

Whenever we are on the viewing the widget tree of a page or Webblock, if we click on the "Go to <insert element here>" we continue on the same widget tree view mode and need to click again on the widget tree icon to finally see the element we selected as demonstrated on the gif below.

The rationale is that if we are using the "Go to" context menu, 9 out of 10 times we want to open the original module to inspect/change the element selected.

It would be nice that when we use the "Go to <insert element here>" context menu it would change to the view that actually allow us to "go" to that element

[Ideas] Automatic Deployments (Nightly Build / Continuous Deployment to Regression )

$
0
0

Hi,


I would like to see a supported way of the automatic publication of solutions.


Currently there is a Solutions API webservice on the ServiceCenter eSpace which should do the trick, but this API is not working on the Enterprise Edition of the Outsystems Platform. (See my message in the Download & Deploy Forge module: http://www.outsystems.com/forums/discussion/16566/download-deploy-you-are-not-allowed-to-use-this-api/).


This idea can be used to:

1. Create a Nightly Build to see broken references in the morning.

2. Create a Continuous Deployment function to the Regression Environment that could publish the latest version of one of more applications on the Development environment to a regression environment and automatically start the Regression tests with a specific timeslot or continuous after each regression test is finished.


Maybe other users might have other good ideas.

Viewing all 1476385 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>