CadActive Application Directory Structure

Modified on Wed, 01 Dec 2021 at 05:47 PM

Once a user downloads the CadActive application, by default, a folder structure is created in %LocalAppData%\CadActive.

cadactive-launcher, cadactive-creo

When the application is first downloaded, all these folders will show except the cadactive-creo folder. When someone loads the application the first time in Creo (see more information here), CadActive's launcher (cadactive-launcher) will analyze which version of Creo the user is running and download the correct Creo CadActive application and place it into the cadactive-creo folder. So long as a user can connect to the internet and the AWS server where we host our application, the Launcher will also update the cadactive-creo folder based on the latest version of our Creo application when we make updates.


The config folder is important for when organizations needs customized settings. The four potential files that can live within this directory are:

  • cadactive-server.txt - This file is for pointing organizations servers somewhere other than our productive server, for example our staging server or an on-premise server. See more information (here).
  • license.json and settings.json - These files are for organizations that cannot connect to our license and settings via the internet and need the downloaded locally, see more information (here).
  • cadactive-debug.txt - This file enables debug mode within our application, see more information (here).
  • cadactive-proxy-info.txt - Some customers pass their network communications through a proxy server, this file can be configured to point our application through the same proxy server, see more information (here).


The cache folder is responsible for storing user login information if a user decides they want to. When a user logs in and selects the "Remember E-mail" button, a user.json file gets written in this cache directory that stores the email for next time use. If a user selects the "Stay Logged-In" button, an authentication token will get stored in this file as well. The next time our app loads, their email will be remembered and they will automatically logged in.


This folder is used often for metrics and other miscellaneous logging when enabled by the user.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article