Moving Update Set after building new Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 04:48 AM
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.
- Labels:
-
Service Portal

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2020 07:08 AM
Unfortunately it is not possible to target a PDI with a clone from another instance (intentionally disabled).
Michael D. Jones
Proud member of the GlideFast Consulting Team!