Learn how to set up the Corti desktop app on desktop and workstations
Table of Contents
Installation Instructions
⚠️ To download and install an application within an EMS local network, you might need specific admin rights - which are proper to your organization's IT system.
In order to install the Corti desktop app on a desktop or workstation, the first thing you will need is the installer link for the application (and the version) you want to install.
The installer link will be provided by Corti, usually via an Amazon S3 service link, and it will come as a Microsoft Installer (.MSI) file.
Once downloaded, launch the MSI file.
⚠️ Be aware that:
- Most likely, the device will prompt the request to allow the Corti app to make changes to the user device.
- If a previous version of the Corti app is already running in the background, the device will also ask for permission to close the Corti app, if opened, before proceeding.
The installation will then proceed and reach the completion without further inputs required.
💡Given that the file has the .MSI format, it is possible to install it wherever preferred.
The following command will install it in the Program Files directory:
msiexec /i Corti+5.0.2.msi APPLICATIONFOLDER="C:\\Program Files\\Corti" /q
Configuration File
A configuration file can be used by your system administrator to configure the parameters and initial settings of the Corti application for all the designed workstations:
- It can be used to configure the most common API, Window viewer and Login options.
- It can also be used to configure more integration-specific options, depending on the need of your organization.
You can find an example of a configuration file here
💡 By design, the user-settings config file is saved on the user directory, not the workstation directory.
⚠️ Please ensure to have enabled roaming profiles on Active Directory and that each user has the user-settings.json correctly stored.
Interface Screen Settings
In adjusting/setting the size of the app's window to your screen, bear in mind that the width and height of the app will affect how you see and experience the app.
This is particularly relevant when using the following:
Triage
Our current Triage interface:
- starts to struggle below 900px width, but it will still display both the timeline and the protocols on the left.
- will switch to a slimline mode below 600px width, where only the timeline is displayed.
The upcoming updated interface will be fully responsive, and ultimately scaling down to phone size if necessary at approximately 400px width.
In both cases, when using Real-time, more vertical space equals more content without scrolling, but are still fully functional at 550px height.
Protocol Editor
Our current Protocol Editor interface:
- starts to struggle below 900px width, but it will still display both the protocols and the actions list on the left.
- is comfortable at 1500px width and above.
Regarding the height, nagivating the Protocol Editor is typically comfortable with a display at 800px or above.
Explore
The Explore interface usually benefits from more space.
- At least 1024px width to be functional, especially when in timeline/ review more.
- Comfortable at 1500px width and above.
Regarding the height, navigating Explore is typically comfortable with a display at 800px or above.