Instructions : How to Deploy an Update Set to a Production InstanceSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article describes how to deploy a packaged batch update set from a sub-production instance to a production instance using the Now Assist for Setup framework. The framework automatically captures all configuration changes made during application setup into a batch update set. Once all configurations have been completed and verified on the sub-production instance, the batch update set can be packaged, downloaded as an XML file, and deployed to the production instance. Prerequisites Before proceeding, confirm that the following conditions have been met: All preset and manual configurations have been completed and verified on the sub-production instance. The batch update set has been packaged on the sub-production instance and the XML file has been downloaded. The production instance version is compatible with the sub-production instance from which the update set was exported. Procedure Part A — Package and Download the Batch Update Set (Sub-production) Navigate to the product configuration page on the sub-production instance. Ensure that all default configurations and manual configurations have been applied before proceeding. Select Package and Download. A confirmation modal will be displayed. Select Package to finalize recording and consolidate all configuration changes into the batch update set. Select Download XML. The downloaded file is an XML file containing all records from the batch update set and its associated child update sets. Retain this file on the local machine for upload to the production instance. Part B — Upload and Deploy the Update Set (Production) Log in to the production instance. Navigate to the Product Hub page. Select “Upload batch” update set. A file selection dialog will be presented. Select the batch update set XML file that was downloaded from the sub-production instance. Allow the system to complete the pre-flight validation and retrieval process. The system will automatically validate the uploaded file. Upon successful validation, the Retrieve Update Set process will be triggered automatically. If the file fails validation, an error message will be displayed. Refer to the Troubleshooting section of this article. Review the retrieval results presented in the modal dialog. The modal will indicate either a successful retrieval or the presence of preview errors. A guidance video is provided within the modal for reference. Select “Preview.” The Update Set page will open in a new browser tab. Review all configuration changes listed. Resolve any preview errors before proceeding to the commit operation. Select “Commit Update Set Batch”, once all preview errors have been resolved. Upon successful completion, the configurations from the sub-production instance will be active on the production instance. Part C — Complete Instance-Specific Configuration (Production) Following a successful commit, certain configurations that were excluded from the update set must be applied manually on the production instance. The following configuration types are typically excluded from the update set and must be re-configured directly on the production instance: Single Sign-On (SSO) LDAP directory integration Notification templates and settings Troubleshooting File Validation Error If an error is returned immediately upon uploading the XML file, perform the following checks: Confirm that the correct file is being uploaded (the XML file downloaded from the sub-production instance). Verify that the file has not been modified, renamed, or corrupted since it was downloaded. If the issue persists, re-package and re-download the batch update set from the sub-production instance and attempt the upload again. Preview Errors Preview errors indicate conflicts or unresolved dependencies within the update set. Each error must be reviewed and resolved individually on the Update Set preview page before the commit operation can proceed. For each preview problem record, the system presents an Available Actions dropdown. The following resolution options are available: Resolution Option Description When to Use Accept Remote Update Overwrites the existing record on the production instance with the version contained in the update set. Select this option when the incoming configuration from the update set is the correct and intended state of the record, and the local version on production should be replaced. Skip Remote Update Discards the conflicting change from the update set and retains the existing record on the production instance. Select this option when the local version on the production instance is the correct state, or when the incoming change is not applicable to the target environment. Compare with Local Opens a side-by-side comparison view of the incoming update set version against the version currently on the production instance. Use this action prior to selecting Accept or Skip in order to review the specific differences between the two versions and make an informed resolution decision. Note: It is recommended to use the Compare with Local action before selecting Accept Remote Update or Skip Remote Update for any conflict. Accepting a remote update will overwrite the existing production record and cannot be undone through the update set process. If a preview error indicates a missing dependency — for example, a referenced record that does not exist on the production instance — the missing record must be created or imported to the production instance before the update set can be committed successfully. Commit Operation Fails If the commit operation does not complete successfully: The Update Set Page throws an error message saying that the commit has failed, as show in the screen shot below: Carefully review the commit status and any error details presented and navigate back to the Product Hub page. The Product Hub page provides a direct link “See Logs” to the commit logs, with details of the specific reasons for any commit failures as shown in the screenshot below. Examine the commit logs thoroughly and address all identified issues before attempting to upload the update set again. Frequently encountered errors include version mismatches between the sub production and production instances. In such cases, it is essential to confirm that both environments are running compatible versions prior to retrying the commit process. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Now Assist for Setup : GA Release