Moving Update Set after building new Service Portal

[ZGauss]

Hello,

I have built a new service portal with all kinds of new widgets, items, workflows, notifications, etc.

I created a new update set and just called it Service Portal in the global application. I have noticed some things that might not be captured in the update set. For example, I have made some changes to instance options on the order status page to not display delivery date or stages, but I did not see it captured in the update set. Also, I have noticed after making some changes to a workflow I did not see it captured in the update set. I always make sure I have my Service Portal update set selected when making changes. Is there a way for me to test moving/completing the update set without a test instance? Should I expect issues when moving the update set to prod? I have a feeling that some of the work I have done will not come over to prod once I am ready to move the update set.

[johnfeist]

Hi ZGauss,

Update sets do not capture data, so in many cases when you change settings they will not be captured.  If you have a lot of settings that need to change, I'd suggest setting up a fix script to run either before or after you apply your update set(s).  The alternative is the Santa Claus model (make a list and check it twice!).

The only way that you can test running an update set outside of your dev/test/prod environment is to use a personal developer instance (PDI).  The caveat around that is when you get the PDI it is absolutely standard OOTB ServiceNow including sample data.  The PDI may not be the same version as you are using for development.  If you can overcome those limitations, you can export your completed update set to your computer and then import it to your PDI.

Hope that helps.

:{)

Helpful and Correct tags are appreciated and help others to find information faster

[ZGauss]

Thank you johnfeist. unfortunately I am way too far in to now use a santa claus model. I will try with my PDI.

[Michael Jones -]

You are correct in that some configuration is not captured within an update set, which can lead to a frustrating experience at times. For Service Portal however I tend to find most updates are there, just not necessarily captured as individual updates - they are contained as a reference within another update so when you make the change you don't see a new line, but see an existing line change in updated date. 

With workflow, always be sure to publish the workflow (that is when the change is captured, not on save). 

As far as testing, it is a difficult proposition. If you have a PDI (or can manage to request a new you) you can move the update set there manually (export to XML) and try it out. 

Otherwise, I'm afraid, you will have go to prod and see what you get...and fix from there. 

If this was helpful or correct, please be kind and remember to click appropriately!

Michael Jones - Proud member of the CloudPires team!

[ZGauss]

I will certainly try that, thank you.  My plan when moving to prod was pretty much what you stated and I would to do it on a Friday night then spend all weekend fixing what was not working properly or was not captured.  Do you know if it is possible to clone over a PDI with an actual instance?