Share artboards between different flows
I often create a series of artboards that I want to use in several flows, or more than once in the same flow.
The "return to previous artboard" functionality is inadequate to allow this to happen.
E.g. A series of artboards that show an image being loaded and edited. I want to transition to this series of artboards in many places throughout my workflow, and once I have progressed through these image editting artboards I want to return to the artboard that I was at before I transitioned. Because I am not returning from the first artboard in the set I cannot use the "return to previous artboard" action.
< Originating Artboard A> -> <Artboard 1> -> <Artboard 2> -> Return to Originating artboard A
< Originating Artboard B> -> <Artboard 1> -> <Artboard 2> -> Return to Originating artboard B
Currently I have the following options:
a. Duplicate the Artboards (Ie Artboard 1 and 2 in the example above). This means that if I modify the Artboard (1 or 2) I have to repeat the modifications in all the duplicates.
b. Make all the content of the Artboards into a component, one component for each artboard (I.e. a component for artboard 1 and a component for artboard 2). This works for some situations where minor layout mods are made, but feels messy to me, and more importantly does not help if I want to add another artboard.
One way to achieve the required functionality is to llow artboards to be grouped together, and add a trigger action "Return to Artboard previous to group"
A more sophisticated version would be to allow the creation of Artboard level components. I.e. A component that contains whole artboards, and allows modification of things such as layout, triggers and actions, addition of new artboards in the "main component" and overrides in the component instances.
Henri Le Forestier commented
We are often working on a full project but need to update our clients of a specific view (e.g. we want to show only the dashboard). We want the client to be prevented to access certain artboards that are still a work in progress but were linked in the prototype mode at an earlier stage.
Problem is, we cannot prevent the client to click links and end up in artboards that are still a work in progress. We need to manually remove ALL links from the prototype mode to prevent that and redo the whole process along the way.
It is especially painful when we go from wireframing (all links are prototyped) to designed mockups (we need to destroy our previous work, only to redo it again later on, hoping to not have forgotten anything!).
I thought the "markup for export" would solve this and break any links to non marked artboards. It does not.