Promote flows to deploy

{{container}}{{container layoutStyle="columns"}}(((

A crucial part of proper release management is a clear distinction between what is (perceived to be) finished and what is still under development.

3

To help you in making that decision, eMagiz gives you the possibility to temporarily save your work, and when you (think you) are finished creating a definitive version that will be promoted to Deploy

4

5

In this microlearning, we will zoom in on this process to educate you on how you can and should use this functionality.

6

7

Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].

8

9

== 1. Prerequisites ==

10

11

* Basic knowledge of the eMagiz platform

12

13

== 2. Key concepts ==

14

15

This microlearning focuses on promoting flows to deploy.

16

17

With promoting to deploy we mean: Saving a definitive version of a flow that is (perceived to be) finished by the developer for the flow to become available under Releases

18

19

== 3. Promote flows to deploy ==

20

21

A crucial part of proper release management is a clear distinction between what is (perceived to be) finished and what is still under development.

22

To help you in making that decision, eMagiz gives you the possibility to temporarily save your work, and when you (think you) are finished creating a definitive version that will be promoted to Deploy

23

24

When you are in the Start Editing Mode you will have to press Stop Editing at some point in time. When you press Stop Editing in the flow you will be presented with the following pop-up

25

26

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--create-new-version-pop-up.png]]

27

28

At this point, you have to make a choice. If you are satisfied with your work you press Save and create a new version.

29

If you are unsure of your work or simply need to stop because there is no more time left go for the option Save and continue

30

31

=== 3.1 Save and create a new version ===

32

33

When you go for the option Save and create a new version you will see the following pop-up

34

35

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--save-and-create-new-version-pop-up.png]]

36

37

Choose whether this was a major, minor, or patch upgrade and give a description of the version that tells you and others what you have changed. Something like this

38

39

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--save-and-create-new-version-pop-up-filled-in.png]]

40

41

Press the button Create version and eMagiz will automatically promote this flow version to Deploy where you can use it as part of your Release (more on releases later in this course).

42

43

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--pop-up-successfully-promoted-to-deploy.png]]

44

45

=== 3.2 Save and continue ===

46

47

When you are not sure that the version you are currently working on is ready for Deploy you can select the other option called Save and continue.

48

When choosing this option eMagiz will automatically create a temporary version of your flow in its current state.

49

You can view who made what (temporary) version when you navigate to the History tab of your flow.

50

51

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--history-of-flow.png]]

52

53

This history of the changes in the flow is not only useful for auditing purposes but also helps you identify who you should ask about the latest changes.

54

As you can see the default description of an autosaved version is Autosaved version. You can give such a version a more descriptive name by selecting it and pressing Edit.

55

56

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--edit-description-auto-saved-version.png]]

57

58

That action will lead you to the following pop-up. In this pop-up, you can change the description of the autosaved version to something that makes clear what you did.

59

60

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--edit-description-auto-saved-version-pop-up.png]]

61

62

Simply press Save when you are done and the description will be changed

63

64

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--edit-description-auto-saved-version-result.png]]

65

66

Furthermore, to make it clear to yourself and others the version of the flow will get an asterisk as a suffix the next time you open the flow

67

68

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--save-and-continue-version-asterisk.png]]

69

70

=== 3.3 Initial promotion ===

71

72

In many cases, there is a link between several flows (i.e. entry and onramp, entry and exit gate, infra, and all other flows). These flows we call the associated flows.

73

The moment you try to promote one of these flows without all others eMagiz will tell you that for an initial promotion you will look for these associated flows

74

and create a new version for them as well for eMagiz to promote them all at once when you press Save and create a new version on the last one of the flows that are associated with each other.

75

76

To indicate to you that such an action is required eMagiz will present you the following pop-up:

77

78

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-promote-flows-to-deploy--create-version-associated-flows.png]]

79

80

== 4. Key takeaways ==

81

82

* In Create you can choose between the options: