Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store a temporal value from an expression as variable #7054

Closed
saig0 opened this issue May 17, 2021 · 1 comment · Fixed by #8842
Closed

Store a temporal value from an expression as variable #7054

saig0 opened this issue May 17, 2021 · 1 comment · Fixed by #8842
Assignees
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog severity/mid Marks a bug as having a noticeable impact but with a known workaround

Comments

@saig0
Copy link
Member

saig0 commented May 17, 2021

Is your feature request related to a problem? Please describe.
In a process, I need to calculate a temporal value (i.e. date, time, date-time, or duration) in an expression and store it in a variable. Later, the variable may be used by a timer event.

Currently, the temporal value is not serialized as a variable. Instead, it replaces the value with null.

As a workaround, I need to transform the value in the expression into a string explicitly.
This way is also mentioned in the docs: https://docs.camunda.io/docs/product-manuals/concepts/expressions#temporal-expressions

However, it is easy to forget to transform the value and it's hard to root cause the problem.

Describe the solution you'd like
A temporal value is stored as a string variable by default.

The string value can be used in a FEEL conversion function to restore the temporal value.

Describe alternatives you've considered
Native support for temporal values without string serialization. But JSON doesn't have a type for these values.

Additional context

@saig0 saig0 added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog Impact: Usability severity/mid Marks a bug as having a noticeable impact but with a known workaround labels May 17, 2021
@Zelldon
Copy link
Member

Zelldon commented May 17, 2021

Example https://github.com/zeebe-io/zeebe-cluster-testbench/blob/develop/processes/actionRunner.bpmn#L8 where this would be useful. Or in other words where I run into this problem. The timeout was set to null, when I used the duration function and I didn't know why.

@npepinpe npepinpe added this to Planned in Zeebe May 19, 2021
@saig0 saig0 mentioned this issue Feb 8, 2022
43 tasks
@korthout korthout moved this from Planned to Ready in Zeebe Feb 21, 2022
@korthout korthout added this to the Evaluate DMN decisions milestone Feb 22, 2022
@korthout korthout moved this from Ready to In progress in Zeebe Feb 25, 2022
@korthout korthout self-assigned this Feb 25, 2022
@korthout korthout moved this from In progress to Review in progress in Zeebe Feb 25, 2022
@ghost ghost closed this as completed in 1081002 Feb 28, 2022
Zeebe automation moved this from Review in progress to Done Feb 28, 2022
@KerstinHebel KerstinHebel removed this from Done in Zeebe Mar 23, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog severity/mid Marks a bug as having a noticeable impact but with a known workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants