While the purchase system grows in the ERP module, Financials documents are stressed to its maximum. I stop by to clear my mind and, amid words, better understand the whole.

The way resource and product movements get reflected on the enterprise accounting system, is quite special in the BrightSide Financials way. Stores are attached to departments and services through contracts. Information about cost centers and business lines, go down the line, to Financials registry. Even more, a relation is saved along using the RelatedPaths API. The next Financials release will feature having lines locked by external sources, in this case: the purchasing system.

ZK is a Java Framework for building web applications, with over 1,500,000 downloads worldwide. BrightSide uses ZK as primary user front-end.

We are proud to announce that now, BrightSide is a Case Study on ZK web site.

Everything started as a Resource Planning feature. Human resources could be operators from external providers, owning aptitudes as normal human resources do. Financials came in help providing contract interventions and yes, you guess it, one of them was the operator intervention. But, why stop it there? As if in a feverish interventionism, we added titulars, usufructuaries, legal representatives and others. So, did we stop then? No!

The Turro.Org Foundation is taking place in the near future, you can read about it in Organization -> Foundation. The organization solely might not be attractive for business opportunities: free software and basic documentation will be made available for system administrators and for developers, see Documents -> Javadoc -> Full report as example.

But things change if you stop selling software and, instead, bring support and services. Then Turro.Org Foundation will be clearly a good choice. Here are some pros:

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.