Uploading Apps
Apps can be uploaded from two sources: .zip files containing new apps and .insight files exported from a running system.
![]() |
Note Certain potentially insecure file extensions cannot be used as attachments. If you have
FICO® Xpress Insight Server hosted on-premise then you can configure this setting to select which are allowed, however the DMP version of
Xpress Insight Server prevents use of the following extension types:
apk, asp, aspx, bat, bin, c, cc, class, conf, cpp, css, dll, exe, gif, iso, java, js, jse, jsp, lib, php, phps, phtml, properties, ps1, rar, rpm, sh, swf, tar, tga, tiff, vb, vbe, vbs, vbscript, war, xlm, xlsm, xltm, xsdt. The
Xpress Insight Server will block any import or upload of a Repository, App, Folder, or Scenario that contains one or more attachments with blocklisted filename extensions. For more on configuring the extension blocklist, see the chapter on Securing FICO Xpress Insight in the FICO Xpress Insight Installation Guide.
|
Each .zip file contains the artifacts that comprise the app: configuration files, compiled model, embedded data files, UI code as html and JavaScript. These are the necessary elements to create a new app in the application.
The .zip files are located on your local machine. For example, the .zip file of the Campaign Conversion app is located in the C:\xpressmp\examples\insight\javascript\campaign_conversion\ folder.
Each .insight file is a proprietary binary file format written out when an app is exported. Each .insight is a live app, potentially with existing scenarios in various states, previously exported from a running system.
See your administrator for the location of your organization's .zip and .insight files.