decimal Launcher User Guide

The decimal Launcher is an application that allows users to authenticate securely and view many software applications that are available from .decimal. Users are then able to securely open (launch), install, and update various .decimal applications to their local computer. The decimal Launcher also allows users to install different versions of each application per site, for users that perform work for multiple sites/locations.

Access and permissions for the decimal Launcher and apps are managed through decimal Direct or by .decimal staff.

The decimal Launcher User Guide provides an overview of the decimal Launcher software as well as guides to perform common tasks using the software.

The decimal Launcher is the lightweight hub for all your new .decimal applications. It serves as a platform to easily apply updates and download new applications while allowing you as the user to only have to log in to a single platform. The Launcher will provide the following features:

• Allow users to log in with one account to access many .decimal applications
• Allow installation and updates of applications
• Verify the authenticity of all applications before opening

Please refer to the decimal Launcher version history for the complete listing of all versions and release notes.

The decimal Launcher can be downloaded from https://direct.dotdecimal.com. Note: You will have to login using your decimal Direct credentials to be able to download the software.

By default, the decimal Launcher installs for the current logged in user in their local app directory (e.g.: C:\Users\<User>\AppData\Local\Programs\decimal Launcher) and shortcuts are created in the start menu and desktop only for this user. As such, it typically does not require administrator permissions to install on local computers.

Due to the decimal Launcher being a lightweight, simple application, there are no steps necessary when installing the decimal Launcher application other than running the installer (e.g.: no configuration files, no custom options, etc). However, the Launcher allows access to other .decimal Apps that may require additional setup steps, please so refer to each app's individual User Guide for setup details.

If it's desired to install the application for all users, IT departments may install the software to a folder accessible by all users (e.g. C:\dotdecimal\) and then create desktop/start menu shortcuts for the “Public User” so that all users have access to a single installation.

1. Launcher maintains an individual AppData folder for each Windows user. As such, each user will have a separate directory where their Launcher application data is stored. Application downloads should be small and fast from .decimal's servers. Additionally, most of .decimal's customer applications (e.g.: p.d) allow editing the application's settings to point to a shared centralized patient database so that users can share application data even though Launcher separates their settings.
2. In the event the decimal Launcher needs to pull and install a new update, the update will be installed to the current Launcher installation folder. Any manually created application shortcuts in the start menu or desktop will not be altered, however, the user performing the update may see an extra shortcut created on their desktop if they do not disable that option during the upgrade.

The decimal Launcher software can be updated by either running a new installation package (follow instructions above) or by an automated in-place update that is managed directly through the Launcher software. The automated (in-place) updates are used only when the currently running version of Launcher has reached End-of-Life (EOL) and can no longer be used. Since not all users will have the necessary permissions to perform a software update, .decimal will generally provide a minimum of 30 days notice for new releases, such that users have a fair amount of time to request assistance from their IT/IS team in updating the software. After the 30 day grace period is reached, the EOL Launcher version will require the in-place update to be completed before allowing access to any .decimal applications.

Authentication is done through your .decimal Auth0 account. If you do not have an Auth0 account please contact your site’s .decimal admin or .decimal customer service at 1-800-255-1613. Once you have your Auth0 account, open the launcher and you should be directed to the login page:

Fig. 1: Main Login Page

Type in your username and password and you will be logged in.

If you have forgotten your Auth0 password or want to reset it you can do so from the Launcher’s log in page.

Fig. 2: Password Reset Request

Fig. 3: Password Email Input

Select the “Don’t remember your password?” link and enter your email that is associated with your Auth0 account. You will receive a link in your email and instructions on resetting your .decimal Auth0 password.

Fig. 4: Password Reset Email Example

Fig. 5: New Password

The primary function of the Launcher is to download .decimal applications. After logging into the Launcher and selecting a site you will be presented with the applications available for that site. After selecting an app if you do not have it installed then the Launcher will have a “Download” button available.

Pressing the “download” button will download the version of the app that is listed. After downloading or if you have the app already installed the button will change to a “Launch” button. The application is now ready to be opened and used as normal.

Fig. 6: Downloading Applications

Fig. 7: Launching Applications

When .decimal releases a new version of an application the Launcher will notify you by showing you a message above the “Launch” button for that application.

Fig. 8: Update Available Warning

The Launcher it’s self will not download this update automatically. The only way to receive this new version is for your site Admin to approve this update and set it as your site’s version for this app. Instructions on how to do this can be found in the decimal Direct User Guide.

Once the application version is set in decimal Direct for your site, the decimal Launcher will enforce the download and installation of the application for all users of that site.

The decimal Launcher provides a “Sandbox” area to install new versions of applications in order to test them before Clinical release. This area is separate from all of your Clinical applications so they will not affect any patient data.

NOTE: This option will only appear for users with the user level 'Elevated' (for Physics access) on their decimal account.

The Sandbox environment requires explicit setting of the app version for each site. This is done using decimal Direct in the Manage → Apps page. Refer to the decimal Direct User Guide for more information.

Once the Sandbox app version is set, it will appear in the decimal Launcher

