Public API to unarchive configurations and other artifacts both global and local

The gap is to do with the huge amount of snapshots and streams that will need to be archived to leverage Jena Index reduction in CLM 6.x.

Also for enterprises, that plan to have a regular cleanup of active configurations on regular basis on some criteria, it is important to automate such actions. We cannot expect 100s of configurations to be manually archived OR restored. This will continue to be valid use case, even if Jena cleanup is no longer a scenario in 7.x platform.

We implemented utility to archive using public APIs. We also have need to restore an entire hierarchy of configurations, in case of need.

In this case, there's no public API to implement this. To enable a maintained utility, we need to have public API to restore configurations.

Can you explain the use case you are trying to solve by using these APIs? Is there some underlying gap in the product we should be considering?

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)
Component - Feature
Operating system - Linux
Source - None

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS (formerly Rational DOORS)
Component - API
Operating system - Linux
Source - None

Please clarify: what is the use case for needing to un-archive? It's our assumption that it's a rare and unusual situation to need to un-archive. Do you see it similarly? If not, please elaborate