Extensiv Hub

How the transition to Extensiv Hub affects SmartScan
Do I need to access SmartScan through the Extensiv Hub interface?
No. Hub is not built for use on the specialized barcode scanning devices used by most of our customers, which typically have limited memory, processing power, and screen real estate. Because of this, SmartScan is not integrated into the Extensiv Hub, but SmartScan will take advantage of Hub’s state-of-the art authentication infrastructure. This means SmartScan will require a Hub-verified user account for login.
How do using a Hub user account affect my ability to access SmartScan?
If your users have existing 3PL Warehouse Manager user accounts, make sure you have completed the process of specifying a valid email address for each of those accounts. The email address is the primary user ID going forward.
This process of migrating an existing account to Hub includes receiving an invitation from Extensiv with a temporary password that adheres to the minimum requirements for password security. Users must login to their new Hub account and change their password prior to using the account to login to SmartScan.
Should I have my users create a new Hub account?
Once Hub is fully enabled, your users must have a valid Hub account to access SmartScan. You can migrate legacy user accounts to Hub, which ensures that historical user activity remains available for that user going forward. This is important for any 3PLs currently using the Extensiv Business Intelligence (BI) dashboards, such as the Outbound Labor Analytics Dashboard. The BI system uses event data from SmartScan to generate dashboard data. If a user starts using a new account as part of the Hub transition, all historical data captured under to previous user account will be lost.
Will the SmartScan login process change once we transition to Extensiv Hub?
SmartScan will get a new login page as part of the Hub transition, but the login process is unchanged. One benefit of this is that the new login page now supports scanning both the User ID and Password values to log in. Previously, scanning was supported only for the Password.
This means that you can simplify the SmartScan log in process by creating barcodes that users can scan instead of manually typing their email address and Password. How much of this to take advantage is up to you and your organization’s level of security awareness.
Do I have to reconfigure my devices as part of the Hub transition?
No. SmartScan gets a new URL as part of the Hub transition (3w.extensiv.com), but our cloud infrastructure will automatically redirect the current URL (secure-wms.com) for the time being. This gives you some flexibility to determine how and when to update your devices to use the new URL directly.
Consider the following to help you make this decision:
- If your devices use a standard web browser like Google Chrome, you can easily update your SmartScan shortcuts to reference the new URL. We recommend doing this as soon as it’s convenient for you.
- If your devices use Zebra Enterprise Browser, you must update the config.json file on the device to reference the new URL. This process is more involved, so we recommend migrating devices in batches over time.
Note: If your hardware partner provides a device management system, such as SOTI, they can quickly and easily update the config.json file for you.