Recommended client configuration
Who is this article for?
Administrators and Users who want to learn about configuration
No elevated permissions are required.
The subsequent sections will provide a detailed explanation of the configurations required to ensure an optimal experience when utilizing either the desktop browser user interface or the mobile application. It is essential to understand these configurations as they play a crucial role in enhancing the overall functionality and user satisfaction.
Desktop UI
General hardware recommendations
| Item | Minimum Recommended | Notes |
|---|---|---|
| Operating System | No restrictions | Must be able to run a supported browser |
| Processor | PassMark score of one thousand or better (e.g., Intel Pentium D 3.60GHz) | |
| Memory | 2GB or more | Also depends on the installed OS and number of applications running simultaneously |
| Network Speed | 1+ Mbps full duplex throughput | Requires an always-on network connection; the Desktop UI does not support offline |
| Display Resolution | XGA (1024x768) minimum; SXGA (1280x1024) or better recommended | Complex screens, such as those used by administrators, may require greater resolution |
Supported browsers
For security and performance reasons, Ideagen recommends using the latest browser version supported by the browser vendor on operating systems. The Ideagen security policy is to always apply browser patches when they are released, and the quality assurance process requires that testing be completed using the latest browser versions.
Ideagen supports the latest version of the following browsers. Ideagen will fix defects encountered with non-current browser versions released within the last six months, assuming upgrading to a newer browser version is not an option.
- Edge
- Chrome
- Firefox
- Internet Explorer (see note below)
- Safari for macOS
If the preferred browser is not in the above list or is in the list but not released within the last six months, be aware that while it may work. The user may experience degraded performance or usability issues.
General browser notes
- Cookies: Enabled. We do not track any personally identifiable information using cookies, but we need them to help maintain the session state. Users will receive an error if they log on without cookies enabled.
- Zooming in/out: Zooming in or out on a browser can cause layout issues in certain cases. If this happens, we recommend that users change the resolution on their screen instead of using the browser zoom functionality. In general, zooming with the browser zoom functions works well.
-
Plug-ins: Plug-ins can sometimes interfere with JavaScript processing, so we recommend using a browser with few or no plug-ins if possible.
- If users experience issues, such as memory growth or slow client-side response times, typically it's a plug-in that's to blame.
- This can easily be verified by running the browser choice in no-plugin or "safe" mode.
-
Error message related to scripts running slowly or being unresponsive are an indication that one or more of the following solutions may be needed:
- A faster CPU or more memory
- A more modern browser (which has a more efficient JavaScript engine)
- An analysis of the machine to ensure that plugins or other programs aren't interfering with normal browser functioning
Internet Explorer required settings
- Internet Explorer cache setting: Check for newer versions of stored pages automatically.
- Internet Explorer compatibility mode: Disabled.
-
Internet Explorer security level: Medium. (This only applies to a subset of customers with implementations before 2014). Avoids issues such as unnecessary user prompts, slower browser response, and unpredictable behavior.
- Add devonway.com and ideagen.com to the Trusted Sites list.
- Alternately, enable the "Automatic prompting for file downloads" and "File download" options.
Mobile application
A Mobile application is available for iOS, Android, and Microsoft Windows. It is tested on current iPhone and iPad models Samsung and Google Pixel devices. Mobile applications serve as an extension of an existing environment and are specifically designed for the collection of information. It cannot function independently from the desktop environment, as the data collected through the mobile application needs to be directed to a central location for effective reporting and workflow management.
Application performance may vary depending on device and module configuration options, so devices should be tested under real user scenarios.
Device differences and other considerations
Stay informed
Not all functionalities may be available on all device types, form factors, operating systems, and/or deployment models. Please refer to this section for exceptions or warnings and release notes for updates.
- Due to the larger screen sizes required for a usable experience, Mobile Work Packages may not be available on non-tablet devices. (Watch release updates and discuss options with your Technical Account Manager)
- The Camera option is not available on an Android device from a Work Package media link. Instead, users are directed to select a pre-existing image from a file. The camera option works as expected on iOS and Windows 10.
- Ideagen only guarantees that minor (patch) updates will work with data from the most recent release. This consideration typically only applies to customers who manage the distribution of the app through a means other than the app stores, e.g., through a custom release cycle to Windows devices. Ideagen encourages all customers to keep up to date with releases to avoid data loss or work with us to develop a tailored distribution mechanism to avoid any data loss.
-
The recommendation is to assign iOS and Android devices to an individual user since that is what those operating systems’ security models were designed to assume. Unlike Windows or Mac OS, Android and iOS are designed to be single-user operating systems; among other things, they don’t have the concept of a separate file system area for each user. Different Ideagen users can log on to the mobile app from a shared device; however, there are important security implications to think about:
- If User A does not explicitly log off from the app before User B uses the shared device, then User B will be taken to User A’s mobile session when they open the app, assuming User A’s OAuth token is still valid
- Since both users are using a shared device, the users could use a file system explorer tool to view each other’s data
Other helpful tips
Additional documentation may also help you understand writing requirements and how to prepare for the deployment of a project.