Custom Application: Savvion BPM Integration with Mobile Devices Series
Mobile Apps have been emerging as one of the most powerful drivers in the recent years. Any product offering which does not integrate with Smart phones is definitely on its way of facing serious resistance in market penetration. Savvion Business Manager from Progress seems to have overlooked the fact in recent years. What's surprising is that the version 3.0 of Savvion (Current Production release is 7.x) actually claimed to have an integration with Biz Mobile although I am not aware of a working version of the same. Organizations that have huge Savvion infrastructure are struggling to have an integration with Smart Phones and similar devices, Blackberry being one of the major phones being sought for.
This white paper intends to showcase some of the approaches in which Savvion Business Manager could be integrated with Mobile Devices with focus on Blackberry. Our overall approach assumes that Cellphone requirement pertains to task Approvals/Completions rather than Business Process Modeling etc.
Savvion Mobile Approaches: Custom Application
By far the most customizable and most costly approach, building a custom app might solve a number of problems. Savvion Business Manager comes with a Web Services based infrastructure which can be leveraged for almost all possible Savvion Back end interaction. A Mobile app could be created which could handle the following
- Provide Task Notifications using Blackberry PUSH technology
- Update Notifications and remove already completed tasks
- Get all available tasks for the user
- Get Task details
- Complete Tasks
- Launch Processes
- Get Process Metrics
- Create Process Dashboard for Senior Managers
An Always ON app provides way better capabilities than email based systems. App could be provided with dashboards, look ups, threshold and several other features which are very difficult with any other mechanism.
The drawbacks of this approach is that the Business Rules need to be created as part of the process/rules engine rather than application forms. Since the App would get raw data while making web services, any front end customizations will not be available. Cost of creating and maintain thick apps on mobile devices again poses a major issue.