For the most comparable experience to the Applied Epic desktop interface, install the Applied Epic Connection Suite, which includes the Epic Extension and the Epic Connection Suite Package. While basic functionality is available without these components, they are required for full Applied Epic capabilities in the browser interface. You can only install the Connection Suite components on machines with Microsoft Windows operating systems.
Your organization can choose to allow users to install the Connection Suite themselves, or your system administrator can install the components en masse on all applicable workstations. This document provides installation instructions for both workflows. Once the Applied Epic Connection Suite Package is installed and Applied has enabled auto-update functionality for your organization, the package automatically updates each time a user signs into Applied Epic. This document provides installation instructions for both workflows. The Single-User Installation section provides standalone installation instructions for users installing the Epic Extension and Epic Connection Suite Package themselves. The Mass Installation section provides information for system administrators installing these components across multiple workstations at once. We recommend that only users with experience editing registry entries and creating and distributing script files to multiple workstations perform the mass installation steps.
The Epic Outlook Add-in is required for email functionality in the browser interface. You must also select Outlook as the Email Integration Default in Configure > Email > System Settings (if you manage this setting system-wide), or direct users to select Outlook as their default in Configure > User Options > Email (if you allow them to select their own default).
If the Applied Epic Desktop Client is installed on the same workstation where you access Applied Epic from your browser, the Epic Outlook Add-in is already installed. Installing the Epic Connection Suite Package also installs the add-in or updates your existing installation. Applied recommends closing Microsoft Outlook before installing the package to prevent errors during email workflows.
If you want to allow individual users to install the Epic Extension and the Epic Connection Suite Package from Help > Connection Suite, they must have the Connection Suite security permission granted. Ensure that they also have the necessary permissions to install software and browser extensions on their local machines.
Use the instructions below to install the Epic Extension and the Epic Connection Suite Package on a single workstation. The Epic Extension is available for Google Chrome, Mozilla Firefox, and Microsoft Edge. You must install the Epic Extension separately for each web browser that you use to access Applied Epic. Install the Epic Extension before downloading and installing the Epic Connection Suite Package.
System administrators can perform mass installations of the Epic Extension and the Epic Connection Suite Package. If a user accesses Applied Epic from multiple browsers, you must install the Applied Epic Extension separately for each one. Install the Epic Extension before installing the Epic Connection Suite Package.
You can install the Applied Epic Extension to workstations using Google Chrome in either of two ways. If you have a Google Admin account, you can use the Google Admin console. If not, you must edit each workstation’s registry.
If your organization uses Google Workspace, you must use a Google administrator account to access the Google Admin console and manage Google services or devices for a group. To learn more about managing Chrome policies from the Google Admin console, see Automatically install apps and extensions in the Google Chrome Help Center.
You must allow all of the Applied Epic Extension permissions for the extension to function; no permissions can be blocked. To learn more about the permission options, see Set app and extension policies in the Google Chrome Help Center.
If your organization does not use a Google administrator account, system administrators can distribute and install the Applied Epic Extension to Google Chrome on user workstations by editing the workstations’ registries.
These instructions assume that you are already familiar with the process of creating a script file to edit the registry and distributing the file across multiple workstations. Using your preferred methods for creating and distributing the file, you must edit the parent registry key containing the Applied Epic Extension to force the installation of the extension in Google Chrome. These instructions identify the parent registry key and the format for editing it.
If you install the Applied Epic Extension using registry entries, users cannot remove or disable the extension without removing the registry key. After you have pushed out the registry changes to users, the extension will be installed the next time each user opens Google Chrome, but it may take a moment to complete.
The <n> is an incrementing numeric value representing the extension, with a value of the form <store id>;<update url>. To force the installation of the Applied Epic Extension, add the store ID for the Applied Epic Extension and the specific URL for Google Chrome:
<store id>: jmigehagkgopllnhcjngjgfblmjladih
<update url>: https://clients2.google.com/service/update2/crx
The finished code to force the installation of the Applied Epic Extension to Google Chrome will resemble this example:
Software\Policies\Google\Chrome\ExtensionInstallForcelist\jmigehagkgopllnhcjngjgfblmjladih;https://clients2.google.com/service/update2/crx
System administrators can distribute and install the Applied Epic Extension to Mozilla Firefox on user workstations by editing the workstations’ registries. Before performing these steps, you may want to familiarize yourself with the Mozilla Policy Templates documentation on GitHub, which provides information on additional registry keys and their values, but be aware that the information is in flux. Make sure to download the latest release of the templates for the most accurate list.
These instructions assume that you are already familiar with the process of creating a script file to edit the registry and distributing the file across multiple workstations. Using your preferred methods for creating and distributing the file, you must edit the parent registry key containing the Applied Epic Extension to force the installation of the extension in Mozilla Firefox, as well as the parent registry key that controls the user’s ability to uninstall the extension.
These instructions identify the parent registry values and the format for editing them. After you have pushed out the registry changes to users, the extension will be installed the next time each user opens Mozilla Firefox, but it may take a moment to complete.
If your organization has previously established a restricted policy on users’ browsers to limit extension installations, you must allow the Applied Epic Extension and the Applied Epic domain (appliedepic.com) using the following registry entry:
System administrators can distribute and install the Applied Epic Extension to Microsoft Edge on user workstations by editing the workstations’ registries. Before beginning the installation, see Microsoft Edge – Policies – Extension policies for more information on the breadth of the configurable options.
These instructions assume that you are already familiar with the process of creating a script file to edit the registry and distributing the file across multiple workstations. Using your preferred methods for creating and distributing the file, you must edit the parent registry key containing the Applied Epic Extension to force the installation of the extension in Microsoft Edge. These instructions identify the parent registry key and the format for editing it.
After you have pushed out the registry changes to users, the extension will be installed the next time each user opens Microsoft Edge, but it may take a moment to complete.
The <n> is an incrementing numeric value, starting at 1 and corresponding to a specific extension, with a value in the format <store id>;<update url>. To force the installation of the Applied Epic Extension, add the store ID for the Applied Epic Extension and the specific URL for Microsoft Edge:
<store id>: iihgonfleoaicakimogonedhokljnalg
<update url>: https://edge.microsoft.com/extensionwebstorebase/v1/crx
The finished code to force the installation of the Applied Epic Extension to Microsoft Edge will resemble this example:
SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist\iihgonfleoaicakimogonedhokljnalg;https://edge.microsoft.com/extensionwebstorebase/v1/crx
If your organization has previously established a restricted policy on users’ browsers to limit extension installations, ensure that all permissions are allowed for the Applied Epic Extension and/or determine the sources from which users can install extensions, using the following registry entries:
SOFTWARE\Policies\Microsoft\Edge\ExtensionSettings
This registry key controls the configuration of the extension. The
allowed_types field lists
the types of extensions and apps that can be installed in Microsoft
Edge. The value is a list of strings, each of which should be extension, theme,
dictionary, or locale.
For the Applied Epic Extension, extension
is required.
SOFTWARE\Policies\Microsoft\Edge\ExtensionIntallSources
This registry key defines the URLs that can install extensions and
themes. You can install items from any URL that matches an item in
this list. You must allow the location of the CRX files and the URL
of the page where the download starts. Additionally, the restricted_domain
field lists domains where extensions cannot run their scripts. Make
sure this field does not contain the domain of your Applied Epic Browser
instance.
Before distributing the Epic Connection Suite Package, you must download the package. Make sure to download a version of the package that is compatible with your installed version of Applied Epic. Installing an incompatible version can result in undesirable system behavior.
Once you have downloaded the MSI file, you can distribute it using a series of PowerShell commands. For more information on running a single command on multiple machines at once, see Microsoft – about_Try_Catch_Finally.
Once the Connection Suite Package is distributed and installed and Applied has enabled the auto-update capability for your organization, the package updates itself whenever a compatible update is available, without requiring you to redeploy it. A default Windows service called Applied Epic Connection Suite Package Installer is installed with the Connection Suite package MSI file. This service performs all subsequent updates to the Connection Suite Package automatically on the user’s workstation each time they log into Applied Epic in their browser. For more information, see the Epic Connection Suite Installer section.
To prevent errors, makes sure all users are logged out and have closed all open Applied Epic browser tabs and windows. To minimize impact to users, Applied recommends installing the package outside of normal business hours.
Follow these instructions to download the Epic Connection Suite Package MSI file and invoke the PowerShell commands to distribute it across multiple workstations:
The installation also creates temporary log files. Access the overall log file (ASI.EpicConnectionSuitePackageSetup.log) in the folder you specified for the installation ($env:TEMP\Applied_Epic_Connection_Suite_Package). You can review log files for each component of the package in C:\Users\YOUR_WINDOWS_USERNAME\AppData\Local\Temp.
Note: If Applied Epic is open in a web browser on a workstation with the Desktop Connector already installed, the Desktop Connection installation will fail on that station, although the other package components will install successfully. To check for a failure of this kind, do one of the following from the affected workstation:
To resolve the issue, close all active Epic Browser sessions on the workstation and retry the package installation.
The Epic Connection Suite Package includes the Applied Epic Connection Suite Installer. This Windows service installs on your workstation along with the package and enables the package to update automatically whenever an update compatible with your current version of Applied Epic is available.
The Installer is available with version 1.38.7 and subsequent versions of the Connection Suite Package (MSI only). After the Connection Suite Package and the Windows service are installed (using the Single installation or Mass Installation workflows above) and Applied has enabled auto-update functionality for your organization, Applied Epic compares the user’s current version of the desktop connector to the minimum required version for the user’s version of Applied Epic each time they log in in their browser. If the installed version is lower than the required version, the MSI file for the appropriate version downloads and installs to their workstation automatically.
To troubleshoot issues related to Connection Suite updates with the installer service, view the log file (with a file name such as Applied Epic Connection Suite Installer20241003.log) in C:\Program Files (x86)\Applied Systems\Applied Epic Connection Suite Installer\logs\.
Once the Applied Epic Connection Suite Installer service is installed on a user’s workstation, Applied recommends denying the Connection Suite security permission in Program Access > General > General (if they have it granted). If you leave the permission granted, the user receives notifications about new Connection Suite updates and may click the Install Update button in the Connection Suite window. This manual update can conflict with the automatic updates.
If users manage their own installation of Applied Rating Services, you may want to leave the permission granted. However, make sure to educate users about the Connection Suite auto-update functionality and direct them to disregard the Connection Suite update notifications.
If you prefer to continue managing Connection Suite updates manually, you can execute the following command in a CMD prompt with administrative privileges to exclude the Applied Epic Connection Suite Installer service from the Connection Suite Package installation:
Because the Epic Connection Suite Package includes Print Center, uninstalling the Epic Connection Suite Package purges any existing incomplete print jobs. Make sure to complete all print jobs before uninstalling.
Before you update to version 1.38.7 or subsequent versions of the Connection Suite Package, you must uninstall any previously installed versions of the package. If you are not a Windows administrator, you will be prompted to enter an administrator's password during the uninstallation process.
To uninstall the Applied Epic Connection Suite Package, follow these steps:
For Windows 10:
For Windows 11:
Uninstalling the Connection Suite Package also uninstalls the Applied Epic Connection Suite Installer service. If you want to uninstall only the Windows service while keeping the package installed, follow these steps to uninstall it using a PowerShell script: