Elephant was providing a Log System, widely used by the whole set of modules. The Log System had also a view where we could see what was going on on our web site. Who entered the system, how many times a file was downloaded, which document was saved or deleted and so on and on. Quite useful, really, because we could follow up the moment something was created, modified or deleted. And who did the action. Yes, and then what? You might think... you go and ask the one who did it what was the deleted content?

We knew what happened but, if this was the case, could scarcely do something to repear it.

Elephant has a complex page construction, element composed and factory driven. Thus, Elephant has powerful configuration grounds and might walk soundly step by step.

To understand what goes on when rendering the HTML, we first need to understand what a page is. One page, one context. One context, multiple layout and content elements. Real world, though, shows that most of times, pages are composed by layout elements spanning site-wide and a single content element. Real life is complex, but follows phisics laws.

Since I started writing code for the enterprise, products where the stars on Moneyland sky. Everything is a product: services, merchandise, manufactures... everything is worth buying or using. Thus, you have something, you give it a code and the magic starts: you have a product. No matter if its free or costs money.

Treasury module its first quarter was kind of disappointing. Didn't really carry modifications, didn't accept anexing and previous exercise was a nightmare. BrightSide Financials version 1.3 includes new features and fixes all those bugs. 

New BrightSide Financials 1.3 will come with some improvements in document relations. Documents follow a relation plan, described in contract models, especifically in model's workflows. Financials shows the full set of relations a document has and allows relating with a single click.