catalog Item and variable set captured in update set automatically by system

[Community Alums]

Hi,

When any variable or UI policy is updated for an item. Automatically the Catalog item and the variable set also captured in the update set by system. This issue was observed after upgrading to Vancouver version. How this can be resolved? For now we are moving the updates manually to Global update set.

Thanks,

Ripunjai

[Maik Skoddow]

Hi @Community Alums 

I have no insights into your instance, and therefore don't know more artifacts are captured than the changed ones. But at the end it is not an issue and I would leave as it is. It doesn't play any role if the artifacts on the target instance are identical.

Maik

[AnveshKumar M]

Hi @Community Alums 

When you create/update anything related to Catalog Item, like Catalog UI Policy, client scripts etc., the version (field: version) of catalog item gets changed causing an update to the catalog item record (table: sc_cat_item). So, the catalog item gets captured in updatesets.

Please mark my answer helpful and accept as a solution if it helped 👍✔️

[Community Alums]

Hi @AnveshKumar M , @Maik Skoddow 

Till Tokyo version this was not observed. Only after upgrade to Vancouver version this issue arised. Due to this,

Use case scenario

whenever 1 developer is working in dev instance and still development is pending on the item or variable set.

Later for another developer, the requirement is to update only UI policy for the same item. Due to this, the pending work/development from the first developer is also captured by another developer and moved to Production. This will impact the existing logic of the item. So, I was checking for the solution how this can made same logic available in Tokyo version.

Thanks,

Ripunjai

[AnveshKumar M]

@Community Alums  I expected this Scenario.

I just compared the sc_cat_item table in Vancouver and Tokyo, the version field is added in Vancouver/Utah (I don't have an Utah instance spinning to check) it seems. And I couldn't find anything related to this in Release notes of both Vancouver and Utah.

I further investigated and found that, a system Script Include sn_sc.CatalogItemVersioningService handles the versioning of catalog items and we can not see the contents of this script include.

For now, You need to clean up the Update sets manually. OR raise a case with ServiceNow.

Please mark my answer helpful and accept as a solution if it helped 👍✔️