3. Index
1 Define the strategy
2 What to be aware of?
3 Integration levels
4 Assessment Levels
5 3 layers in your mobile integration
6 Examples
4. First of all: Define the Strategy
Trend:
Bring Different
Think devices and
your environment
own Inside-out
s
device
Convert the problem Offer valuable services
Define the strategy
into an opportunity , independent from the
platform
5. What do we need to be aware of?
Functionalitie
Raona SharePoint
s
Approach
Effort Infrastructure
Mobility
SharePoint Devices
6. Integration Levels
OOTB OOTB interface Customized Device-specific
Advanced
Standard
Basic
Total
Interface with minor Interface app
Tree view enhancements Usability Device-
Navigation Customized Total oriented
No custom Navigation integration usability
Apps OOTB Apps with LOB apps Opens up your
market and
customer base
7. What level do I need?
User Experience
Basic
Standard
Advanced
Total
Functional Capabilities
8. 3 layers in your mobile strategy
Internal Services Service Exposure Devices
Web
Service
CRM
FireWall
Intranet
BI
VPN
Others…
11. What can you do with Raona WF
APP?
Configure the URL and
credentials to retrieve
the workflow from any
SharePoint list/site
Subscribe to the
workflow you are
interested in
12. What can you do with Raona WF
APP?
See your pending tasks
Approve or reject a
task, depending on the
actions available
Usuarios vienen con el tablet… yqueiren que funcionen las app’s.. (no va silverligth, componentes). Lo que es un problema, podemos convertirlo en una oportunidadPiensa de dentro hacia fuera… (por ejemplo ofrecer sap hacia fuera? -> no.. Pero si las tareas que se . generan… /// El CRM? O partes?)Traductor de entornos… no voy a ofrecer un citrix para meternos en SAP, via terminal server--- no aportamos valor -> adaptamos la navegación al tablet, hacer una app a medida… Cada dispositvio tiene un entorno y llevarse lo mismo de logica de negocio al dispositivo. Usarlo como capa de presentación… e iniciador de servicios. En caso de cambiar de dispositivo, solo cambiamos la capa de presentación.Error de una empresa -> movilizar el CRM. Lo hacemos en android 2.2 .. Si cambiamos de plataforma, que pasa?
The configuration data is stored in Azure and the subscriptions are created in Azure Service Bus.The Azure Worker Process queries the tasks’ list to retrieve the pending tasks for the subscribed workflow every n-minutes.The new tasks are published to the Azure Service Bus. If there is any task for the subscribed clients, the Azure Worker Process will notify the mobile clients using Microsoft Push Notification Service.The client can connect to the Service Bus and retrieve all the data for these tasks.Once the task is opened, it can be approved or rejected depending on the available actions.More than one device (W8, Windows Phone, Desktop Gadget, etc.) can be subscribed to the same workflow. The service bus then makes sure the messages are delivered and synchronised accordingly.