To switch the Launcher to Sandbox mode click the dropdown menu in the top bar and select “Switch to Sandbox mode”.

Fig. 9: Switch to Sandbox Mode

When you switch over to Sandbox mode you will notice the Launcher has a different look to clearly distinguish you are not opening Clinical versions of these applications. All apps opened by the Launcher while in Sandbox mode will also open in their Sandbox modes, if the app provides support for Sandbox usage.

Fig. 10: Sandbox_UI

In order to maintain the safety of our users and our applications the Launcher provides the following safeguards:

• Inactivity Timeout:
  • The application inactivity timeout is set to 10 minutes by default. If the user performs no keyboard/mouse interactions within the application within that time period they will be automatically logged out and required to re-authenticate
  • NOTE: This value can be changed in the App settings
• Session Timeout:
  • Once a user logs in using Auth0 the user's authentication session token is valid for 10 hours. After which they will be required to login and re-authenticate to the decimal Launcher. Any applications launched from the decimal Launcher that are using this token will need to be relaunched once the user has re-authenticated in the decimal Launcher

• If any file in the application directory is added, removed, or altered in any way the Launcher will refuse to open the app. The Launcher will then delete and reinstall the altered app. Because of this it is suggested that you do not attempt to store any files in these directories as they will be removed.
• If a critical bug or vulnerability if discovered in an existing release of any application .decimal will flag that version invalid. When the Launcher attempts to open an invalid application, it will notify the user and delete the application entirely.

This ensures binary file security to ensure that the application files are not tampered with on .decimal's server or on client work stations (via hashes and checksums).

All administrative actions such as setting app versions or adding users can be completed though the decimal Direct Admin page. For more information please refer to the decimal Direct User Guide

Certain app settings can be set to modify the behavior of the Launcher.

The app settings can be accessed via the Cog at the top right corner of the Launcher window:

Fig. 11: App Settings

Currently the following settings can be changed:

• Timeout Time: Sets the amount of time before the inactivity timer logs you out of the app. The default is 10 minutes.

Make sure to “SAVE” your changes once you are done to ensure you do not lose them. Fig. 11: Edit App Settings

For questions, comments, support requests, bug reporting, or to schedule a training session, please contact our customer support team at: 1-800-255-1613

This section details a few very common errors and resolutions end users can experience while using the decimal Launcher. If you experience an issue not on this list or have questions please contact .decimal customer support.

On February 28th, 2025 .decimal's cloud authentication provider performed maintenance on their services. This resulted in the decimal Launcher having a minor display error, where the placeholder text “Email Address” and “Password” does not shrink away while typing as shown below. Please note that this issue is only a display error and the text you are typing is properly being entered into the application. So the decimal Launcher Application can continue to be used as normal, you just will not be able to see the first 14 characters typed in the email or password fields.

We are working on a fix to correct the issue and the Launcher Application will automatically update when this fix is released. No further action is needed at this time, you may simply continue to use the Launcher application normally. Sorry for any inconvenience. If you have any questions please contact .decimal Customer Support at E-Mail: customersupport@dotdecimal.com or Phone: 1.800.255.1613.

• Error: Request failed with status code 401
• Explanation: The user authentication token sent to .decimal servers is incorrect. This is typically due to Web Security Appliances (WSAs) intercepting/inspecting our HTTPS traffic on the hospital's network, which can change the authentication request headers.
• Solution:
  • Follow the IT Support Common Issues and Troubleshooting Steps guide for WSAs and unrestricting .decimal HTTPS traffic.
  • Note: If your IT department has applied any security updates to whitelist .decimal servers, this may required users to logout and re-login or reboot the workstation to apply the new policy updates. This step is entirely dependent on your clinic's IT security setup and policies and how those policies have been implemented. For assistance please contact your IT department.

The following requirements are needed to be met prior to running the decimal Launcher.

Note: decimal Launcher is a lightweight ElectronJS application and does not require moderate hardware resources. But the applications it installs and manages could require much more substantial resources. Refer to each app's individual userguide for its specific hardware system requirements.

1. The decimal Launcher uses decimal Direct to manage site, user, and application permissions. As such, the decimal direct IP address 64.128.252.104 port 443 must be whitelisted for the decimal Launcher to pull user, site, and application permissions.
2. The decimal Launcher uses Auth0 via decimal Direct's API for user credential management (i.e.: login authentication). As such, the Auth0 IP address(es) may need to be whitelisted in order for users to be able to login and authenticate with the secure Auth0 servers. While .decimal's applications use the decimal Direct API to authenticate, the decimal Launcher uses Auth0 connections to provide the login page and pull Auth0 tenant information. The Auth0 whitelist documentation provides details on the Outbound and Inbound firewall settings.
3. The decimal Launcher uses Azure EastUS IPs, https://decimaldirect.blob.core.windows.net, and http://ocsp.msocsp.com to download application packages and updates. These will need to be whitelisted in order for the user to download apps within the decimal Launcher.

Copyright © 2020-2024 .decimal, LLC. All Rights Reserved.
.decimal, LLC. 121 Central Park Place, Sanford, FL 32771. 1-800-255-1613