Initializing help system before first use

Summary of Companion File Changes

This section lists the major companion file changes.
  • There is a new mandatory attribute, version, on the <model-companion> tag, which must have a value of "3.0".
  • The XML namespace attribute (xmlns) is mandatory on the <model-companion> tag.
  • The <client> tag no longer has an id attribute.
  • The <interfaces> and <interface> tags have been removed. Views are now defined within one or more <view-group> tags, which contain <*-view> tags specific to the view type.
  • Custom views must be explicitly declared using the <custom-view> tag, or they will not be visible in the UI.
  • All interface attributes now appear on the <*-view> tag, including:
    • title (was text)
    • id
    • authorities
    • default
  • New requires-scenarios-loaded attribute on view tags, which can be set to false to make a view available when the current scenario has not been loaded. This is useful when creating a custom view for editing model parameters before loading a scenario.
  • The <version> tag has been renamed to <project-version>.
  • The authority names listed in the authorities attribute for a view must be space-separated (previously, they could be comma-separated).
  • The <client-resources-local-path> tag is valid only within the <client> tag.
  • The <object-type-defaults> tag is obsolete; the default action when double-clicking a scenario is to open the default custom view.
  • The baseline-only attribute on model resources has been renamed to load-only.
The other sections of the companion file remain largely unchanged from release 2.0:
  • Schema
  • Model resources
  • Database mirrors
  • Custom authorities
Parent Topic New Companion File Format

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