After delivering 4.0.3 Michael and I had some conversations about adding more features and a complete re-design of the BRMS web interface. Basically we are looking at how to break things up into "perspectives" kind of like eclipse has (but simpler), just to make it easier to present the user with the information they need for their current work example:
- BA type users (no package configuration, follow templates, read only sometimes etc)
- Developers (configure stuff - eventually should only need eclipse so this doesn't have to be too strong on the web side)
- Admins/operator types (migrate, security setup etc).
Nothing that complex, but we do need to have it scale up and down to these skill levels.
I think we can do something like merging the previous BRMS organization with the new tree feature. We do like the tree/explorer motif, fairly familiar to most people and easy to make it filterable based on both server side and user settings. Also, its more like ideas that the jboss web console is moving to.
The new package feature
Also with this refactory we will enable I18n internationalization then people can easily edit the bundle file/config to add they own language setting. Other key features like rule based authorization and custom queries are also some of the new features.
We are messing around with a few designs and also very receptive on ideas and feature requests you can find our task list on Jira and suggest something, also you can ping the dev mailing list on firstname.lastname@example.org
The new BRMS design concept