Initializing help system before first use

# Managing the Component Lifecycle

When it is installed, the Xpress Workbench component is a fully working configurable application that can be set up to perform a wide range of tasks.
When you choose to deploy a new version of Xpress Workbench as it becomes available, follow the upgrade lifecycle to protect your apps and data.
Note: The component lifecycle only promotes Xpress Workbench upgrades and should be used specifically to test a new version of Insight prior to deployment.

Promoting Xpress Insight does not promote app implementations. This means any apps must be re-imported to each environment after the Insight component has been promoted.

For more information about developing, exporting, and importing apps, see the Insight 5 Mosel Developer Guide or the Insight 5 Python Developer Guide.

Note: Xpress Workbench 3.18 on FICO® Platform uses path-based routing for components. Multiple components now have the same URL domain name, but different paths.
Upgrade lifecycle:

1. Any existing apps deployed to Xpress Workbench should be backed up by exporting them before beginning the upgrade.
2. Create a new component.
3. Navigate to the Backup Archive page.
4. Restore the project from the original component.

A typical Xpress Workbench component lifecycle runs as follows:

1. Any existing apps deployed to Xpress Workbench should be backed up by exporting them prior to beginning the upgrade.
2. The new version of the Insight component is deployed to the Development environment and the exported apps are re-imported for test.
3. The new version of the Insight component is then submitted to the Staging environment, and the exported apps are re-imported for testing and approval.
4. When approved, the Insight component is deployed to the Production environment.

The three lifecycle environments (Development, Staging, and Production) are distinct from each other and require separate Xpress Workbench servers, data repositories, authority, and access control settings for each. However, all the environments can access a shared list of user accounts.

Parent Topic Deploying Components to FICO® Platform

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