User Interfaces in #BPM – #bpmCamp 2010 @ Stanford session
- When should one deviate from the “stock UI builder” included in a BPMS? Teamworks ships with a great out of the box prototyping UI builder. It let’s you build simple interfaces extremely quickly (integrated with process data), but has some limitations when it comes to more customized look-and-feel. But when is a departure from the standard UI worth it?
- Once one decides to roll a custom interface, which frameworks have the most currency? There were people present that had worked with ExtJS and Flex, or just used Ajax to customize the Teamworks user interfaces.
- Why can’t access to process work be more universal? There was a lot of discussion about the process portal, but why aren’t tasks and updates available via twitter, RSS, SMS, SalesForce, and email among other things?
- There was general consensus that the reporting framework should be more “open” out of the box- providing useful data for charting in a simple XML format, along with optional detailed information in an XML format, in order to make it easier to support alternate visualizations. This approach would make it much easier to plug in different charting tools. (Note: to that end, bp3 has built a reporting framework that supports Google Visualization (and soon Fusion charts).
- There was a lot of interest in using the newer REST api’s for Teamworks.