--- name: update-set-workflow-45bd25d33f84 description: Manage ServiceNow update sets — create named sets before any development, ensure auto_switch tracks API changes under the OAuth service account, complete on done, and export for promotion. Mandatory for all change-producing work. version: 1.0.0 tools: - snow_update_set_manage (action='create') - snow_update_set_query (action='current') - snow_update_set_manage (action='switch') - snow_update_set_manage (action='complete') - snow_ensure_active_update_set --- # Update Set Workflow for ServiceNow Update Sets are MANDATORY for tracking changes in ServiceNow development. Without an Update Set, changes are not tracked and cannot be deployed to other instances. This is also enforced: configuration writes are blocked at the tool layer while no update set is active for the session. When you hit that block, ask the user whether to capture the work in a named update set, then call `snow_ensure_active_update_set({ name })` once and retry. Only if the user explicitly declines tracking, re-issue the call once with `__skipUpdateSet: true` — the choice is remembered for the rest of the session. ## Before ANY Development ALWAYS create or ensure an Update Set is active before making changes: ```javascript // Step 1: Check current Update Set var current = await snow_update_set_query({ action: "current" }) // Step 2: If no Update Set or using Default, create one if (!current || current.name === "Default") { await snow_update_set_manage({ action: "create", name: "Feature: [Descriptive Name]", description: "What and why this change is being made", }) } // Step 3: Now safe to make changes // All changes will be tracked! // Step 4: When done, complete the Update Set await snow_update_set_manage({ action: "complete", update_set_id: current.sys_id, }) ``` ## Update Set Naming Conventions | Type | Format | Example | | ----------- | --------------------- | ------------------------------------ | | Feature | `Feature: [Name]` | `Feature: Incident Auto-Assignment` | | Bug Fix | `Fix: [Issue]` | `Fix: Approval Email Not Sending` | | Enhancement | `Enhancement: [Name]` | `Enhancement: Dashboard Performance` | | Hotfix | `Hotfix: [Issue]` | `Hotfix: Critical Login Bug` | ## Update Set Lifecycle 1. **In Progress** - Active, receiving changes 2. **Complete** - Ready for export/promotion 3. **Ignore** - Changes won't be promoted (use for experiments) ## What Gets Tracked Update Sets automatically capture changes to: - Tables and columns - Business Rules - Script Includes - Client Scripts - UI Policies and Actions - Workflows and Flow Designer flows - Service Portal widgets and pages - ACLs and Security Rules - System Properties - Scheduled Jobs - And more... ## What Does NOT Get Tracked - Data records (use Import Sets for data) - Attachments on records - User session information - Some system tables (sys_user, etc.) ## MCP Tools for Update Sets ```javascript // Create new Update Set snow_update_set_manage({ action: "create", name: "Feature: My Feature", description: "Description of changes", }) // Switch to existing Update Set snow_update_set_manage({ action: "switch", update_set_id: "sys_id_here", }) // Get current Update Set snow_update_set_query({ action: "current" }) // Complete Update Set snow_update_set_manage({ action: "complete", update_set_id: "sys_id_here", }) // Export Update Set as XML snow_update_set_manage({ action: "export", update_set_id: "sys_id_here", }) ``` ## Best Practices 1. **One feature per Update Set** - Don't mix unrelated changes 2. **Descriptive names** - Make it clear what the Update Set contains 3. **Complete when done** - Don't leave Update Sets open indefinitely 4. **Test before completing** - Verify all changes work correctly 5. **Never use Default** - Always create a named Update Set ## OAuth Context & Update Set Tracking **Serac uses OAuth service account authentication.** All API calls run as an OAuth **service account**, not as your UI user. Update Sets must be "current" for the user making the changes — for API changes that means current for the service account. ### The Two Contexts ``` ┌─────────────────────────────────────────────────────────────┐ │ YOUR UI SESSION (when you log in to ServiceNow UI) │ │ User: john.doe │ │ Current Update Set: [Whatever you selected in the UI] │ └─────────────────────────────────────────────────────────────┘ ┌─────────────────────────────────────────────────────────────┐ │ SERAC OAUTH SESSION (API calls) │ │ User: oauth.service.account │ │ Current Update Set: [Set via Update Set tools] │ │ ← All Serac changes are tracked here │ └─────────────────────────────────────────────────────────────┘ ``` ### auto_switch — REQUIRED for tracking - **`auto_switch=true` (DEFAULT)** — Update Set is set as current for the service account, all changes ARE tracked ✅ - **`auto_switch=false`** — Changes will NOT be tracked. Only use for queries/analysis, NEVER for development. ### Key points - ✅ **Update Sets ARE created** — they exist in ServiceNow - ✅ **Changes ARE tracked** when `auto_switch=true` — all Serac artifacts go into the Update Set automatically - ❌ **NOT visible in YOUR UI session** unless you provide the `servicenow_username` parameter (which also makes it current for that UI user) - ✅ **Deployment still works** — the Update Set can be exported/imported normally - ⚠️ Don't disable `auto_switch` for development tasks ### When to use `servicenow_username` Optional. Pass your ServiceNow username when you want the Update Set to also appear as current in your UI session — handy when you're working in the ServiceNow UI alongside Serac and want to see the same Update Set selected in both places. It does not affect tracking; tracking is governed by `auto_switch`. --- Source attribution: groeimetai Original project: https://github.com/groeimetai/snow-flow/blob/af3ad2b3c01305526a44b2647415ba794237462c/packages/skills/update-set-workflow/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 Serac Labs Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: groeimetai Original project: https://github.com/groeimetai/snow-flow/blob/af3ad2b3c01305526a44b2647415ba794237462c/packages/skills/update-set-workflow/SKILL.md Attribution basis: Source repository record Fields of work: Sales, Development & Engineering, Product Management Roles: Sales Development Rep (SDR), Backend Developer, Product Manager Specialties: Frontend, Design, API, Testing, DevOps Tools: Snow_Update_Set_Create, Snow_Update_Set_Current, Snow_Update_Set_Switch, Snow_Update_Set_Complete, Snow_Ensure_Active_Update_Set Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 6c235bc8eff7e4376d569d3fd2a4ba38fd305d86f47b9a8d4ddf91ff420ef0ac