Initializing help system before first use

Local Data Changes

When a scenario modification is completed successfully the server does not issue a data change event to the client that submitted the change.
However, the JavaScript API creates local data change events within your view so that the scenario observers are triggered to update. The way this works changes slightly depending upon which method you use to create the ScenarioDataChange object:
  • Scenario#modify: When completed successfully a change event will trigger other scenario observers listening to any modified entities to fetch the latest data from the server and be called with that data. The observer from which the scenario object originates will NOT be notified of any changes related to this request. It will be your responsibility to make sure the changes are not only committed to the server but also applied to any UI elements managed by this observer.
  • View#modifyScenario: When completed successfully a change event will trigger all scenario observers listening to any modified entities to fetch the latest data from the server and be called with that data. You need to be careful not to use this within an observer which you don't want to refresh after the change, use the other method instead. It would cause forms or editable tables to redraw and so possibly lose the user's position or focus.

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