Hoppa till huvudinnehållet

Run multiple instances of one workflow

Kommentarer

3 kommentarer

  • Phil MacIntyre

    Hi Berend,

    Thank you for your question. You may only run a single instance of a Workflow per context in which it originates. That is to say, you could run multiple instances of a Workflow so long as each was invoked from a different source in the app (e.g., the I Want To Menu, the context menu, from the taskbar, from a feature action, etc.), or even from the same source, as long as you had multiple copies of that Workflow and invoked them separately (e.g., I added 3 copies of the same Workflow to my IWTM - I could then run each of the 3 as separate Workflows).

    If you invoke a specific Workflow again, we restore your previous session, so the user can pick up where they left off (with their previous work preserved). If you run a Workflow again but with a change in context (e.g, a Workflow invoked from a feature action from feature A, and then invoking the same feature action from feature B) we will reset the Workflow so you don't mistakenly complete a Workflow in the wrong context.

    We also have a couple of commands which you can use to guide how your Workflows interact with one another ('workflow.cancel' and 'workflow.refresh') as described in our Dev Center docs.

    I hope that helps,

    Phil

    0
  • Berend Veldkamp

    Hi Phil,

    Thanks for this detailed answer. What I'd like to accomplish is to run a (inspection) workflow on one feature (and keep it open), and then run the same workflow for other features too. This way, a user would be able to quickly switch between different features. Ideally, each instance of the workflow would run in its own tab in the taskbar.

    From what I understand now, this could be accomplished by adding the same workflow, say, 10 times, for a maximum of 10 instances. This would probably be a practical limit caused by the screen size anyway.

    For context, this app will be used in an aircraft, and if features are located close to each other, a user may not have time to finish one inspection before starting another. Sometimes the aircraft will fly in circles around a cluster of features, so one needs to quickly switch between those too.

    0
  • Phil MacIntyre

    Hi Berend,

    Thank you for the description of your use case. You're correct that if you simply add multiple copies of the Workflow, they could be invoked separately and would then run separately, without a previous instance being cancelled/restarted by a new invocation.

    We had another user who was concerned that if their workers kicked off a Workflow from say a feature action, where the context is important, that the results might get applied to the wrong feature, hence why we trigger the form reset if the context changes.

    If you're looking to run the same Workflow against multiple features (from multiple instances of the Workflow), it may be a good idea to include some dynamically populated indicator so that the user knows which feature they're interacting with to avoid confusion.

    Have a nice day,

    Phil

    0

Du måste logga in om du vill lämna en kommentar.