Gives you the ability to design the screens outside the software and connect them as a component with the BPM engineOn the improvement part, I think the documentation for the tool, the official documentation, is not as strong as in other tools. You have lot of community. That is good. But sometimes you need - when you are working on a big client or a critical process - to be certain about certain things. So I think that the documentation for the tool, from the company, could be a little stronger. Also, the size of the team within Latin America. The size of the team that, in each country, knows about BPM - because of the size of Red Hat in comparison with the size of IBM or Oracle - is very little. You have maybe three or four people in the company, in Red Hat Mexico, that know about BPM; and in Peru, maybe one, who also needs to know about five other tools. You have help there, but sometimes you don't need that kind of help. You need to sit down with someone and take a good amount of time and discuss a process to solve a problem. It's a consequence of the size. IBM and Oracle are monsters. They have, say, 100 more employees than Red Hat. That is the problem. But on the other side, the price is good. You could pay four times less, five times less, in an average implementation with Red Hat than with IBM. So there is a trade-off.
