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

[Ideas] Expose REST: Be able to interchangeably use Pascal/Camel casing and Underscore casing

$
0
0
Outsystems Consume REST functionality already interprets underscore casing, to Pascal casing and vice versa - the same should be implemented for Outsystems expose REST functionality.

Most of outsystems developers use pascal casing to build their application; However when an external application and external developer consumes an exposed REST service, the de facto standard naming convention for REST is to be used, that is the underscore naming convention.


Example

ClientId would be Interchangeably interpreted as client_id and vice versa

ThisIsAnExample would be Interchangeably interpreted as this_is_an_example and vice versa

yetAnotherExample would be Interchangeably interpreted as yet_another_example and vice versa
 

Developers should be able to build their app as they normally would with outsystems platform using Pascal casing naming convention for REST Input/output parameters and JSON request/response structures - and outsystems would be able to convert between pascal/camel casing and underscore casing.


Request:
Developer could enable an option accept "underscore casing" compatibility or outsystems can build this in by default.

Response:
REST response could response back with either Pascal casing or underscore casing (there should be an option to enable this OR at least add a "OnAfterResponse" action to let the developer manipulate the REST service method response.


[Ideas] Include SQL server hostnames in error messages

$
0
0
If you create a database connection to an external server, and test it, obviously you know that the server you are testing is the server that is down.

Unfortunately, if that server goes down after everything is up and working, and you attempt to publish, you will get an extremely cryptic error message that forces you to assume there is a problem with your local server.

Internal Error
 
 
Exception Details:
[1] Internal Error: Invalid compiler output.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)


No where in that error message does Service Studio (or even Service Center if compiling from there)  nor even in Lifetime does that error message tell you that the SQL problem is not with your local machine, but with an external SQL server.


Please include hostnames of the SQL server in question with the error messages, so that we know WHAT connection you are referring to. It will save people HOURS of work.


Sincerely,
Braxton Bragg

[Ideas] Allow more than just "alphanumeric characters" in the value property of a Special List inside a ComboBox.

