Maintenance Mode

Third-party gadget developers can register with client services to receive notifications (FINESSE_MAINTENANCE_MODE_EVENT) when maintenance mode is scheduled. These notifications are triggered 15 seconds before the desktop reload. The DesktopCache API can be used to save and restore the gadget state after reloading to the alternate node of the Cisco Finesse server.

If a third-party gadget is logged in to a voice/non-voice Media Routing Domain (MRD), the gadget must send a NOT_READY message with reason code: 50045 to the Finesse server after a successful migration during maintenance mode. This message does not change the agent state.