Attaching Files
An app may require that certain app or scenario attachments be provided. These requirements are app-specific and documented by app's author. Files can also be attached for process or workflow requirements. For example, you may want to include an email with information on why you changed a scenario or a file that contains an approval for the change. These types of files have meaning for your app or scenarios, but they do not directly impact the calculations.
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 server blocks any import or upload of a repository, app, folder, or scenario that contains any attachments with these extensions. For more on configuring the extension blocklist for an on-premises installation, see
Securing Xpress Insight.
© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.