Bump modeling dependencies

[nikku]

Closes #4118
Closes #4037

Related to #3622
Related to #4062

[barmac]

The documentation link from HTTL rule leads to a non-existing page: https://docs.camunda.io/docs/next/components/modeler/reference/modeling-guidance/rules/history-time-to-live

Note that the URL generated from https://github.com/camunda/camunda-docs/pull/3324/files will be different (httl-required vs. history-time-to-live).

[barmac]

#4118 is fixed 👍

[barmac]

#4037 is fixed 👍

[barmac]

For #3622, I will add a template to dev resources which uses new properties.

[nikku]

#4154 (comment)

Yes, that is intentional. What we use is the final URL, and the documentation needs to be fixed.

[barmac]

I cannot set a default number value to number property.

[nikku]

I cannot set a default number value to number property. (ref)

Let's consider if this is the desired behavior, or = 100 would be the proper way to set a default.

[barmac]

The dynamic ID check is not supported and triggers undesired suggestion in VS Code:

Screen.Recording.2024-02-26.at.10.42.41.mov

We should probably switch to 100% programmatic support.

[barmac]

Combination of type: Boolean, value: true, feel: required blows up the FEEL entry:

Screen.Recording.2024-02-26.at.10.46.15.mov

[barmac]

type: Number, feel: static works incorrectly when changing values with increment/decrement:

Screen.Recording.2024-02-26.at.10.48.24.mov

[barmac]

type: Number, feel: static works incorrectly when changing values with increment/decrement:

Screen.Recording.2024-02-26.at.10.48.24.mov

This applies also to feel: optional though it seems to jump less.

[barmac]

Such condition is never fulfilled regardless of the field value:

    {
      "type": "Text",
      "value": "displayed when static is 100",
      "binding": {
        "name": "text",
        "type": "zeebe:property"
      },
      "condition": {
        "property": "number-static",
        "equals": 100
      }
    }

I have to use string value to make it work.

[barmac]

type: Boolean, feel: optional does not trigger FEEL editor

Screen.Recording.2024-02-26.at.10.54.39.mov

    {
      "id": "boolean-optional",
      "type": "Boolean",
      "value": true,
      "label": "boolean-optional",
      "binding": {
        "name": "boolean-optional",
        "type": "zeebe:property"
      },
      "feel": "optional"
    }

[barmac]

@nikku I've pushed my dev template for number and boolean values. We should fix the bugs I found prior to the release or disable the feature.

[nikku]

To better understand the impact: Is this breaking existing functionality (if no Boolean or Number inputs are used)? For now it looks to me like we can continue (no need to disable).

[barmac]

It's not breaking. Only a new feature is broken. Sure we can merge and fix this later. It's not a blocker for the merge but rather for the release.

[barmac]

What is troubling is that the Windows build is consistently failing :/

[nikku]

It's not breaking. Only a new feature is broken. Sure we can merge and fix this later. It's not a blocker for the merge but rather for the release.

Let's consider if we announce it or not. That is all, I think.

I updated this PR to not indicate that #3622 is closed. Could you comment on the issue regarding the remaining topics to handle?

[nikku]

Let's get this PR merged, and follow-up afterwards.

[nikku]

Moved #3622 back to ready as it is clearly not fixed.

[marstamm]

Thank you for the thorough integration testing. I gave all reported issues an initial evaluation here.

type: Boolean, feel: optional does not trigger FEEL editor

@barmac , I could not reproduce this issue, is there anything I am missing when trying to reproduce it?

[barmac]

It looks like this is an edge case, but the UI jumps/flickers if you click a lot:

Screen.Recording.2024-02-28.at.14.54.24.mov

[nikku]

Looks like a bug to me. Clicking the FX toggle does not properly prevent the click interaction, temporarily triggering checking the checkbox (via standard browser "check if label for checkbox is clicked" interaction.

[marstamm]

Clicking the FX toggle does not properly prevent the click interaction, temporarily triggering checking the checkbox

I agree, but it does not prevent you from toggling as initially reported. This is also an issue for boolean toggles in form-js, so it needs to be fixed in the properties-panel. I'll create some GH issues for what was reported.