Hello,
When an application goes out of support and is depreciated in AGOL, you are able to set a replacement item within the application that points to the new application that you might have replaced this with.
However, some organisations might replace the soon to be depreciated apps with the new app sooner rather than waiting for the product to be depreciated.
For example, our organisation have switched our WebApp Builder applications to Instant App or Experience Builder.
Or an organisation might switch applications as the other application might offer more functionality - for example, switch from Instant Apps to Experience Builder.
It would be good for all applications (or at least soon to be depreciated applications) to have the replacement item functionality built into them as soon as they are created or when they are soon to be depreciated.
The rationale behind this is:
- Services can update to the latest products before the old products go out of retirement
- Services can switch between new products (e.g. if the service decides to make a map more sophisticated, so move from an Experience Builder application to an Instant App application)
- Setting the replacement item for a product before it is retired will provide more time to the services to test the change-over from an old to new application.
- Services might have bookmarked the old application, so setting the replacement item would direct them to the new application
At the moment, we are going to have to strip out the content from the old WebApp Builder applications and leave only a link to the new Exp Builder or Instant App applications - but it would have been good to set the replacement items.
Please could you look into whether the replacement item could be added to your applications.
Thank you.
