have the AO (application objects) number displayed for each of the forge applications.

If there is a AO limitation on the environment and you almost reach and you need to install component from forge you can encounter yourself in a situation when the error upon component installation just says that you've exceeded AOs limit and component can't be installed. It would be rather helpful to have information of how many AO is required to install component. 

Even if the AO count was shown when viewing the component on the forge that would be extremely useful. 

Agreed Ouen, perhaps a simple calculation of the increase/decrease in AO count that will be effected by the publish can be shown prior to doing the whole publish. Maybe it can be part of the validation?

It would be useful to know beforehand the amount of Application Objects a Forge component will consume once installed. For example when making calculation for new projects. Off course you can just install the component and look it up in Service Center, but it would be easier if this information is just available in the Forge right away.

I got this idea because i wanted to calculate the AO's it will cost to use Architect Dashboard for my client.

I want to know how much AO's the installation will eat up before i install a widget or component.

It would be nice that when I consider to use and install a Forge component that I can see upfront how many application objects it requires.

Highly doubt this will happen due to the licensing shift away from AOs. But... +1. ;)

J.Ja

I know, but still more than plenty of customers that have AOs limited in their license. And partner environment is limited too. Took me some time to figure out we need 101 OAs just to install dynamic case management in our partner environment. 

I agree with you Daniel, there is yet some customers with AOs

Daniel -

Yup, but OS doesn't invest in deadlined things as a habit. We're not going to see anything around Traditional Web, AOs, Editable Table, etc. even though many clients are still on these and will be for some time.

J.Ja

Indeed, this will be very useful. Many a time, I had to download the forge component on dev environment (environment with unlimited AOs) to see the count. After checking out I had sometimes difficulty deleting the component because it was having an extension as a dependency which was shared by another component.

Showing the AO count on the forge component page like dependencies will make it transparent and decisive factor for a few.

Swatantra

Hi all! Thanks for your comments. I have a question about this. That's good reasoning for consumers, but I would also like to understand: what's your producer perspective?