REST Connector: validation for URL not working in all cases

[MaxTru]

Describe the Bug

REST Connector: validation for URL not working in all cases

Steps to Reproduce

1. Use the REST POST Connector
2. Have the following FEEL statement for the URL:

"https://api.github.com/repos/camunda/product-hub/issues/" +
  string(epicIssueNumber) +
  "/comments"

3. Deploy diagram => everything works
4. See that Linting gives an error:

Expected Behavior

Linting only highlights actual errors

Environment

SaaS as of 07.11. on a 8.3.x cluster

[sbuettner]

@MaxTru The multi-line input breaks the input validation check as we only test non-FEEL input. Its therefore an outcome of the missing multi-line support in the modeler FEEL syntax validation.

cc @nikku

[MaxTru]

Hi Simon,
I think there was an update on this, but I forgot :-) Can you please recommend what way I should best format this (I want to get rid of the errors in our diagram). Currently I have:

"https://api.github.com/repos/camunda/product-hub/issues/" +
  string(epicIssueNumber) +
  "/comments"

[sbuettner]

Hey @MaxTru as this was merged camunda/feel-scala#701 we have to wait until zeebe is using the new FEEL engine. Hopefully in the next release in December. This will unblock this issue. For now you will have to either use the rest connector or convert the issue number to a string in a previous script task.

[CharlieBytesX]

Hi, what's the proper way to interpolate strings with process variables?

[CharlieBytesX]

Or append
Im using:
"http://host.docker.internal:3000/get_person_id_by_employee_cr_id/"+string(employee_cr_id)
and get
jakarta.validation.ValidationException: Found constraints violated while validating input:

• Property: url: Validation failed.

[ev-codes]

Hi @CharlieBytesX !

Your FEEL expression looks ok to me.

Here's some troubleshooting steps:

• Make sure the dynamic FEEL expression button (fx) next to the URL field is enabled. When enabled, the button should turn blue and an equals sign should appear next to the text field (see screenshot).
• Make sure the employee_cr_id process variable is not null. If a null value is expected, you could try an expression like: "YOUR_URL" + (if employee_cr_id then string(employee_cr_id) else "")

[ev-codes]

I'm closing the issue because:

• I can no longer reproduce the bug
• I don't think @CharlieBytesX 's question is related to the original bug in this issue

We can re-open this issue later if needed 😄