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!

[Daniel Draes]

You should be able to raise that with us through your reseller. On the other side, as long as you have a servicenow instance in our cloud, you also should be able to get a HI/Support login.

[Kartik Aysola · Accepted solution]

This is an expected behaviour with Catalog Builder. We are aware of it and we'll address it in a release in the near future.

[spike]

Thanks for the update. Feels like something that should be looked at sooner rather than later.

[Mario Quinones]

Hi,

Can you provide a HI case number that we can check to see its status?

Mario