You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A `flow` or a `design flow` can be defined as a series or set of artboards starting from one artboard (called a home artboard), which are connected to other artboards or screens via wires or interactions.
178
+
179
+
| Property | Type | Description |
180
+
| --- | --- | --- |
181
+
| name | string | User gesture or other event which will trigger the action. |
182
+
| homeArtboard |\| Artboard from which a particular flow or a prototype experience begins |
183
+
| url | string | URL is the latest published link associated with a particular flow and can be `null` in case no link is published for that flow |
184
+
185
+
NOTE: All `url` returned via {@link interactions#flows} are related to published flows and are usually a subset of the URLs returned via {@link cloud#getSharedArtifacts}. However, the reverse may or may not always hold true.
172
186
173
187
* * *
174
188
@@ -187,6 +201,20 @@ In case there are multiple interactive prototype experiences (flows), implying m
Returns a collection of information on *all* flows across the entire document.
210
+
211
+
**Since**: XD 33
212
+
213
+
A document can have zero or multiple (one or more than one) flows and can therefore have zero or multiple home artboards. Each entry in the return array represents a `FlowInfo` object.
214
+
215
+
**Kind**: static property of [<code>interactions</code>](#FlowInfo)
0 commit comments