2.5 Ability to integrate with MS Office. Please describe capabilities. 2.6 Describe the processes/methods available for interfacing with other applications (such as APIs, web services, etc.). 2.7 Must be compatible with all industry standard web browsers including, but not limited to, Internet Explorer, Chrome, Firefox, Safari, etc. Detail compatible browser versions in response. Please detail all user and public side device, browser and operating system requirements and limitations. 2.8 Application is capable of running on a separate server from the database. 2.9 Supports Windows Active Directory (AD) authentication. 2.10 Explain method for authenticating external users (not AD users). 2.11 Describe what is installed and/or stored on the client desktop (e.g. cookies, plug-ins, preferences, etc.). 2.12 User preferences should be on the server, not on the desktop. 2.13 Describe what information can be viewed by the system administrator for active users. Detail any tools available for use by the system administrator to manage active user sessions. 2.14 System is capable of automatic session timeouts. Describe options for configuring session timeouts. 2.15 If concurrent licensing model is used, allows a configurable timeout period for users not active in the system, ensuring that licenses are freed up when not being used. 2.16 Detail all software, tools, add-ons, etc. which must be installed on a workstation to access any portion of your solution. 2.17 Maintain user-defined configuration and data field definitions when upgrading
2.5 Ability to integrate with MS Office. Please describe capabilities. 2.6 Describe the processes/methods available for interfacing with other applications (such as APIs, web services, etc.). 2.7 Must be compatible with all industry standard web browsers including, but not limited to, Internet Explorer, Chrome, Firefox, Safari, etc. Detail compatible browser versions in response. Please detail all user and public side device, browser and operating system requirements and limitations. 2.8 Application is capable of running on a separate server from the database. 2.9 Supports Windows Active Directory (AD) authentication. 2.10 Explain method for authenticating external users (not AD users). 2.11 Describe what is installed and/or stored on the client desktop (e.g. cookies, plug-ins, preferences, etc.). 2.12 User preferences should be on the server, not on the desktop. 2.13 Describe what information can be viewed by the system administrator for active users. Detail any tools available for use by the system administrator to manage active user sessions. 2.14 System is capable of automatic session timeouts. Describe options for configuring session timeouts. 2.15 If concurrent licensing model is used, allows a configurable timeout period for users not active in the system, ensuring that licenses are freed up when not being used. 2.16 Detail all software, tools, add-ons, etc. which must be installed on a workstation to access any portion of your solution. 2.17 Maintain user-defined configuration and data field definitions when upgrading