Yesterday saw the release of Omada’s brand new component for business process management within Microsoft FIM 2010 platform. See the official link press release here.
For my view on the current Microsoft / Omada / BHold discussion see the following posts:
- Microsoft and BHold (initial thoughts)
- Microsoft Identity Management, BHold and Omada
The exciting news for this post however is the brand new workflow builder aptly called Omada Workflow Builder for FIM 2010. Something that has impressed me a lot of the last few releases from Omada is the level of integration they seek with the seamless adding of their modules into the FIM 2010 portal. This has always been one my biggest comments/complaints to all the ISV vendors of FIM components. The last few releases have started to address this concern of mine – and the new workflow builder looks right on the money.
Subsequent to the announcement I had the privilege to get an inside look at some of the new features and they seem straight forward (at least from the surface – I have not been able to play with these myself). Again the obvious plus point was the integration into the FIM 2010 portal. Until I have developed business processes in this tool I will reserve comment – but I have included some very nice looking screenshots.
This component again show Omada’s commitment to developing solutions on top of the FIM 2010 platform. In my view this makes the platform more will rounded and sends a clear message of intent to customers and Microsoft that Omada is not going anywhere.
Portal front page view of business process initiation: The new workflow builder integrates seamlessly on the FIM 2010 front-end as with all the current Omada modules for FIM 2010.
Requesting access to resources: The further enhancement is the seamless integration of the workflow process windows into the FIM 2010 portal through FIM 2010 RCDC’s. Below is screenshots of a resource request process being initiated as well as an approver taking action on the request.
Approval task example
Just how flexible and simple the development of these new workflow tasks are – that remains to be seem. I hope to get a view on that soon. Something I further liked about the solution is that the standard process workflow instances are exposed in standard reports under the existing Omada Compliance Center for FIM 2010 for reporting purposes.
