Changes for page Flow Editor - Components

Last modified by Carlijn Kokkeler on 2024/02/27 15:32
From version 12.1
edited by Carlijn Kokkeler
on 2024/02/27 11:30
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2024/02/27 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -132,7 +132,7 @@
132 132  
133 133  As most of the use cases for incorporating a router component on flow level without eMagiz generating it for you lie within messaging we won't go into detail in the exact mechanics of each of these router options.
134 134  
135 -=== 3.7 Support ===
135 +=== 3.7 Service activators ===
136 136  
137 137  In eMagiz, support objects can be linked to a functional component to aid the working of that component. These components are identifiable through the grey color of the components
138 138  
... ... @@ -140,8 +140,16 @@
140 140  
141 141  We will discuss the support components in more detail in a later microlearning.
142 142  
143 -=== 3.8 Channel ===
143 +=== 3.8 Support ===
144 144  
145 +In eMagiz, support objects can be linked to a functional component to aid the working of that component. These components are identifiable through the grey color of the components
146 +
147 +[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--support-components.png]]
148 +
149 +We will discuss the support components in more detail in a later microlearning.
150 +
151 +=== 3.9 Channel ===
152 +
145 145  To connect all these components (except for the support objects) we need channels. A channel makes sure that the output of component A is sent to component B for further processing.
146 146  
147 147  [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--channel-components.png]]
... ... @@ -148,7 +148,7 @@
148 148  
149 149  Each channel should be given a descriptive name so you and others you work with know what the channel is used for.
150 150  
151 -=== 3.9 Annotation ===
159 +=== 3.10 Annotation ===
152 152  
153 153  eMagiz also offers you the option to add an annotation and link it to one or more components.
154 154  This way you can make it explicit for yourself and others what is exactly happening in those components and why you have opted for a certain option.
... ... @@ -155,7 +155,7 @@
155 155  
156 156  [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--annotation-components.png]]
157 157  
158 -=== 3.10 The Combination ===
166 +=== 3.11 The Combination ===
159 159  
160 160  Combining this all together results in a flow with at least an input and output component helped by several support objects. An example of what a working flow looks like is:
161 161