How to Preserve API-Created Service Catalog Items During Clone Without Overwriting Lower Environment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
We are working on Clone Management and need guidance on preserving Service Catalog items that are created automatically via APIs in lower environments.
In non-production environments, applications are on-boarded through APIs, which automatically create:
Service Catalog Items (sc_cat_item)
Variables and Variable Sets
Flows / Execution Plans / Workflows
Related configuration records
These catalog items also have environment-specific customizations, which are manual and not captured in Update Sets.
Key questions we are trying to address:
Is it possible to preserve API-created catalog items and related configurations during a clone, similar to how standalone tables are preserved using Clone Profiles?
Can catalog items and related tables be excluded or frozen during a clone to prevent overwriting lower-environment configurations?
If exclusion is not feasible, is a recommended approach to:
Clone everything,
Remove catalog data,
Recreate catalog items via APIs,
Reapply customizations through scripts?
What is the best way to identify and configure all related tables correctly in:
BAU Clone Profiles (limited data)
Full Clone Profiles (full production data)?
How can we ensure in-development applications and catalog configurations are protected during clone activities?
Looking for best practices or proven approaches from the community to handle API-created catalog items and environment-specific configurations safely during cloning.
