Service Catalog - Catalog Item Submission ErrorsIssue <!-- /*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: ; } } Issue #1 Issue #2 XML End-Tag Error on Catalog Item Submission Unique Key Violation Error on Order Confirmation Page ISSUE #1 XML End-Tag Error Displayed When Submitting a Catalog Item Component Service Catalog – Catalog Item Submission Affected Areas Service Catalog Application, CMS Affected Release London Release Error Message Element type "td" must be terminated by the matching end-tag "</td>" Description When a user submits a Service Catalog request, the following error is displayed on screen: Element type "td" must be terminated by the matching end-tag "</td>" The issue has been reproduced via the Service Catalog application and via CMS. Cause ⚠ Root Cause The Script Include CatalogLabelEvaluator has been customised, and was therefore skipped during the instance upgrade to the London Release. The customised version contains malformed HTML that triggers the XML parsing error at submission time. Resolution Resolution Steps Navigate to the Script Include CatalogLabelEvaluator in your instance. Revert the Script Include CatalogLabelEvaluator to its Out-of-Box (OOB) version. Re-test the catalog item submission to confirm the error no longer appears. ✅ Expected Outcome After reverting the Script Include to OOB, the XML end-tag error will no longer appear when submitting catalog items via the Service Catalog application or CMS. ISSUE #2 Unique Key Violation Error on Order Confirmation Page Component Service Catalog – Order Confirmation Affected Areas Platform Catalog Item Submission Affected Table sc_request Error Message Unique Key Violation error on the order confirmation page Description When a catalog item is submitted from the platform, a Unique Key Violation error is displayed on the order confirmation page. Notably, the REQ record is created successfully — the error is a side effect of a workflow script activity, not a failed submission. ℹ Important Note The REQ record is created successfully. The Unique Key Violation error is a secondary error triggered by the workflow script — it does not prevent record creation but causes a misleading error to appear on the confirmation page. Cause ⚠ Root Cause The workflow defined on the sc_request table contains a Run Script activity that includes a current.update() statement. This causes a duplicate database write, triggering the Unique Key Violation error. Resolution Resolution Steps Open the workflow defined on the sc_request table. Locate the Run Script activity within the workflow. Remove the current.update() statement from the Run Script activity. Save and publish the updated workflow. Re-test catalog item submission to confirm the Unique Key Violation error no longer appears on the order confirmation page. ✅ Expected Outcome Once current.update() is removed from the Run Script activity, the Unique Key Violation error will no longer appear on the order confirmation page after catalog item submission. 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: ; } } All applicable versions Resolution<!-- /*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: ; } } Please refer under issue column