Missing customer updates in update set

[oluseyiasol]

i have been working on creating a service Catalog.  AFter pushing the update set to our Test environment, i noticed that some catalog UI policy actions were missing, in addition to the order number of some variables being missing , which makes the variables appear in the wrong locations on the request form.   Assuming i have identified all the missing customer updates.  How can i capture them in the 'fix-it" update set in my dev environment?

[Hemanth M]

Hi @oluseyiasol ,

1. Create a new update set in dev and recapture missing items (by adding, removing something) so that it captures in your new update set.
2. once done move it to test
3. if everything looks good, create a new update set in Test (may be name it as Parent Batch) and original and additional update set as child to this update , using a parent filed
4. Move it Prod.

Hope it helps!

[Rafael Batistot]

Hi @oluseyiasol 

Create a new update set and transfer to new one 

https://servicenowontoast.com/2024/06/11/configuration-in-the-wrong-update-set/

[Tanushree Maiti]

Hi @oluseyiasol 

Assuming the existing update set is UpdateSet_A, follow the steps below:

1. Create and Set the Active Update Set

• Create a new update set, for example UpdateSet_B, in the Dev instance to address the issue.
• Mark UpdateSet_B ( just an example) as In Progress and set it as the current active update set.

1. Re-capture the Missing Catalog Item Variables

• Navigate to the relevant Catalog Item.
• Open each variable where the Order Number is missing.
• Make a minor/trivial change, or re-enter the exact same Order Number.
• Click Update to ensure the change is captured in UpdateSet_B.

1. Re-capture the Missing Catalog UI Policies and Actions

• Open the specific Catalog UI Policies and their associated Catalog UI Policy Actions that failed to move or were missing.
• Make a minor change, such as:
• Toggling a checkbox off and back on.
• Re-entering the same description.
• Making another insignificant change.
• Click Update or Save to capture these records in UpdateSet_B.

1. Create the Parent Update Set

• Create a new parent update set, for example UpdateSet_C.
• Set UpdateSet_C to In Progress.
• Navigate to Local Update Sets.
• Open UpdateSet_A and UpdateSet_B.
• Set UpdateSet_C as the Parent for both update sets.

1. Move the Parent Update Set

Once all the above steps are completed, move the batch/parent update set (UpdateSet_C) to the next instance.

Because UpdateSet_A and UpdateSet_B are associated with UpdateSet_C, their components will be moved together in the appropriate creation order.

[AndersBGS]

Hi @oluseyiasol 

you either need to capture the artifacts in a new update set or you need to utilize the “add to update set” you can download from the community and install on your instance.