Michal Rykiert

Given other priorities, we stick with the recommendation to use floating-point number fields.

Given other priorities, we stick with the recommendation to use floating-point number fields.

We'll make it happen!

There's a chance it will be introduced in the new (web) Studio. For now, I put it under review.

We haven't experienced a lot of voices around such functionality. It's not on our roadmap for now.

We don't plan on expanding PowerShell actions. We suggest using other methods.

Makes sense! >> backlog :)

I believe such functionality already exists.

Already in our backlog :)

We consider this a nice-to-have. For now, we're not going to introduce such a feature.

We plan to address it in the new (web) version of Studio. I can't promise it's going to be available in the first release of it, but we have it on the radar :).

Done! :)

Done :)

Under review :)

Under review :)

We consider this a nice-to-have feature, and given current priorities, we realistically won't have time to address it.

We've already considered a very similar idea in the past and we decided against it (too far from where we want to develop the platform). The decision still stands.

We're currently in the middle of ongoing graphical changes. Once they're over, we can address this topic further. For now, I'm changing the status to under review.

It's already in the backlog, stay tuned!

We plan to address this idea in the new version of Designer Studio (in web). I can't promise it's going to be available in the first release of it, but let's see :)