Update from SAP DITA CMS (squashed):

commit 6f95a084be534b73c36b4175aadd37b824a81f9b
Author: REDACTED
Date:   Mon Jun 17 08:21:42 2024 +0000

    Update from SAP DITA CMS 2024-06-17 08:21:42
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

commit 8e681288b9a6745ac1ecb8240beeb48040f8bb96
Author: REDACTED
Date:   Mon Jun 10 12:57:52 2024 +0000

    Update from SAP DITA CMS 2024-06-10 12:57:52
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

commit 60bfb6e65113c744182ef8c8708144b08b46040e
Author: REDACTED
Date:   Mon Jun 10 12:51:44 2024 +0000

    Update from SAP DITA CMS 2024-06-10 12:51:44
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

##################################################
[Remaining squash message was removed before commit...]

docs/70-interface-migration/additional-references-for-interface-development-6daed01.md

@@ -53,7 +53,7 @@ Interface Development
 </td>
 <td valign="top">
 
-Updated list on new enhancement and guidelines from SAP
+Updated list on new enhancements and guidelines from SAP
 
 </td>
 </tr>
@@ -94,6 +94,23 @@ Integration flows recipes
 <tr>
 <td valign="top">
 
+[Handling Mail Attachments in SAP Process Orchestration and SAP Cloud Integration](https://community.sap.com/t5/technology-blogs-by-sap/handling-mail-attachments-in-sap-process-orchestration-and-sap-cloud/ba-p/13624118?emcs_t=S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExUOTNCNVo1TzNQREZ8MTM2MjQxMTh8U1VCU0NSSVBUSU9OU3xoSw)
+
+</td>
+<td valign="top">
+
+Interface Development
+
+</td>
+<td valign="top">
+
+This blog guides you through the migration of emails and file handling processes from SAP Process Orchestration to Cloud Integration. It emphasizes scenarios like extracting email attachments and transferring files between SFTP and email while preserving original file names and functionalities.
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 [Guidelines to Migrate/Integrate Data Into Cloud from/to On-Premise Systems](https://blogs.sap.com/2019/07/19/explosion-of-sap-cloud-dataintegration-sap-tool-procurement-guidelines-to-migrateintegrate-data-into-cloud-fromto-on-premise-systems/) 
 
 </td>
@@ -144,7 +161,3 @@ Blog about B2B Partner Directory
 </tr>
 </table>
 
-
-
-
-

docs/70-interface-migration/customizing-the-pipeline-concept-aeb106f.md

@@ -0,0 +1,57 @@
+<!-- loioaeb106f049144c71a0b7814a2ffedc3f -->
+
+# Customizing the Pipeline Concept
+
+You can apply the pipeline concept as a template and fit it to your custom needs. For example, implement your own exception handling, or define a different global maximum number of retries.
+
+Depending on your needs, you can customize the identification of scenarios, the status of ProcessDirect flow, and retry handling.
+
+
+
+<a name="loioaeb106f049144c71a0b7814a2ffedc3f__section_dfx_r1f_j1c"/>
+
+## Identifying a Scenario
+
+In SAP Process Orchestration, a scenario is uniquely defined via party, sender component, sender interface, namespace, and virtual receiver. In the pipeline concept, a scenario is identified using only sender component and sender interface. Depending on your specific requirements, you can extend the scenario definition. For example, change the partner ID to fetch the Partner Directory information accordingly.
+
+
+
+<a name="loioaeb106f049144c71a0b7814a2ffedc3f__section_wzs_t1f_j1c"/>
+
+## Status of ProcessDirect Integration Flows
+
+If a scenario-specific integration flow that's called via the ProcessDirect adapter fails, the exception is fetched in an exception subprocess. In this exception subprocess, the custom status is set and the integration flow ends with an error end event. This ensures that the generic integration flow calling the scenario-specific integration flow keeps the message in the inbound queue until it's eventually retried. Furthermore, in the message monitor, the message processing log of the scenario-specific flow turns into status *Failed* with custom status *RetryViaParentFlow*.
+
+If you prefer the scenario-specific integration flow \(or child flow\) to be set to *Completed* instead of *Failed* because the retry is handled by calling the generic integration flow \(or parent flow\) anyway, you can change the child flow's exception subprocess as follows:
+
+1.  Switch the *error end event* with an *end event*.
+
+2.  Set a header such as `error_occured` with value `true`. The header is then passed to the parent flow, showing that an error occurred in the child flow.
+
+3.  In the parent flow, add a router after the request reply step that checks for the `error_occured` value, and, if `true`, raises an exception. Otherwise, the message in the parent flow isn't retried.
+
+
+For a similar scenario, see [Handle Exceptions in Dependent Integration Flows](https://help.sap.com/docs/integration-suite/sap-integration-suite/handle-exceptions-in-dependent-integration-flows).
+
+
+
+<a name="loioaeb106f049144c71a0b7814a2ffedc3f__section_sxr_51f_j1c"/>
+
+## Retry Handling
+
+For errors occurring in message processing, you can define a **scenario-specific maximum number of retries**. By default, if no such value is defined in the Partner Directory for the specific scenario, the number of retries is **unlimited**.
+
+You can change the global setting to any other value by adapting the Groovy script `readRetryHandlingFromPD`. In the following example, the default value is `10`.
+
+> ### Note:  
+> Since the header `SAPJMSRetries` is incremented after the retry, you must increment the `maxJMSRetries` by 1 to achieve 10 retries.
+
+```
+    // read retry handling from the Partner Directory
+    def maxJMSRetries = service.getParameter("MaxJMSRetries", Pid , String.class);
+    
+    // if the value exists in the Partner Directory, create a new header holding the max number of retries incremented by 1
+    // otherwise, set the header to default which is 10
+    message.setHeader("maxJMSRetries", maxJMSRetries ? maxJMSRetries.toInteger() - 1 : '9');
+```
+

docs/70-interface-migration/interface-design-and-implementation-b763478.md

@@ -23,6 +23,11 @@ Migration Tooling, a feature in the Cloud Integration capability, can help you m
 
 -   **[Integration Patterns](integration-patterns-980eace.md "")**  
 
+-   **[Pipeline Concept](pipeline-concept-6e527fb.md "The pipeline concept allows you to set up
+		your asynchronous integration scenarios in Cloud Integration similarly to how messages are
+		processed in SAP Process Integration and SAP Process Orchestration, in
+		pipelines.")**  
+The **pipeline concept** allows you to set up your asynchronous integration scenarios in Cloud Integration similarly to how messages are processed in SAP Process Integration and SAP Process Orchestration, in pipelines.
 -   **[Additional References for Interface Development](additional-references-for-interface-development-6daed01.md "The following table provides additional resources for developing interfaces.")**  
 The following table provides additional resources for developing interfaces.
 

docs/70-interface-migration/interface-migration-0cab9f4.md

@@ -19,10 +19,16 @@ As part of the testing phase in every migration project, several products on the
 		integration. The service interfaces are defined in the Enterprise Services Repository (ESR), which then generates the ABAP objects using the
 		SPROXY transaction on the SAP side.")**  
 When working with ABAP proxies in the context of SAP Process Orchestration, you need to follow certain steps to ensure successful integration. The service interfaces are defined in the Enterprise Services Repository \(ESR\), which then generates the ABAP objects using the SPROXY transaction on the SAP side.
+-   **[Migrating Java Mappings](migrating-java-mappings-468c179.md "Migrate your Java mappings in SAP Process Orchestration to the more efficient Groovy script in Cloud Integration using Groovy script
+		templates.")**  
+Migrate your Java mappings in SAP Process Orchestration to the more efficient Groovy script in Cloud Integration using Groovy script templates.
 -   **[Directory API](directory-api-07096c2.md "The SAP Process Orchestration Directory API is a set of SOAP APIs to read and change objects from the Integration Builder and Integration
 		Directory. ")**  
 The SAP Process Orchestration Directory API is a set of SOAP APIs to read and change objects from the Integration Builder and Integration Directory.
 -   **[Interface Design and Implementation](interface-design-and-implementation-b763478.md "In a migration project, you may need to redesign a particular integration flow or
 		develop one from scratch in an implementation project.")**  
 In a migration project, you may need to redesign a particular integration flow or develop one from scratch in an implementation project.
+-   **[Modernization Recommendations](modernization-recommendations-d337a6f.md "Learn about a set of recommendations aimed at aligning your integration practices with
+		contemporary standards and the integration strategy of SAP.")**  
+Learn about a set of recommendations aimed at aligning your integration practices with contemporary standards and the integration strategy of SAP.