Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Rollback process for product catalog changes

aparna_u
Giga Contributor

We have created a product catalogue and published it with few Product specifications, product offerings and characteristics.
Now it is working fine and we are able to place orders using this catalogue. Now customer needs to remove some characteristics from product specification.
For this, we need to create a new version of PS, remove the characteristics and publish it and we need to associate with Product offering which requires new version of prod offering also to be created. We also need to retire the previous versions of product specification and offering. This gets very cumbersome with every incoming change. Is there a simpler way to manage these catalogue changes and also rollback them when needed from one instance to another.

2 REPLIES 2

Tanushree Maiti
Kilo Patron

Hi @aparna_u 

 

For minor changes that do not affect the core product structure (like updating descriptions or removing non-critical characteristics), use the Minor changes to published product offerings and specifications  feature.

 

The best practice is to capture all changes  in a dedicated Update Set.

 

Move the update set to next higher instance ( e.g Dev- test)

either by Update Source ( if configured) 

Or Update set :  Export xml -> Next instance import xml

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

SohamTipnis
Mega Sage

Hi @aparna_u,

 

Right now you are following strict versioning in ServiceNow, which is why every small change is becoming complex. For minor updates like removing characteristics, you don’t always need to create a new version of the product specification and offering; you can update the existing one directly if it doesn’t impact active orders.

You can also use effective dates instead of retiring records, so older versions remain for history without cluttering the catalog. For moving changes and rollback between instances, use update sets or source control instead of recreating everything.

In short, use versioning only for major changes, and keep smaller changes simple to avoid unnecessary overhead.

 

Let me know if this helps!!! 😉

 

If you find my answer useful, please mark it as Helpful and Correct. ‌‌‌‌😊


Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10