At the companywhere I work, we currently use two eSpaces for each application. One is accessible from the Internet, and the other from the Intranet. Each eSpace contains all the modules of each application.

For reasons of organization and ease of maintenance, we are considering to change the eSpaces architecture, which raises some questions we would like to clarify.

There is any inconvenience in building an application along several eSpaces, where each module is implemented in a different eSpace, although from a common template? This is because some applications are really big, and this way, it should be easy to maintain, right?

Thanks in advance.
Hugo Laibaças
(Direção-geral do Orçamento)
Hi Hugo,

It is perfectly common, not to say advisable, to have your apps structured along multiple eSpaces. Namely, you may have an eSpace that is a common resource producer, containing your data model (Entities) and maybe a few actions and web blocks that are used to operate over those entities. You could then have several eSpaces that feed off that producer eSpace. We use that all the time in OutSystems projects and even our ready-made apps use that approach.

Another use is to have common visual styling in an eSpace: having the Theme (including general CSS), headers and footers all in one place.

Points to have in mind, to diminish solution compilation times etc is to try to minimize circular references as much as possible. Always try to have clear producers and consumers and make references unidirectional.

Hope this helps and good luck! :)

Hi Miguel,

Thanks for your answer. It was really helpful.


I have another question.

How can we «have common visual styling in an eSpace: having the Theme (including general CSS)»?
Having all the styling stuff in one place, would be a great advantage, but we don't know to acommplish that. We know that each eSpace can reference other eSpace's Actions, Entities, WebBlocks, etc., but we don't see how to reference the CSS of other eSpace.

Can you point us the way, please :-)

Hugo Laibaças
Hugo Laibaças wrote:
Can you point us the way, please :-)
Hi Hugo,

Yes, since 6.0 the Agile Platform has a theme inheritance/reference scheme similar to the "normal" references. :)

Have a look at the documentation at

especially the sub heading "Using Theme References" to get started.