Found possible bug in Tasklist API

[aavila]

Hello everyone.

I think I found a bug in regards to how the Tasklist API recieves the variables JSON when completing a task. When I try to send this valid JSON string when completing a task:

{
    "variables": [
        {"name": "fechaInicio", "value": "10.10.2023"},
        {"name": "fechaFin", "value": "10.11.2023"},
        {"name": "razon", "value": ["vacaciones"]}
    ]
}

I get a 500 server error code.

Now, when I try to send only one variable:

{
    "variables": [
        {"name": "fechaInicio", "value": "10.10.2023"},
    ]
}

I get this error code:

That makes no sense. I’ve searched over here and over StackOverflow, and everything indicates that I’m using a valid JSON string format, thus it should not matter if I’m using a point inside the string or not (which I’ve already tried changing for a -, but the same error appears) Does anyone know why this could be happening apart from it being an internal error regarding how the JSON objects are treated?, Why can’t I use those symbols?

[GotnOGuts]

As mentioned in your other thread, the value itself must be a string containing a valid JSON document.

Thus.

{
    "variables": [
        {"name": "fechaInicio", "value": "10.10.2023"},
    ]
}

should be sent as:

{
    "variables": [
        {"name": "fechaInicio", "value": "\"10.10.2023\""},
    ]
}

[aavila]

This was exactly the problem! Thanks for your help @GotnOGuts!