Details
L3 - Default Description
Given:
a date variable 2019-12-12T10:59:00.000+0200 that is displayed as 2019-12-12T10:59:00.000
Steps to reproduce:
1. Add a variable filter on the Process Definition view
Variable : dateVar = 2012-12-12T06:12:12
Problem:
I get no result. When I switch the operator to =! the respective instance will be displayed
Expected behavior:
The process instance is displyed
Rootcause:
- The backend only interprets the full-formatted value 2019-12-12T10:59:00.000+0200 as a value of type Date. 2019-12-12T10:59:00 is treated as a String
Solution Idea:
- When a short-form date value is used for filtering (2019-12-12T10:59:00), the frontend sends the full value to the backed (2019-12-12T10:59:00.000+0200)
- If users want to search for 2019-12-12T10:59:00 as a String value, they can surround it with single quotes. This is similar to how number and null values are handled, see for example https://docs.camunda.org/manual/7.15/webapps/cockpit/bpmn/dashboard/#search
- The behavior is consistent for all places where people can search for variable values
Hints:
- Filtering by the full value 2019-12-12T10:59:00.000+0200 works as expected currently
- Same problem when using the filter on other views (instance view, etc)