1
 Follower
14
 Likes

Exclude recommended applications from AO count

Licensing
Implemented
on 01 Dec 2017

Hi there. 

In order to respect the architecture principles defined by OutSystems, it is recommended that developers install the Discovery application. The application is extremely useful and very necessary, but is only used to validate the architecture and it has about 50 application objects... 

I believe that applications such as this should should not be considered in the Application Objects count, for licensing purposes.

Best regards,

Maria

Created on 13 Nov 2017
Comments (14)
13 Nov 2017

Completely agree with you Maria, specially for small projects where you have limited AOs.

13 Nov 2017

Why should you have discovery on production server anyways?


14 Nov 2017

I agree with J. One shouldn't have the discovery application in the production, or test environment even.

17 Nov 2017

I don't have it installed on the production environment, I am talking about projects with limited application objects on the development environment.

17 Nov 2017

Agreed. The main tools that are "mandatory" to keep the minimal quality of an application and recommended by Outsystems, could be provided by "free". Or be part of the Outsystems platform.

17 Nov 2017

I maintain that certain tools/apps should not be deployed to test or production environments, but I will concede on one point and agree that referenced system entities should not be included in the AO count of an application.

24 Nov 2017

Hanno,

The applications are not deployed to test or prd. I am talking about development environments with limited AO objects, such as 200, where the 50 AOs from Discovery, for example, make a huge difference.

24 Nov 2017

Okay in that scenario I agree. I was not aware that you have a limited AO development environment.

6 Apr (2 weeks ago)
Changed the status to
Implemented
on 01 Dec 2017


Hi Maria,

Thank you for your input!

We're glad that you see value in our Discovery application!

The Discovery application is not meant for the production environment and the only current edition with a capacity limit in development is the One edition. 

The One edition is meant to build one or two apps and is limited to 200 AOs. The development environment is limited to the same 200 AOs as it would be impossible to move to production more than that without upgrading to an Enterprise edition (the One edition does not scale in capacity). 

However in order to solve the issue you reported we have added 200 AOs as grace to the development environment. Effectively the environment is limited to 400 AOs and our clients get a warning when they're close to the 200 AO limit in development as well.

I'm marking your idea as implemented as I believe the current configuration solves the issue, do let me know if that is not the case.

Thanks!

6 Apr (2 weeks ago)

Hi Pedro,

Thank you for your answer and for bringing some good news :)

When will the change from 200 to 400 AOs take place?

Thanks!

16 Apr (7 days ago)

Is any SUs ugrade planned for dev environment?

17 Apr (6 days ago)
Merged this idea with 'Do not count Discovery SUs' (created on 2018-04-13 23:00:29 by André Alho)
13 Apr (10 days ago)

This is a fundamental component to work with Outsystems.


It shouldn't cost you 25k SUs.




Merged from 'Do not count Discovery SUs' (idea created on 2018-04-13 23:00:29 by André Alho), on 2018-04-17 08:06:35 by Vasco Pessanha
16 Apr (7 days ago)

see: Exclude recommended applications from AO count



Merged from 'Do not count Discovery SUs' (idea created on 2018-04-13 23:00:29 by André Alho), on 2018-04-17 08:06:35 by Vasco Pessanha
views
229
Followers
1