Search: "remove flow"

Remove flows from Create

We’ll walk you through how to remove flows, what to consider before doing so, and how to ensure a smooth process.

Remove flows from Create == In this microlearning, we will focus on how to remove flows from Create and what things to consider before you remove your flows from Create.

Event Streaming, API Gateway or Messaging) * Whether the integration is synchronous or asynchronous All in all, there are various reasons why you might consider to remove flows from Create. To remove flows from Create you navigate to the Create phase and press on the button located at the left-hand bottom of the screen called Add integrations.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-adding-flows-to-create--add-integrations-button.png]] Selecting this option leads you to an overview where you can add (and remove) flows to and from Create. [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-adding-flows-to-create--add-integrations-overview.png]] In this overview, all integrations that have already been transferred to Create are indicated as a blue cube with a checkmark in the middle [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-adding-flows-to-create--added-integrations.png]] All integrations that have **not** been transferred to Create yet (or have been removed from Create but not yet from Design) are identifiable as a white cube with a green border [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-adding-flows-to-create--not-yet-added-integrations.png]] When you want to add a flow to Create simply click on the cube linked to the integration you want to add and eMagiz will change it to a green cube with a + icon and will tell you what you want to add.

Key takeaways == * Adding (and removing) flows can be done via a visual overview showing you the current status * eMagiz will tell you what you want to add (or remove) so you can check before you action * Removing means removing (so no turning back) == 5. Suggested Additional Readings == * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] ** [[Flow Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Flow Management.WebHome||target="blank"]] *** [[Remove flows from Create (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Flow Management.novice-flow-management-remove-flows-from-create||target="blank"]] * [[Flows (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

Suggested Additional Readings == * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] ** [[Flow Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Flow Management.WebHome||target="blank"]] *** [[Remove flows from Create (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Flow Management.novice-flow-management-remove-flows-from-create||target="blank"]] * [[Remove Flow (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

. === 3.1 Best practices === * Remove flows as part of completing your production deployment (after a grace period in which you confirm that everything works as expected).

One could deviate from this standard if they have discussed this with the business owner. * Remove flows only after written approval of the business owner of the process * Remove flows from back to front.

{{video attachment="novice-flow-management-remove-flows-from-create.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}}{{/container}}

Next to that, the removed flow may cause a different design decision towards the location of the system. == 3.