Idea:
Implement a logic within the HCL Connections Desktop Plugin that detects when the server is in a designated "Maintenance State" (e.g. HTTP 503 or HTTP 540) and temporarily suppresses user-facing error pop-ups.
User Story:
From the Administration perspective, I want the Desktop Plugin to handle server downtime gracefully without alerting end-users, so that the helpdesk is not flooded with tickets and users are not interrupted during scheduled maintenance windows.
Use-Case & Problem Description: Currently, when the HCL Connections environment is taken offline for maintenance (e.g., users are redirected to a maintenance page), the Desktop Plugin attempts to sync "My Drive" and fails.
Current Behavior: The plugin displays the error: "HCL Connections - Sync failed for 'My Drive on <site_name>' because the server is currently unavailable." This pop-up recurs every few minutes for the duration of the maintenance window.
Pain Point: In an environment with thousands of users, this disrupts work and might cause confusion.
Business Impact:
User Experience: Repeated error pop-ups (every few minutes) are intrusive and erode user trust in the application's stability and quality.
Operational Efficiency: Allows IT teams to perform maintenance without needing to notify the entire user base to "ignore error messages," streamlining communication.
Possibility to Reduce Support Costs: Maintenance windows might trigger a spike in L1 support tickets because users might interpret the error pop-up as a personal technical issue rather than scheduled downtime.
Possible Solution: The "Maintenance Mode" logic should rely on standard HTTP response codes.
Trigger: If the Desktop Plugin receives an HTTP 503 Service Unavailable or similar, it should catch this specific exception.
Action: Instead of displaying a UI Error Alert, the plugin enters a "Silent/Standby Mode."
Recovery: The plugin should switch to a background polling mechanism (checking connection silently every X minutes) and automatically resume normal sync once the server returns HTTP 200 OK.