Something that is very cool about WBM are the things called "Business Items".
The Business Items are nothing more of the inputs and outputs that get generated in a process. Is the thing that gets created, modified or destroyed in the process (ok, remember that in nature nothing gets created or destroy, just transformed)
Here it is how a Business Item looks in a process:
But the business item, in this "Application" has a lot of stuff inside it.
Just looks the attributes you can add to it, you can even put a "Business Item" inside other "Business item"
Or the documentation stuff, text, files and links.
And you can even document if the "Business Item" has stated... Approved, Draft, etc.
And we can tell the process which activity make the business item's state to change. Here is how it looks like.
After seeing the news of Google TV going to Android version 4.2.2, I thought:
"This could be good news, it can be a good thing for the custom ROM community."
Since moving the GTV platform from the close source Android 3 to the open one 4.2.2 can represent more access to the source code and more possibilities to custom development.
But I was complete wrong, there is one limitation for custom ROMs on the Google TV platform. The device manufactures has "Locked BootLoaders" on the Google TV devices. That's why it can not be possible to install custom ROMs.
I found this unfair, specially for Google TV devices that are no longer supported by it's manufacturers. The fair thing will be is that manufacturers release the keys of the bootloaders for the consumers to do whatever they want with the device they pay for.
The manufacturers can rely on every contract term to say if you screw the device it is not my fault, but they have to unlock the bootloaders.
This is why everybody asks for a "Nexus Google TV"