Catalog Builder / Update Set bug

[spike]

I think I've found a bug. I can't report it to ServiceNow as I'm not a direct customer (we buy through a reseller hence I don't have a support logon). At least I've not found a way. Therefore I thought I'd post it here for thoughts.

When you create a new catalog item through the Catalog Builder, because the current update set captures ALL of the changes the Catalog Builder makes, including all its saves and temporary actions as you go through the build and publish process, you end up with customer updates in your update set that refer to a sys_id that doesn't exist.

I've added an attachment that takes you through the steps to reproduce this if anyone is interested. 

I'd be interested in anyone's thoughts, and if there's a way I can raise this with ServiceNow I'd be interested in that as well. Or maybe just point out I'm a complete muppet and I'm doing something wrong!

Thanks!

[Kartik Aysola]

Hi,

This is being taken up as an enhancement and not a defect, hence we do not have a case task for this. Unfortunately, there is no way to track it by our customers 😞 

Kartik

[Kartik Aysola]

This has been fixed in the Tokyo release. Once you upgrade to the Tokyo version, you will no longer see the draft items captured in the update set. Also, to make it easier to manage update sets w.r.t. Catalog Builder, especially for business users who have no knowledge of update sets, we have come up with a feature in Tokyo whereby update sets are automatically and exclusively created for the changes made via the Catalog Builder. Click here to know more about this feature.

[Adam43]

This feature of the auto-generated update sets for catalog builder- there needs to be better management for those update sets.  I'd like to have a property to turn off the auto-created update set entirely- as we'll capture the work in a developer update set.  Or maybe make it possible to have all catalog builder work done inside a master parent batch.  all configurable within catalog builder's UI.