Skip to Content (Press Enter)
Back to Ideas
21
Like
Follow Idea
2015-12-02 13-57-16
Jeffrey Pogoy
Application Object In-Depth Details or Breakdown
1380Views
9Comments
Not right now
Licensing

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.

03 Dec 2015
Copy link to comment
2018-04-06 14-15-37
Pedro Martinho
Changed the status to
Not right now

Hi Jeffrey,

Thanks for you comment, estimating Application Objects is something that becomes easier with experience and additionally the reuse of application objects is a main factor to take into account when sizing a new app or feature.

One of the big plus points of OutSystems is the application object reuse. This means that if we structure our portfolio correctly application objects can be reused across apps. This means that we should look at the number of objects over the portfolio and not necessarily on an app by app level.

For example: if we have an entity, let's say a product table that is used both by a catalog app and a contract management system, that entity would only count once, not one time per app or system.

As we build more with OutSystems, and assuming we apply best practices in terms of reuse, the more we build the "cheaper" it becomes to build new apps and features because we can leverage exiting components from other apps.

Cheers,

Pedro


08 Jun 2018
Copy link to comment
Merged this idea with 'List the Application Objects (AOs) consumed per Application.' (created on 29 Apr 2021 14:28:28 by Goncalo Duarte Almeida)
14 Aug 2025
Copy link to comment

Right now we only can see the application objects consumed per espace, and

It would be nice to have the ability to see per application as well.


For those who don't have unlimited AOs, this info allows us to manage better our applications by AO with more accuracy.

29 Apr 2021
Copy link to comment
Merged this idea with 'Application object Count For each application' (created on 14 Jan 2024 12:45:44 by GOKULPRASANTH M)
15 Jan 2024
Copy link to comment

Application object count for each application will show means it will be helpful. Attached the example .

14 Jan 2024
Copy link to comment

This is recently become available in ODC Portal. For OutSystems 11 not yet implemented.

28 Sep 2024
Copy link to comment
Merged this idea with 'Built-in AO (Application Object) Usage Tracking in Service Studio and LifeTime' (created on 28 May 2025 05:26:28 by Divyaarthi Sivaraj)
14 Aug 2025
Copy link to comment

It would be extremely helpful to have a built-in feature that allows developers to calculate and track AO (Application Object) usage directly within Service Studio and LifeTime. Currently, estimating AO consumption often requires manual effort or third-party tools, which can lead to inefficiencies and inaccuracies.

By integrating AO usage insights at the module, component, and widget levels, developers and architects could better manage licensing impacts and optimize applications early in the development process. This visibility would also support better planning, governance, and cost control, especially in large enterprise environments.

Benefits:

  • Improved transparency of AO consumption

  • Faster, more informed architectural decisions

  • Reduced risk of exceeding AO limits unexpectedly

  • Encourages more efficient application design

28 May 2025
Copy link to comment

This could yield valuable insights. !

29 May 2025
Copy link to comment