Skip to content

apps/panel 0.75.1 ​

English · Русский

Released on 26 August 2026. Previous release: 0.75.0.

What changed ​

  • The graph.edges parameter has been removed from the BPMN panel types and configuration because the panel does not use it.
  • When the panel opens or refreshes the graph, it runs the configured method and continues to show the returned Link resources as existing connectors.
  • When a person draws a new connector, the panel reads its persistence settings from the matching graph.toolbar.items[] entry, sends the new Link using request.linkName, and runs the graph method again. The connector remains on the diagram when the refreshed response contains that saved Link.

Configuration update ​

Remove graph.edges when you next edit a BPMN configuration. Do not move its former entries elsewhere. Keep connector creation under graph.toolbar.items[].request; the graph method supplies existing Link resources.

The fragment below uses illustrative values: workflow-link is a stable toolbar item ID, and WFConnectorInstance stands for the project's technical Link type.

json
{
  "graph": {
    "toolbar": {
      "items": [
        {
          "id": "workflow-link",
          "bpmnType": "bpmn:SequenceFlow",
          "request": {
            "linkName": "WFConnectorInstance"
          }
        }
      ]
    },
    "nodes": []
  }
}

Replace both illustrative values with the identifiers used by the project. See the BPMN configuration guide for the supported configuration boundary. If a newly drawn connector does not remain after the refresh, follow the guide's creation recovery steps before retrying with unchanged configuration or data.

Compatibility ​

Older saved JSON remains loadable when it still contains graph.edges: the panel ignores the extra property. Removing it does not change how existing connectors are displayed or how connector changes are saved.