Tie ECA Model config entity's status to the Modeller plugin's status

The eca.model.* entities don't always exist. They do for the BPMN.io modeller, but they don't for the classic modeller at this point. So, I wonder if the views should be based on the eca.eca.* config entities, and we should probably provide views reference to the model entity if one exists so that you get access to more details from there?

If that's worth a consideration, an MR would be welcome and we'd be reviewing it and help getting it into the project.

I think using eca.eca + relationship in Views is redundant since there is a 1-to-1 relation with eca.model and the purpose is showing documentation on the UI.

On my first try I edited the save function of ModellerBpmnBase plugin and broken my VM 😅

Then I realized the issue is on the Model config entity (not part of the BPMN submodule): just adding ->setStatus in the setData function (like the service/Modellers was doing) and "status" in the config_export annotation did the trick.

(am I doing this right? 😬)

I think using eca.eca + relationship in Views is redundant since there is a 1-to-1 relation with eca.model

That's not the case. It is true for models that have been created with the bpmn_io modeller, but not for the eca_cm modeller, though. That's what I mentioned in #2.

Marking as fixed due to missing feedback.

Automatically closed - issue fixed for 2 weeks with no activity.