From 045c2fe6990490540adebd9615eacad0e0654460 Mon Sep 17 00:00:00 2001
From: Joel Enriquez <76045284+jlenriquez-os@users.noreply.github.com>
Date: Thu, 10 Apr 2025 16:03:34 +0900
Subject: [PATCH] Update side-effects-breaking-changes.md

Changed the "ServiceCenter" module to "(System)" module.
---
 src/release-articles/11/side-effects-breaking-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/release-articles/11/side-effects-breaking-changes.md b/src/release-articles/11/side-effects-breaking-changes.md
index a670ce9e..080fd8a0 100644
--- a/src/release-articles/11/side-effects-breaking-changes.md
+++ b/src/release-articles/11/side-effects-breaking-changes.md
@@ -26,7 +26,7 @@ As such, before introducing a breaking change for a new release, OutSystems care
 
 **Rationale**: During a solution publish, Logical Database configurations were fetched by ExtensionID at a deployment stage where that value could be `NULL`, causing configurations to not be set correctly.
 
-**Fix**: Updated the `Async_Operation_LogicalDatabase` entity to include the SS_Key attribute, and updated the solution publish process to use it to fetch the Logical Database configuration. It is advised that customers who have referenced `Async_Operation_LogicalDatabase` in a module must refresh their module's dependency on the ServiceCenter module.
+**Fix**: Updated the `Async_Operation_LogicalDatabase` entity to include the SS_Key attribute, and updated the solution publish process to use it to fetch the Logical Database configuration. It is advised that customers who have referenced `Async_Operation_LogicalDatabase` in a module must refresh their module's dependency on the (System) module.
 
 ### Introduced in Platform Server 11.33.0