All pages
Powered by GitBook
1 of 1

Loading...

Dependency Configuration

Video

This video explains how to start a new release cycle in Simplex. - You will learn how to select and upgrade your extension's dependency version to prepare for content development.

Step by Step Instructions

1. Navigate To Manage Edition

To start a new release cycle in Simplex, navigate to the Manage Edition section to begin managing your extension's release cycle.

Navigate To Manage Edition

2. Open Current Editing Site Window

The "Manage Edition" interface shows the different phases of the release cycle - starting with the editing phase. - Steps for preparing the release and publication are grayed out. These steps will be actionable once the new editing process is complete.

Open Current Editing Site Window

3. Review Dependency Configuration

In the editing phase, first set the dependency configuration. -- The parent edition that the extension in this example depends on is the International Edition, January 2024 version.

Review Dependency Configuration

4. Identify New Version Availability

The blue link indicates a new version is available due to one or more releases of the International Edition since the current version.

Identify New Version Availability

5. Start Release Cycle With New Version

Start the release cycle by clicking the link to select the new version your extension will depend on.

In this demonstration, we will select the January 2025 version.

Now - Run the dependency upgrade process to set the new version as the dependency for your extension.

The system upgrades the dependency and enters maintenance mode to apply the new version settings. This may take a bit of time.

The new version will be used to validate all artifacts and derivatives within your extension. It will also be the version used for classifying any concepts created in your extension.

Once complete, the new version, such as the January 2025 edition, is set as the dependency.

You are now ready to proceed to the content development phase, where you update all artefacts and derivatives.

For more information, see the related videos on content development and release management.

6. Choose Dependency Version

7. Run Dependency Upgrade

8. Monitor Upgrade Progress

9. Validate Artifacts Against New Version

10. Confirm New Version Set

11. Prepare For Content Development

Provide Feedback
Start Release Cycle With New Version
Choose Dependency Version
Run Dependency Upgrade
Monitor Upgrade Progress
Validate Artifacts Against New Version
Confirm New Version Set
Prepare For Content Development