Which is the way to migrate in all instances record producers created/edited using catalog builder?

[GeoVic Gkou]

Hello everyone,

Catalog Templates have been created ,using catalog builder, so users can create record producers by themselves, then the development team can approve that form and apply additional requirements/scripting logics, so the form can lead to the creation of an HR Case.

• Which is the correct environment for those templates to be used (dev,prod)?
• If they can be used directly in production by stakeholders , which is the best way for administrators to apply changes once they receive the approval RITM and before the item has been published?
• How those changes can be migrated to lower environments or the opposite?
  
  
  

Just have the above questions related to the maintenance/migration of the updated record producers.

[Community Alums]

We have a lvl 1 service desk along with some business units creating catalog items via catalog builder in production; the business users creating items do not have access to Dev. Once submitted the draft catalog item goes to the appropriate team for approval and subsequent publishing. 

Once a catalog item is published we apply the update set which is created by Catalog Builder to the Dev environment. We also apply copies of the Prod database fairly regularly to the lower environments which keeps things in line. 

[GeoVic Gkou]

What if before the approval the approver notices that the change is not complete and the item need fixes by someone with admin rights to add script etc.?
What happen at this point?