Skip to content
Diteko

Import a flow

Projects › New project asks where the flow is:

  • In my Connect instance. Lists the flows on the instance the server is connected to, and links the project to the one you pick. Only a linked project can run tests live on Connect. This needs the server connected to Connect.
  • In a JSON file. A flow exported from Connect’s flow designer, or compiled with cxblueprint (flow.compile_to_file). Every block type cxblueprint can emit is understood.
  • I will paste it. The same JSON, pasted.

A project from a file is not linked. Set its Connect flow ID on the Flow stage to link it; until then it can dry-run only.

From Python:

# A Connect export, or cxblueprint output
project = dk.projects.from_json("claims.json")
# A cxblueprint flow object
project = dk.projects.from_cxblueprint(flow)

When a flow will not import

Section titled “When a flow will not import”

Diteko checks the flow before saving it and says what is wrong: a missing start block, a transition to a block that does not exist, a block nothing reaches. Unknown block types are not an error; they are treated by their shape (a block with conditions branches on the environment, one without passes through) and the import says so.