From Apps to Enterprise Mobility: Crossing the Chasm
CIOs around the world are under pressure from their user base to extend support for mobility. Their users are familiar with ‘Apps’ that people build and release at the drop of a hat. This leads to an expectation that the Enterprise Apps that they want should also have the same turnaround time.
However, this is far from reality…
Before embarking on an Enterprise Mobility strategy, it is important to understand the difference between an App and Enterprise Mobility and what it takes to cross that chasm.
Let’s understand what an App is – It is typically a mechanism to collect inputs from users and either share it with other users/systems or use that information to push out content to the user. Primarily it provides a mechanism to view data and communicate. Enterprise mobility, however, covers a larger scope. While an App is an integral part of Enterprise Mobility, there are many other components to it. These include the following:
Connectivity, Data Extraction, and Processing: An enterprise will have hundreds of business applications. When it comes to connecting to and rendering these over a mobile device, one of the first requirements is that of integrating with these varied systems. The purpose of integrating is to collect and send data from the front-end mobile app to these varied systems. This is a big pain point for the CIO’s IT teams since there is no defined protocol/methodology to achieve this. And this contributes to delays in these projects.
Security: Enterprise Applications need to mirror the security standards that are defined at the organizational level. All aspects of authentication, authorization and access control need to be adhered to.
User Experience: While user experience might not be a big driver in adoption when it comes to Enterprise Apps, the need or focus on it cannot be discounted. It is important that the Apps that are built need to match if not exceed the user experience that the typical enterprise user is accustomed to.
Understanding these differences is the key to success here. A CIO can then educate his/her business teams on the complexity involved. This realization will help them lead their organization to cross the chasm from Apps to Enterprise Mobility.
Fetching Data From One Iflow Via Process Direct And Invoking A Loop Process Call With Exception Handling
This is my first blog Post where I have been tried to describe a real time scenario of CPI where we have to call the iflow followed by another iflow and spilt the data and fetch it with looping process call.
This is my first blog post and I will be guiding you on how we can build a connection and interchange messages between Company and our Trading Partners using Trading Partner Management capability which is recently added in SAP Integration suite.