Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Call Activity - Process Id field doesn't support expression and it should
See original GitHub issueFor Camunda Cloud, when you create a new Call Activity, the process Id field should support expressions but it shows an error (Not a valid QName) instead.
Steps to Reproduce
- Create a new call activity
- Enter
=in theprocessIdfield - An error will be shown complaining about the invalid id
Expected Behavior
It should work, that’s a documented feature.
Usually, the processId is defined as a static value (e.g. shipping-process) but it can also be defined as expression (e.g. = “shipping-” + tenantId). The expression is evaluated on activating the call activity and must result in a string.
Environment
- OS: Mac OS
- Camunda Modeler Version: Latest
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@danshapir As a workaround you could go to the XML view and change the process ID there.
As it is a documented feature we should fix it.
Is there any update on this issue? Or a workaround until it’s fixed?