added affected components

Author: cortex-lp

content/en/blog/releases/2025.X/2025.5.md

@@ -164,6 +164,26 @@ For example:
 }
 ```
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+* [{{% ctx %}} Innovation Core Application][]
+  * [{{% ctx %}} API Gateway Service][]
+  * [{{% ctx %}} Authorisation Service][]
+  * [{{% ctx %}} Concurrency Management Service][]
+  * [{{% ctx %}} Configuration Management Service][]
+  * [{{% ctx %}} Data Storage Service][]
+  * [{{% ctx %}} Execution Management Service][]
+  * [{{% ctx %}} Licence Management Service][]
+  * [{{% ctx %}} Listeners Service][]
+  * [{{% ctx %}} Monitoring Service][]
+  * [{{% ctx %}} Package Management Service][]
+  * [{{% ctx %}} Provisioning Service][]
+  * [{{% ctx %}} Scheduling Service][]
+  * [{{% ctx %}} Triggers Service][]
+* [{{% ctx %}} Innovation Execution Application][]
+  * [{{% ctx %}} Execution Service][]
+
 <!-- 	Cortex\2025 Q2 S4	 - 	PBI	 - 	34902	 - 	Flow Engine - Expose Tenant, System, PackageName, PackageVersion, FlowName, ExecutionId on _executionContext	 -->
 <!-- ***Add node name -->
 
@@ -172,6 +192,10 @@ For example:
 The {{% ctx %}} Interaction Portal now supports the use of separate credentials for querying Active Directory Groups. This may be used when the user provided for running PowerShell does not have permission to query the AD Groups.  
 Currently, there is no documentation available on how to do this. For further assistance, please raise a case in the [{{% ctx %}} Service Portal][].
 
+Affected Components:
+
+* [{{% ctx %}} Interaction Portal][Interaction Portal]
+
 <!-- 	Cortex\2025 Q2 S6	 - 	PBI	 - 	35059	 - 	CORTEX Interaction Portal - Apply changes from Configuration Portal core flows	 -->
 
 #### Observability
@@ -180,6 +204,21 @@ Currently, there is no documentation available on how to do this. For further as
 
 The executions data used by the Running Executions tile on the [Operations Overview][] page and [Running Executions][] grid on the [Packages][] page has been extended to include child executions; previously only the root executions were included.
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+* [{{% ctx %}} Innovation Core Application][]
+  * [{{% ctx %}} API Gateway Service][]
+  * [{{% ctx %}} Concurrency Management Service][]
+  * [{{% ctx %}} Execution Management Service][]
+  * [{{% ctx %}} Monitoring Service][]
+  * [{{% ctx %}} Package Management Service][]
+  * [{{% ctx %}} Provisioning Service][]
+  * [{{% ctx %}} Scheduling Service][]
+  * [{{% ctx %}} Triggers Service][]
+* [{{% ctx %}} Innovation Execution Application][]
+  * [{{% ctx %}} Execution Service][]
+
 <!-- 	Cortex\2025 Q2 S4	 - 	PBI	 - 	34658	 - 	CORTEX Gateway - Display all executions in Packages->Package Definitions grid, Packages->Package Version Editor->Running Executions grid and Operations Overview->Running Executions tile	 -->
 
 ##### New columns added to the Running Executions grid on the Packages page
@@ -191,6 +230,26 @@ The [Running Executions][] grid on the [Packages][] page has had the following c
 * `Root Execution Id`: The unique identifier for the root execution; all related executions will have the same Root Execution Id.
 * `Executing On`: Where the execution is running, in the following format `<node-name> (<ipaddress-or-fqdn>)`.
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+* [{{% ctx %}} Innovation Core Application][]
+  * [{{% ctx %}} API Gateway Service][]
+  * [{{% ctx %}} Authorisation Service][]
+  * [{{% ctx %}} Concurrency Management Service][]
+  * [{{% ctx %}} Configuration Management Service][]
+  * [{{% ctx %}} Data Storage Service][]
+  * [{{% ctx %}} Execution Management Service][]
+  * [{{% ctx %}} Licence Management Service][]
+  * [{{% ctx %}} Listeners Service][]
+  * [{{% ctx %}} Monitoring Service][]
+  * [{{% ctx %}} Package Management Service][]
+  * [{{% ctx %}} Provisioning Service][]
+  * [{{% ctx %}} Scheduling Service][]
+  * [{{% ctx %}} Triggers Service][]
+* [{{% ctx %}} Innovation Execution Application][]
+  * [{{% ctx %}} Execution Service][]
+
 <!-- 	Cortex\2025 Q2 S6	 - 	PBI	 - 	35284	 - 	CORTEX Gateway - Running Executions - Add column for root execution ID	 -->
 <!-- 	Cortex\2025 Q2 S6	 - 	PBI	 - 	35518	 - 	CORTEX Gateway - Running Executions - Add node name as column and property on _executionContext	 -->
 
@@ -210,6 +269,27 @@ To disable the Code Analyser, or to update the Allowed list, please refer to the
 | [Single Node][Disable Code Analyser - Single Node] | [Single Node][Update Allowed list - Single Node] |
 | [Multi Nodes][Disable Code Analyser - Multi Node]  | [Multi Nodes][Update Allowed list - Multi Node]  |
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+* [{{% ctx %}} Block Packages][Blocks]
+* [{{% ctx %}} Innovation Core Application][]
+  * [{{% ctx %}} API Gateway Service][]
+  * [{{% ctx %}} Authorisation Service][]
+  * [{{% ctx %}} Concurrency Management Service][]
+  * [{{% ctx %}} Configuration Management Service][]
+  * [{{% ctx %}} Data Storage Service][]
+  * [{{% ctx %}} Execution Management Service][]
+  * [{{% ctx %}} Licence Management Service][]
+  * [{{% ctx %}} Listeners Service][]
+  * [{{% ctx %}} Monitoring Service][]
+  * [{{% ctx %}} Package Management Service][]
+  * [{{% ctx %}} Provisioning Service][]
+  * [{{% ctx %}} Scheduling Service][]
+  * [{{% ctx %}} Triggers Service][]
+* [{{% ctx %}} Innovation Execution Application][]
+  * [{{% ctx %}} Execution Service][]
+
 <!-- 	Cortex\2025 Q2 S4	 - 	PBI	 - 	34450	 - 	Flows Engine - Add analyser to disallow use of windows.intPointer 0	 -->
 <!-- 	Cortex\2025 Q2 S4	 - 	PBI	 - 	34979	 - 	Flows Engine - Whitelist Analyser - Required Types/Namespaces and Allowed Types/Namespaces	 -->
 <!-- Code analyser not Whitelist analyser -->
@@ -218,6 +298,11 @@ To disable the Code Analyser, or to update the Allowed list, please refer to the
 
 Erlang has been updated to version `26.2.5.12` to address recently identified vulnerabilities.
 
+Affected Components:
+
+* {{% ctx %}} App Server Install Scripts
+* {{% ctx %}} Upgrade Scripts
+
 <!-- 	Cortex\2025 Q2 S6	 - 	PBI	 - 	35439	 - 	Installation/Upgrade - Elrang vulnerability - Erlang version 26.2.5.12	 -->
 
 ##### General security enhancements on {{% ctx %}} Gateway
@@ -228,6 +313,10 @@ Erlang has been updated to version `26.2.5.12` to address recently identified vu
 * Permissions-Policy header
 * Content-Security-Policy header including removing unrecognised `navigate-to` directive
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+
 <!-- 	Cortex\2025 Q2 S3	 - 	PBI	 - 	34781	 - 	Security - Review and update Permissions-Policy - Gateway	 -->
 <!-- 	Cortex\2025 Q2 S3	 - 	PBI	 - 	34734	 - 	Security - Run 3rd Party security checks For Gateway and verify that settings are up to date	 -->
 <!-- 	Cortex\2025 Q2 S3	 - 	PBI	 - 	34448	 - 	Security - Unrecognized Content-Security-Policy directive 'navigate-to'	 -->
@@ -238,6 +327,13 @@ Erlang has been updated to version `26.2.5.12` to address recently identified vu
 
 The icons for the [Decision Blocks][] have been updated to differentiate them from each other, and make it clearer what the flow is doing.
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+* [{{% ctx %}} Block Packages][Blocks]
+* [{{% ctx %}} Innovation Execution Application][]
+  * [{{% ctx %}} Execution Service][]
+
 <!-- 	Cortex\2025 Q2 S4	 - 	PBI	 - 	34660	 - 	CORTEX Blocks - Decision Blocks - Icons easier to identify	 -->
 
 #### Installation
@@ -246,6 +342,12 @@ The icons for the [Decision Blocks][] have been updated to differentiate them fr
 
 The certificate update script for High Availability (HA) installations has been improved to ensure that the certificate used by RabbitMQ is updated one node at a time, to prevent any downtime during the update process.
 
+Affected Components:
+
+* {{% ctx %}} Upgrade Scripts
+
+<!-- TODO: discuss with PO to put to upgrade -->
+
 <!-- 	Cortex\2025 Q2 S2	 - 	PBI	 - 	20328	 - 	Installation - Certificate update is not HA	 -->
 
 #### Upgrade
@@ -254,6 +356,16 @@ The certificate update script for High Availability (HA) installations has been
 
 The {{% ctx %}} Gateway upgrade now stops and starts the AppPool associated with the web application rather than performing an `iisreset`. This is to prevent any downtime for other web applications running under IIS on the same server.
 
+Affected Components:
+
+* {{% ctx %}} App Server Install Scripts
+  * {{% ctx %}} App Server Backup
+  * {{% ctx %}} App Server Recovery
+* {{% ctx %}} Web App Server Install Scripts
+  * {{% ctx %}} Web App Server Backup
+  * {{% ctx %}} Web App Server Recovery
+* {{% ctx %}} Upgrade Scripts
+
 <!-- 	Cortex\2025 Q2 S3	 - 	PBI	 - 	34540	 - 	Upgrade - IISReset needs to be more specific for dual sites	 -->
 
 #### Documentation
@@ -336,6 +448,10 @@ Disaster Recovery Guides have been added to the {{% ctx %}} Product Portal to he
 
 A bug has been fixed that caused the {{% ctx %}} Gateway to stop working when the `Blocks.json` file was corrupted. Gateway now has a fallback mechanism to restore the `Blocks.json` file from a backup if it is corrupted, allowing the Gateway to continue working.
 
+Affected Components:
+
+* [{{% ctx %}} Gateway][Gateway]
+
 <!-- 	Cortex\2025 Q2 S6	 - 	BUG	 - 	35549	 - 	CORTEX Gateway - Blocks.JSON corruption causes gateway to stop working - merge from 2025.3 to main	 -->
 
 #### Scalability
@@ -357,6 +473,16 @@ The new folder structure is as follows:
   * `CORTEX Backups\Web Application Server\Applications\Configuration`
   * `CORTEX Backups\Web Application Server\Applications\Reliable Collections`
 
+Affected Components:
+
+* {{% ctx %}} App Server Install Scripts
+  * {{% ctx %}} App Server Backup
+  * {{% ctx %}} App Server Recovery
+* {{% ctx %}} Web App Server Install Scripts
+  * {{% ctx %}} Web App Server Backup
+  * {{% ctx %}} Web App Server Recovery
+* {{% ctx %}} Upgrade Scripts
+
 <!-- 	Cortex\2025 Q2 S3	 - 	PBI	 - 	34775	 - 	Disaster Recovery - Seperate backup path for app server and flow debugger	 -->
 
 #### Installation