Switching Devices
Introduction
This page will describe the 'Switching to Mobile' and 'Switching to Desktop' activities that allow users to control the device the ID&V flow and redirect the user to a URL of choice once the process is finished.
Switching to Mobile
The Switching to Mobile activity is typically found at the beginning of the customer's ID&V journey. When the customer begins their journey on a desktop browser, this activity will prompt them to scan a QR code on their mobile device so that the ID&V flow will continue from their mobile device. For more information on this Switching to Mobile activity and its parameters, see the Activity Parameters guide.
After scanning the QR code, the customer will be redirected to their mobile device
In cases where the customer begins their journey on a mobile device, this activity will be skipped and the customer will not be required to scan the QR code to redirect their device.
While the customer is completing the flow from their mobile device, a screen on their browser will appear that encourages the user not to close the web page. This is to ensure a smooth redirect once the process is complete.
Switching to Desktop
The Switching to Desktop activity typically occurs at the end of an ID&V flow. There are no requirements from the customer to scan a QR code. Instead, they will be redirected to their desktop browser once this activity is reached. For more information on this activity and its parameters, see the Activity Parameter guide.
The customer will see a message from their web browser that will confirm that ID&V flow has been completed successfully.
If is often necessary to switch a user back to the device from which they started the process so that the user can be redirected to the correct location on the correct device.
E.g. if an end user started their ID&V journey on a desktop device then then should be returned to the desktop device so that they can be redirected on the desktop device.
Redirection
Redirection of an end user happens at the end of the ID&V flow. The user is redirect based on a 'well known' parameter for the Process Token - _redirectUrl . By specifying a _redirectUrl parameter when creating a Process Token the end user will be redirect to the URL specified.
For more information see the Integration Guide.