$
0
0
The Special Variable allows for Text, Phone Number or Email type variables once you start typing text in the Value 1 property. However, it only allows for alphanumeric characters in the value properties, which makes it impossible to enter an email address for example.
In my case, I need values like "Before+" (not allowed) and "Before-" (allowed), while they would fit perfectly in the assigned special variable, which is a Text.
(Edit: This is in version 8. I didn't confirm yet that the problem exists in version 9 as well)

[Ideas] New feature: Don't let Service Studio Freeze and block so often

$
0
0
It would be wonderful if Service Studio stopped blocking so many times. You can even add a checkbox asking users if they want this feature enabled or not

[Ideas] IsNull built-in function

$
0
0
It would be nice to have built-in function acting like SQL IsNull:
    IsNull(value, replacementValue)
    - returns value if it is not null / not default, or replacementValue if value is null / default

Currently, you have to use If like this: Value = If(Value = "", ReplacementValue, Value). In many cases Value and ReplacementValue are fields of entity/structure, which might be a field of other structure, so you know how the expression can be quite long in reality. It would be much clearer, and less chance for mistakes (like when you accidentally put something else in place of Value inside If) with IsNull function.

[Ideas] [ServiceStudio] Add the ability to create a REST API documentation for multiple web services, (not just 1 web service)

$
0
0
When you EXPOSE a REST web service, and set Documentation property to "yes", you will be able to access your web service documentation via
 
https://<SERVER>/<eSpace>/rest/<WebService>

Sometimes you might add multiple web services under a single eSpaces, now if you want to view all REST API documentation, the documentation should be available at

https://<SERVER>/<eSpace>/rest/

(It would be even better if we could just combine and edit multiple API documentation from various eSpaces.)

[Ideas] [Integration Studio] Import database, add the ability to detect when a table you added no longer exist (has been deleted)

$
0
0
If you sync a database and use a deleted table in your app, an error will occur.

When using the "Import database" feature via Integration Studio, add the ability to detect when a table you've added previous, no longer exist (has been deleted).

Detection should occur when integration studio connects to the database server and has re-imported the database using the same database (same connection string) and also when the user selects to manually refreshed a given table.

Note: You might also want to add a method to verify the integrity of database via Platform database API. 

[Ideas] [Integration Studio] When a database is imported, all naming should be converted to camel casing (alias), in order for the imported database entities to display and use correctly with scaffolding via service studio.

$
0
0
When a database is imported, all naming should be converted to camel casing (alias),  in order for the imported database entities to display and use correctly with scaffolding via service studio.


Example
Lowercase with an underscore word separator (mysql database standard naming convention)
user_account_role ----> UserAccountRole

Uppercase with an underscore word separator (Oracle database standard naming convention
USER_ACCOUNT_ROLE ---> UserAccountRole


Note: Original table, column naming should be kept in order to avoid issues and for developers own viewing, the original name is to be displayed in the property details, similar to expose REST structure, structure attribute original name property. 




[Ideas] [Integration Studio] Similar to service studio "Convert to static entity" feature, there should be a "Convert to static entity" for imported database tables.

[Ideas] Consume REST services - put the full response (including headers) in the error logs

$
0
0
It's impossible to debug these things without it.

J.Ja

[Ideas] Turn the SortRecordList (extension) into a built-in/system action

[Ideas] Aggregate with distinct

$
0
0
Aggregate should have an option to remove duplicates.

I see this as a new tab like "Sorting" where you could select the column you want to remove duplicates.

[Downloads] Platform Server 8.0.1.50 Connector for WebLogic

$
0
0

What's New in 8.0.1.50
  • Added support to Edge Browser (#991318)

Fixed in 8.0.1.50
  • Fixed error editing Database Catalog description in Service Center (#867581)
  • Fixed SEO Site rules not being applied in Oracle installations (#1020695)
  • Fixed extension download version and user information in Integration Studio "Download Other Versions" dialog (#429597)
  • Fixed minor issues in eSpace and Solution Edit screens in Service Center (#908661)
Compatibility
  • Compatible with Platform Server Version 8.0.1
  • Compatible with Development Environment Version 8.0.1
Additional Resources For further information on any issues, please contact Product Support.

NOTICE: OutSystems does not give support to any undesirable behavior you may experience due to the use or manipulation of undocumented components of the OutSystems Platform, such as, internal JavaScript, RuntimePlatform library, database system meta-model, components in installation directories, etc.

[Downloads] Platform Server 8.0.1.50 Connector for JBoss 7 Community

$
0
0

What's New in 8.0.1.50
  • Added support to Edge Browser (#991318)

Fixed in 8.0.1.50
  • Fixed error editing Database Catalog description in Service Center (#867581)
  • Fixed SEO Site rules not being applied in Oracle installations (#1020695)
  • Fixed extension download version and user information in Integration Studio "Download Other Versions" dialog (#429597)
  • Fixed minor issues in eSpace and Solution Edit screens in Service Center (#908661)
Compatibility
  • Compatible with Platform Server Version 8.0.1
  • Compatible with Development Environment Version 8.0.1
Additional Resources For further information on any issues, please contact Product Support.

NOTICE: OutSystems does not give support to any undesirable behavior you may experience due to the use or manipulation of undocumented components of the OutSystems Platform, such as, internal JavaScript, RuntimePlatform library, database system meta-model, components in installation directories, etc.

[Downloads] Development Environment 8.0.1.50

$
0
0

Fixed in 8.0.1.50
  • Service Studio
    • Performance improvements to Add/Remove references dialog window (#1022476)

  • Integration Studio
    • Added option to set Java location in Integration Studio (#1002213)
Compatibility
  • Compatible with Platform Server Version 8.0.1
  • Compatible with Development Environment Version 8.0.1
Additional Resources For further information on any issues, please contact Product Support.

NOTICE: OutSystems does not give support to any undesirable behavior you may experience due to the use or manipulation of undocumented components of the OutSystems Platform, such as, internal JavaScript, RuntimePlatform library, database system meta-model, components in installation directories, etc.

[Ideas] BPT: Rollback\Undo Activities

$
0
0
In Service Center Process Management we could have the ability to undo / rollback the activities, one by one or directly to some point in the process.

This would be very usefull in situations where something went wrong and we need to fix the process execution and run it again from start of just from some specific point.
Instead of deleting activity records in the OutSystems database it would be much simpler and safer if it was managed by Service Center itself.

[Ideas] [Service Studio] Completely disable input where property "Enabled=false"

$
0
0
When Input.Enabled property has been set to false, a user can not interact with the input widget (he can not modify the value).

The input field is now disable however if the user use chrome he/she could change the input value by right clicking on the input field and select "Inspect Element", from here the user can change the input value.

To avoid this issue you have to overwrite the user input field within your action, it would be good if outsystems fixed this issue by overwriting any modified value where input.enabled=false.


[Ideas] Expose REST web service: Add versioning control

$
0
0
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.

[Downloads] OutSystems Platform 9 - Offline Documentation

$
0
0
There are situations in which OutSystems developers may not have access to the Web, therefore, may not be able to reach online documentation. To overcome these offline situations, OutSystems produces and makes available here a package containing all documentation in Windows Help format.
You should take into consideration the following differences to the online documentation: - Contextual help does not work with offline documentation. This means F1 key and other help buttons will always try to open the online documentation. You will have to open the offline documentation and manually search for information; - Some help content resorts to online resources (like videos and code snippets), and while in offline mode you won't have access to it; - To get new versions of the offline documentation, you must download it from here.

Disclaimer: OutSystems reserves the right of changing the format and the delivery of this documentation without previous notice.

[Ideas] Delete reminders directly from TrueChange tab

$
0
0
It should be possible to delete reminders directly from the context menu or the delete keyboard key in the TrueChange tab of Service Studio.
Viewing all 1476385 articles
Browse latest View live


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