Introduction 

SAP Cloud Integration version 5.75/7.40, 6.67/ (8.x→ 8.31), one of the capabilities of SAP Integration Suite, comes with a feature which will allow you to update the version of an integration flow component.  To know more, you can refer the help documentation.

In this blog, I will cover the detailed aspects of this feature, which pain, problem it will address and how to leverage this feature to improve the developer productivity and efficiency. 

But before that lets try to understand the need for the versioning of the components.

In SAP Cloud Integration, new version is created when a component, which is already shipped and is being used by the customers undergoes some changes, enhancements, improvements. New features are offered in this component via the minor version updates and small fixes like label changes or UI alignments are offered via micro version updates. To know the versioning of the components in detail, refer the “Versioning of Components” section from this blog post.

Problem 

Manual update of component version is inefficient. Integration Developers face significant challenges when updating the version of the components manually.

Integration Developer​

Manual update of the component is a multi-step process as described below:

Manual component deletion​ – Manual update involves deleting component (Flow steps, Adapters etc.). Recreation of component – After deletion, integration developer must recreate component manually, and maintain their configurations, including properties and externalized parameters.

These manual steps are Effort-Intensive, and the process is time-consuming, cumbersome and error prone.

Solution

Enabled one-click update version feature to update the component which is backward compatible to the latest available version without any loss of the existing properties, configurations, externalized parameters etc. In past we had enabled this feature for the Integration flow configuration, process pool elements, however in this release, the framework is extended to enable the feature to update the flow steps, adapters which are the widely used components in the modeling of integration flow artifact.

This feature is available across all the environments of the Cloud Integration such as NEO, CF and Edge Integration Cell. Feature applicability – Flow steps and Adapters.

To know more about Runtime Profile, refer this help documentation and blog post.

How it works?

A dedicated “Update Version” will be available if the component version is older than the latest available version corresponding to the runtime profile (e.g. SAP Cloud Integration, Edge Integration Cell etc.). Backward-compatible components will be migrated to the latest version seamlessly. When you update the version, existing fields will be retained with the same values, and new fields will be populated with default values. If a default value is not present for a mandatory field, you must add the value, and new fields will be populated with default values. If a default value is not present for a mandatory field, you must add the value.

Flow step – Content modifier version 1.5 is selected for the update. Image: 1

Update Version feature updates the Content Modifier from 1.5 to 1.6 (latest version) as it contains the backward compatible changes.

Image: 2

Content Modifier flow step is updated to the latest version and now the Update Version feature is not available as the component is on the latest version.

Image: 3

If the components are not backward compatible, they will not be updated rather the feature will educate Integration Developer to delete and recreate the components by maintaining the configurations manually. See the below example.

Generate Splitter flow step cannot be updated from 1.5 to 1.6 as it contains incompatible changes. 

Image: 4

Integration Developer will be asked to delete and recreate the component manually.Image: 5

Note: You can update one only component (Flow step, Adapter, Process) at a time. Selecting an integration process focuses the update exclusively on that process.

Benefits

Eliminates manual recreation of flow steps ​.Saves time & reduces effort​.Minimize errors​.Keep components latest.Improve developer efficiency and productivity​.

This enhancement is designed to make integration process development easier by enabling the integration developers to access the latest features through seamless updates of integration flow adapters and flow steps.

Next steps

Show “Change” summary in the Update Version UI.​Update “Process” component and its child elements.

Hope you will be benefited with this feature. Please experience the Update Version and provide your valuable feedback.

​ Introduction SAP Cloud Integration version 5.75/7.40, 6.67/ (8.x→ 8.31), one of the capabilities of SAP Integration Suite, comes with a feature which will allow you to update the version of an integration flow component.  To know more, you can refer the help documentation.In this blog, I will cover the detailed aspects of this feature, which pain, problem it will address and how to leverage this feature to improve the developer productivity and efficiency. But before that lets try to understand the need for the versioning of the components.In SAP Cloud Integration, new version is created when a component, which is already shipped and is being used by the customers undergoes some changes, enhancements, improvements. New features are offered in this component via the minor version updates and small fixes like label changes or UI alignments are offered via micro version updates. To know the versioning of the components in detail, refer the “Versioning of Components” section from this blog post.Problem Manual update of component version is inefficient. Integration Developers face significant challenges when updating the version of the components manually.Integration Developer​Manual update of the component is a multi-step process as described below:Manual component deletion​ – Manual update involves deleting component (Flow steps, Adapters etc.). Recreation of component – After deletion, integration developer must recreate component manually, and maintain their configurations, including properties and externalized parameters.These manual steps are Effort-Intensive, and the process is time-consuming, cumbersome and error prone.SolutionEnabled one-click update version feature to update the component which is backward compatible to the latest available version without any loss of the existing properties, configurations, externalized parameters etc. In past we had enabled this feature for the Integration flow configuration, process pool elements, however in this release, the framework is extended to enable the feature to update the flow steps, adapters which are the widely used components in the modeling of integration flow artifact.This feature is available across all the environments of the Cloud Integration such as NEO, CF and Edge Integration Cell. Feature applicability – Flow steps and Adapters.To know more about Runtime Profile, refer this help documentation and blog post.How it works?A dedicated “Update Version” will be available if the component version is older than the latest available version corresponding to the runtime profile (e.g. SAP Cloud Integration, Edge Integration Cell etc.). Backward-compatible components will be migrated to the latest version seamlessly. When you update the version, existing fields will be retained with the same values, and new fields will be populated with default values. If a default value is not present for a mandatory field, you must add the value, and new fields will be populated with default values. If a default value is not present for a mandatory field, you must add the value.Flow step – Content modifier version 1.5 is selected for the update. Image: 1Update Version feature updates the Content Modifier from 1.5 to 1.6 (latest version) as it contains the backward compatible changes.Image: 2Content Modifier flow step is updated to the latest version and now the Update Version feature is not available as the component is on the latest version.Image: 3If the components are not backward compatible, they will not be updated rather the feature will educate Integration Developer to delete and recreate the components by maintaining the configurations manually. See the below example.Generate Splitter flow step cannot be updated from 1.5 to 1.6 as it contains incompatible changes. Image: 4Integration Developer will be asked to delete and recreate the component manually.Image: 5Note: You can update one only component (Flow step, Adapter, Process) at a time. Selecting an integration process focuses the update exclusively on that process.Benefits Eliminates manual recreation of flow steps ​.Saves time & reduces effort​.Minimize errors​.Keep components latest.Improve developer efficiency and productivity​.This enhancement is designed to make integration process development easier by enabling the integration developers to access the latest features through seamless updates of integration flow adapters and flow steps.Next steps Show “Change” summary in the Update Version UI.​Update “Process” component and its child elements. Hope you will be benefited with this feature. Please experience the Update Version and provide your valuable feedback.   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog