nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Redirect Any Item to a Replacement Item

BBurkholder

With the February 2026 ArcGIS Online release, ESRI introduced “Replacement Items” to transition users from retiring apps — ArcGIS Configurable Apps and Classic Esri Story Maps. The workflow is documented here:

https://doc.arcgis.com/en/arcgis-online/manage-data/replacement-items.htm

This idea proposes expanding Replacement Items so they can be used for ANY item type within ArcGIS Online, especially maps and applications.

The existing "Replacement Item" experience on an item’s Settings page works well, but currently only takes effect when the retirement is triggered by an ArcGIS Online update. In the February 2026 update, Replacement Items could be configured ahead of time but did not activate until after the AGOL release. Item owners need more control over when and how these redirects go live.

Screenshot 2026-03-18 091202.png

This idea proposes the following enhancements:

When an item is marked as deprecated, the “Replacement Item” option becomes available to the item’s owner within Settings.
When a replacement item is designated, the redirect takes effect immediately; OR
Ideally, owners could specify a future date when the redirect begins.

If a scheduled retirement date is set in the future, users could see a notification or pop‑up showing the planned retirement date, with options such as “View New App” or “Stay on Current App.”

Screenshot 2026-03-18 091719.png

After the retirement date passes, users would automatically be redirected to the new item.

Screenshot 2026-03-18 092033.png

Why a scheduled date option is important:

Many organizations follow required notice periods for software, dataset, or application retirement — often 30 to 90 days. While item owners can manually apply deprecation or redirect on a given date, providing a built‑in user-facing warning and the ability to preview the new application creates a smoother transition and better user experience.

Even without a scheduled date option, the ability to set replacement items for any item type would provide immediate value and help organizations prepare for upcoming app retirements (for example, Web AppBuilder in 2027), ensure users access the most current resources, and maintain compliance with internal deprecation and sunsetting policies.

In short, broader support for Replacement Items would help:

Prepare for and communicate future app retirements
Redirect users to the most up‑to‑date maps and apps
Deprecate items cleanly while guiding users to newer versions
Improve the overall user experience by reducing confusion and broken links

Implementing this functionality would meaningfully improve item lifecycle management in ArcGIS Online.

Vind meer berichten getagd met

Status: Openen

Reacties

D_Atkins

I just want to throw in that while this Idea is rightfully focused on "Replacement Items" workflows, that there is a higher-level architectural need for the ability for AGOL administrators to set and update Content Ids.

I.E. even within Experience Builder -- an organization may develop a test or pilot application to test the business side of things. When that workflow matures, there may be a desire to redevelop a 'better' version of the same application, and when prepared, to replace the test version. This is just one of many use cases, I'm sure.

See: Overwrite Experiences to Maintain IDs - Esri Community

RobBlash

I like the deprecation flag as a control for the replacement items. Great idea!

TrebinMT

I would like to reinforce this idea and suggest an enhancement to ArcGIS Online that would significantly improve how organizations manage deprecated content.

Currently, identifying deprecated or soon-to-be-retired items in the ArcGIS Online UI is difficult. Searching by app type is not sufficient, especially given the broad use of “Web Mapping Application” for many legacy apps, including Classic Story Maps.

I recommend introducing a dedicated content filter that allows users to easily identify items that are deprecated and scheduled for retirement. This would be distinct from existing item status tags such as “Authoritative” or “Deprecated,” which are used intentionally by organizations to describe content currency and trust.

Instead, this filter would reflect Esri-defined lifecycle status, enabling users to quickly locate affected content without relying on keyword searches, URL inspection, or deep familiarity with app types. This would greatly improve usability, particularly for less technical users.

Additionally, it would be valuable to include deprecation and retirement status in Organization Item Reports and Dashboards. Exposure of this information through the ArcGIS API for Python would further support automation and proactive content management at scale.

PeterKnoop

I would also add the use case of needing to redirect users when content is moved between ArcGIS Online organizations and/or Enterprise portals. If the initial URL was widely circulated and used, it would be helpful if a redirect could be provided for folks visiting that URL, which would take them to the new version of the item at its new location.

SharonJanzen__B_Sc_

With the retirement of webappbuilder and classic storymaps, it would make sense to expedite this idea. I'm madly re-creating apps in advance of the retirement of webappbuilder apps and it would be handy to be able to redirect users immediately after I've made the new app. Unless I'm missing something... please correct me if this functionality already exists. Cheers!

Doe mee aan het gesprek

Meld je aan om te posten, content te volgen en meer. Nieuw hier? Registreer gratis.