camunda/camunda-modeler

Describe the bug The FEEL Playground reports the following warning for cycle(), a supported Camunda FEEL function: No Function Found: No function found with name 'cycle' and 1 parameters. cycle(duration) is supported by the Camunda FEEL engine and is valid for timer expressions. This looks like a false positive caused by a mismatch between the Playground evaluator and the linting built-in-function catalog. Steps to reproduce Open a FEEL expression in the Modeler FEEL Playground. Enter: =cycle(duration("P7D")) Observe the lint warning: No Function Found: No function found with name 'cycle' and 1 parameters. Expected behavior The expression should be recognized as valid and should evaluate to: R/P7D The two-argument overload should also be recognized: =cycle(3, duration("PT1H")) which should evaluate to: R3/PT1H Environment OS: not recorded Camunda Modeler Version: not recorded Execution Platform: Camunda 8 Installed plug-ins: not recorded Additional context Camunda docum

Problem you would like to solve When I open a new version of the Desktop Modeler (or I am new to Desktop Modeler entirely), it is not always clear what certain buttons do, especially for more complex features. For example, the cluster of buttons in the top right including the Variables panel: and the cluster of buttons in the bottom right including the process application and deploy buttons: Proposed solution Display tooltips on icon-only buttons (especially the ones highlighted above). This would help address the problem, and also help users discover new features we add in these buttons (variables panel, for example) Alternatives considered Keep the status quo Additional context No response

Problem you would like to solve Connection Manager allows users to specify a tenant ID in Self-Managed (and planned for SaaS) However, there are no guardrails to check whether the tenant ID is correct (or possibly correct). This can cause confusion for users because: Modeler provides regex validation for the other connection fields (like URL), and actually tries to connect to the cluster using them Users can face deployment errors with unclear messages if the tenant ID is filled incorrectly Proposed solution Verify the tenant ID actually exists by using the get tenant or search tenants endpoints as part of the connection check Consider also implementing (or asking the team responsible for the Orchestration Cluster API) to: add tenants to the topology endpoint the connection manager already uses create a new endpoint that allows us to fetch all connection-related information in a single call Tenant ID should remain optional Alternatives considered Keeping the status quo Lint warnin

Problem you would like to solve I am always frustrated when I want to break a path and continue by Link intermediate events: First the Link throw event including Name and Link Name, then create the Link catch event and enter the information Name and Link Name again. This interrupts the modelling flow, and this will be happen often. I use Link events frequently like carriage return with a typewriter: to accentuate different aspects of a process parts to emphasize a part of the process to confine certain steps to keep left-to-right direction despite jumping back (f.e. in loops) and more. Proposed solution Create a coordinated pair of Link events, if the respective partner does not exist. But how to configure the related throw / catch events simultaneously? 1.) Create and configure the Link intermediate throw event as usual. Provide the "Plus" sign for create a successor: 2.) Clicking the "Plus" sign creates a Link intermediate catch event and copies all relevant properties from the L

Describe the bug Given I define a condition expression on a flow leaving a non-gateway element (e.g. a task), when I open the properties panel, it displays "Conditional expression must be defined". Steps to reproduce Create a non-gateway element with an outgoing sequence flow Define a condition expression on the flow now this happens Expected behavior We display: "Condition expression is not supported". Environment OS: [e.g. MacOS 10.2, Windows 10] Camunda Modeler Version: [e.g. 2.0.0] Execution Platform: [e.g. Camunda 7, Camunda 8] Installed plug-ins: [...] Additional context Discovered via https://camunda.slack.com/archives/C0693F1NFK5/p1774889613007019