Initializing help system before first use

Scenario Attachments

Scenario attachments can both be read and written by the model.

They have two main uses: as an optional source of input data, and as a way of creating alternative result artifacts, such as a PDF or a spreadsheet.

When a scenario is created it has no attachments, so the model should check whether the attachment existed after trying to download it from the server. One option is to check for an app attachment of the same name if the scenario attachment does not exist: 
insightgetscenattach('input.dat') 
if insightattachstatus <> INSIGHT_ATTACH_OK then 
  insightgetprojattach('input.dat') 
end-if

This allows an app to supply a default input data file as an app attachment, which can then be optionally overridden for each scenario by downloading it, modifying it, then uploading it as a scenario attachment.

A model can also create scenario attachments as a result of its execution. The file to attach must exist must first be created in the Mosel working directory before being transferred to the server: 
! E.g., use mmsheet to create a spreadsheet containing result data, then: 
insightputscenattach('results.xls')

Several other subroutines are available which affect scenario attachments.

Calling insightsetscenattachdesc provides a description for an attachment, which will appear in the attachments dialog in the web client and can be retrieved using VDL and the JS API.

Hide an attachment using insightsetscenattachhidden, so that it is not visible in the attachments dialog in the web client until the user chooses to show hidden attachments.

Rename an attachment using insightrenamescenattach.

List all the available scenario attachments by calling insightlistscenattach, and retrieve information a particular attachment using insightgetscenattachinfo.

Note An app or scenario can have a maximum of 250 attachments, each of which has a maximum size of 150Mb. Scenario attachments are included when cloning and exporting the scenario.
Note While a scenario is queued or executing, the scenario attachments cannot be modified by another user. App attachments are not locked in this way, so care must be taken to ensure that changes to app attachments do not affect an executing model unexpectedly.
Parent Topic Using Attachments

© 2001-2019 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.