Static Entities should not be count Application Objects

By Fantato on 3 Jan (2 weeks ago)

Nowadays Static Entities count as AOs but in some cases this can exclude simple applications from the backlog of the company. Per example, recently we decide not to go with an site that it is only a simple form containing 2 screens and 1 table. Because this form uses 30 combo from 30 static entities.   It is overrated spent 33 AOs to implements only a single form. 

If is not possible to ignore static on AOs , but at least a different count to do it.

leonardo.fernandes4 Jan (2 weeks ago)

Please think about static entities as being enumerates. Enumerates are not just a dataset, they are a dataset that you can use to develop business logic for each element individually. If all records on a static entity are treated the same by your app, you don't need an enumerate.

You can check if a static entity is needed on your app by finding usages of its records. If no records are used, then you can easily replace it with a regular entity. Just export the contents to an excel file, and use the wizard to bootstrap the entity from that excel.

If you need 30 static entities, each one containing 3 records, that would be 90 different business rules for your simple form. That would not be a simple form at all. This suggests me that you don't need all of those static entities.

For example, if you have a Countries static entity, but not a single rule specific to a given country, then you don't need this static entity. However, if you do have a distinct rule (for example, selecting a country then changes how a phone number is validated), then you're better off keeping the static entity.