A few months ago, one of our customers asked if it would be possible for their OpenText- users to perform the steps in their workflow on their mobile devices. We answered that with a definite ‘Yes!’. We all know you can go mobile with OpenText, but they offer multiple mobile solutions. So, we deep dived into these different solutions and presented our customer a plan that suited their requirements perfectly. The biggest lesson we learned? There are many ways to go mobile with OpenText, however which road to take is completely dependent on the process and organization.
It seemed obvious that other customers are also playing with the idea of going mobile. Accessing your Content Server environment from a mobile device can have advantages for many customers. Therefore, we did not just focus on this use case, but we took a broader view on the different mobile solutions that OpenText must offer. We looked at a couple of use cases and explored the possibilities of each OpenText solution. We discussed what individual users (roles) would like to gain by accessing Content Server on their mobile device. Finally, we settled on the following use cases:
We examined other use cases as well but they did match our scope. While they may be important when working with Content Server from a desktop, they were not our focus when looking at mobile use of Content Server.
When we started our research most of our customers where still using CS10.5. With our use cases in hand, we looked at four different available solutions that OpenText offers for mobile. We like to share with you what we found:
Time waits for no one. We experienced this first hand after presenting our view on how to best handle workflow tasks via mobile devices to our customer, OpenText had been moving forward. The company announced Content Server Mobile. This application is the successor of ECM Everywhere, but uses CS16's SmartUI. SmartUI is built on the ActiveView platform, so Content Server Mobile has some advantages over ECM Everywhere in flexibility and adaptability for different needs. While we have not seen this application in action in real life, it looks very promising.
The lesson we learned from our research in going mobile with OpenText? If a customer asks you about using Content Server on a mobile device, there is not one clear-cut answer. For each customer, the most suitable mobile solution depends on their needs. Are they just looking to access documents from a mobile device? Or do they need to complete workflow tasks via mobile? Each OpenText solution comes with its own advantages and drawbacks.
So, if you are thinking about going mobile with OpenText we have these pointers for you. Make sure you have a general understanding of all OpenText solutions. Do you want to find out which solution fits your needs best? Contact us via the button below.