Feature Request: Cross-Workspace Version Propagation for Enterprise App Exchange

Product Suggestions
, , ,
1

Overview

In Tulip, a single instance can host multiple workspaces (often mapped to different sites). When an app is published as an Enterprise App in one workspace, other workspaces can download and publish their own copy. However, when the source app is enhanced and a new version is published, downstream workspaces do not see or receive a streamlined update path within their existing local copy. They must re-download, resulting in duplicate apps and fragmented version management across workspaces.

This request proposes version propagation and in-place upgrade capabilities within Tulip Enterprise App Exchange, allowing downstream workspaces to see new source versions and upgrade their existing app (same app identity) without creating duplicates.

Problem Statement

  • Duplication & Fragmentation: When a new version is released in the source workspace, other workspaces must download again, creating multiple apps for the same solution.

  • Governance & Traceability Gaps: Downstream apps drift from the source; it’s hard to track who is on which version and whether sites are up to date.

  • Operational Overhead: Teams spend time reconciling updates, migrating data/configs, and cleaning up duplicates.

  • Enterprise Consistency: Enterprises need a single app lineage with site-level configurations—not separate clones that diverge rapidly.

Proposed Enhancement: Enterprise App Exchange — Linked Versioning & In-Place Upgrade

  1. Linked App Identity Across Workspaces

    • When an app is published as an Enterprise App, it receives a global app ID (source lineage).

    • Workspaces that download the app create a linked instance (local app) that retains the lineage reference to the source app.

  2. Version Propagation

    • When the source app publishes Version N+1, all linked workspaces:

      • See a notification in App Exchange and in their app’s Version panel.

      • Can view release notes, diff highlights, and compatibility checks.

  3. In-Place Upgrade (No Duplicate Creation)

    • Downstream workspace clicks “Upgrade to Version N+1” on their existing local app.

    • The app maintains the same local identity and history, applying the new version in place.

    • Option to preview and test in a sandbox before finalizing.

2

Hi @OlgaStroilova ,

Please look into this as well.

3

Hi @sagar007 the features/problem areas listed here are on our radar as well, but they are longer term investments. We are in 2026 planning now, and will provide an update with the parts that we’d take on first.