FAQs

Executive level FAQs

Q1. What are the benefits of this upgrade?
A: The portal upgrade is built on an upgraded technology stack that provides improved stability, scalability, enhanced security, and improved reporting capabilities.

Q2. What is the timeline of this upgrade?
A: Checkpoint has carefully planned the upgrade schedule to minimize business disruption. Your designated Checkpoint contact will communicate the upgrade dates and assist with any questions throughout the upgrade process.

Q3. Would I get access to review readiness?
A: Yes. Sandbox (Pre-Production) users will have access to evaluate the upgraded portal during a designated period for testing and validation.

Q4. Will business functionality change?
A: No functional compromise is expected. Existing reports, workflows, business processes, and customer-specific customizations are expected to remain available in the upgraded portal.

Q5. Is a pilot deployment possible in production?
A: Yes. A pilot deployment can be performed in the Production environment for selected users. The required users belonging to a store can be moved to the upgraded portal, allowing validation of key business processes and providing confidence before all data from the legacy portal is moved to the upgraded portal.

Q6. What downtime should be planned during the upgrade?
A: Production cutover is expected to require approximately two hours while user settings, configurations, and related portal data are moved.

Q7. What is the rollback plan if issues are identified?
A: Rollback can restore users moved to the previous portal version within approximately 45 to 50 minutes if required. The legacy portal will remain available until upgrade validation is completed.

Q8. Who is responsible for validating business readiness?
A: Business users validate portal functionality, workflows, and reporting capabilities, while IT teams validate network connectivity, authentication, security, and integrations.

Q9. Will users require retraining after the upgrade?
A: No retraining is anticipated. The upgraded portal maintains a familiar user experience while introducing enhancements and usability improvements.

Q10. What are the primary risks during upgrade execution?
A: Key risks include incomplete URL allowlisting, MDM policy configuration gaps, SSO onboarding delays, certificate validation issues, and unsynchronized transactions during the cutover window.

End User FAQs

Q1. Do users need a new ItemOptix Mobile App?
A: Yes. Users must update to ItemOptix Mobile App version 2.2.1 or later before the portal upgrade.

Q2. Will my existing bookmark continue to work?
A: Existing bookmarks may continue to work while the current session remains active. However, users should update their bookmarks to the new portal URL after the upgrade.

Q3. Do I need to clear my browser cache?
A: Yes. Browser and mobile application cache should be cleared before validation and first login after the upgrade.

Q4. Can I continue working during the upgrade?
A: Users should avoid performing active transactions during the upgrade window and complete any pending work beforehand.

Q5. What should I test after the upgrade?
A: Users should validate login functionality, business-specific barcode and RFID use cases, mobile application workflows, portal functionality, and any associated integrations.

Q6. Will the login process change?
A: No login changes are expected unless otherwise communicated by your IT team.

Q7. What should I do if mobile printing does not work?
A: Ensure you are using a supported browser and that browser pop-ups are enabled.

IT Department FAQs

Q1. What are the V2 Portal URLs?
A: Checkpoint will provide the appropriate Production and Pre-Production portal URLs for your region. The domain remians same.While the portal URL may vary by region, the underlying domain remains unchanged.

Q2. Which API endpoints need to be allowlisted?
A: Required API endpoints and domains will be shared by Checkpoint during upgrade planning.

Q3. What SSO changes are required?
A: Register and configure the V2 portal in the identity system. Identity Provider (IdP) configurations, certificates, metadata, ACS URLs, and Entity IDs will need to be updated.

Q4. What network validation should be completed before go-live?
A: Validate DNS resolution, firewall rules, proxy settings, VPN settings, URL accessibility, and HTTPS connectivity.

Q5. What certificate checks are required?
A: Verify SSL certificate trust chains, certificate validity, and TLS compatibility.

Q6. What MDM updates may be required?
A: Update managed app configurations, Mobile Device Management (MDM) policies, VPN settings (if applicable), and URL allowlists.

Q7. Which browser settings are required?
A: Cookies and JavaScript must be enabled and browser pop-ups should be allowed.

Q8. What activities should be paused during cutover?
A: User synchronization jobs, configuration changes, active transactions and offline sync activities should be paused.

Q9. Which domains are commonly missed during allowlisting?
A: Supporting domains for fonts, maps, reporting, analytics, and monitoring services should be reviewed and allowlisted.