Changes for page Remove flows from Create

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -28,7 +28,7 @@
28	28
29	29	As you can imagine there is a need to be able to remove flows from Create after they have previously build. The main reason would be that the system that was once connected to your integration landscape is no longer used or has become out dated. As part of the lifecycle management of your integration landscape we advice to remove those integrations from the Create phase. This functionality helps you with that. Do note that removing a flow from Create is a prerequisite of removing the integration (line) in Capture and Design. So to do proper lifecycle management you start at Manage and work your way back to Capture to correctly and completely remove the solution from your integration landscape.
30	30
31		-{{warning}}Note that to remove a flow from Create that has been deployed before you first need to remove the flow from all Releases in Deploy before you can remove the flow in question.{{/warning}}
	31	+{{warning}}Note that to remove a flow from Create that has been deployed before you first need to remove the flow from **all** Releases in Deploy before you can remove the flow in question.{{/warning}}
32	32
33	33	Another potential use case for this functionality is when you have made a mistake in Design or Capture with regards to directionality or naming. In those cases you can also remove the flows from Create and re-add it on a later moment in time when those aspects are configured properly. Do note that not all configuration changes in Design or Capture need to be preceeded by removing the flows from Create. In general most of what is in Design and Capture can be changed after an integration has been moved to Create. The exceptions to this rule are:
34	34