Scenario 3 - Customizations
Webview Integration
In this scenario you are an experienced integrator and you have deployed some customizations with UI extensions and macros. It’s called Workspace Designer and opens a webview with Workspace Designer url.
Problem
In this scenario you are an integrator and you have deployed a customization with a UI extension (button) and a macro. You installed a button on the home screen that opens a webview on the device with Workspace Designer web page, for that to work you also have installed a macro called LaunchWorkspaceDesigner.js. Your task here is to verify that the custom button added to the home screen does what it’s designed to do.
As an integrator you want to go to the room and test your customizations to be sure it works and is ready for customers to use.
By clicking this button on the home screen (you might need to swipe to the next page of home screen on the device to find it):
Before you start!
You will verify that the button Workspace Designer is not working.
Your goal is to verify that after clicking on the Workspace Designer button the user will reach the Workspace Designer webpage opening on the device as a webview.
Your task
In this scenario you want to start a Remote Access session and verify if your integration is working. You will see that it’s in fact not working exactly as expected. You just caught an error before reaching the end user! Well Done!
Since in this scenario you are an expert integrator you know exactly what to do to fix this issue. From the device's overview page you will need to go to the macros tab inside Control Hub, and activate the Launch Workspace Designer macro to get the correct behavior.
Here is the Macros page in Control Hub where you should ensure the LaunchWorkspaceDesigner.js macro is toggled on in Control Hub → Macros tab, then click Save:
Once you have done that you will be able to verify with a Remote Access that the custom button works as expected. You should click on it and verify that webview opens on the device to be sure your integration is working.
If you are familiar with the UI extensions and macro engine you can play with the code a bit and test the behavior with Remote Access.
You can also install macros from the public macro repository available here: https://roomos.cisco.com/macros. If you create a user in Local Device Controls you can install macros from the public repository (please check the disclaimer section before using any macro from the public repository on you deployed devices).
Let’s move over to Scenario 4 - Call.