orchestra 1.0.0-alpha21

WARNING: THERE IS NO MIGRATION PATH. YOU MUST REINSTALL FROM SCRATCH.

Do not update an existing site to this release. Orchestra ships no update hooks, and none is coming until the first beta release. A site on an earlier alpha holds a database and a module list this code does not match.

Uninstall the Orchestra modules, drop what they leave behind, and install 1.0.0-alpha21 fresh. Every instance, token, task, incident, variable, attachment and delegation from an earlier alpha is lost, and that is expected.

Between alpha20 and alpha21 in particular, no field, table, setting, permission or path changed: this release changes code, the Complete modeler's stylesheet and scripts, and the French catalog.

New

• The Complete modeler marks the rows holding unsaved work. A node or flow you type in is tinted and labeled "Modified" at once, before Apply; one added or cloned is labeled "New"; one moved, dragged or renamed is marked too. The marks survive every rebuild and go when the workflow is saved, like the unsaved changes warning. #3629081: Mark the Complete Modeler rows holding unsaved work, as you type

Fixes worth naming

• A BPMN.io save could delete a flow. A conditioned flow reconnected in the Complete modeler keeps its id, which could be the from__to id of a plain flow joining its old steps; saved in BPMN.io, one of the two overwrote the other. BPMN.io also drew such a flow along its old route, right on top of another flow, so it looked missing. #3629069: Never delete a flow reconnected in another modeler on a BPMN.io save, and draw it between its actual nodes
• A version migration ignored a step halted on an incident, so an instance stopped by a mistake in its workflow could not be moved to the version that fixes it: nothing moved, nothing was reported, and every retry halted again. The halted step now moves with its child or instance, and a part that cannot move says why. #3629058: Let a version migration move a step halted on an incident, and report it when it cannot
• The Complete modeler could not take a condition off a flow whose condition settings were incomplete: choosing "None" again reported the empty Variable as required. #3629075: Let the Complete Modeler take a condition off a flow whose condition settings are incomplete
• A flow pointed at another step kept an id naming its old steps. On save, the Complete modeler now gives such a flow an id naming the steps it joins, as long as its id was a generated one; its BPMN.io route, its label position and its translations follow it. A cloned flow also starts from its source's condition settings. #3629147: Rename a flow pointed at another step in the Complete Modeler, while its id is still a generated one

Changed

• A node or flow just added or cloned in the Complete modeler is brought into view, with the focus on the first field of its form. #3629076: Move the focus to a node or flow just added in the Complete Modeler, in its form

Housekeeping

• The codebase metrics page is refreshed: 1,407 files and 134,901 lines of code.