Oh, the beloved item lists! :)
We're going to evaluate your request and see how we can address it.
Regardless, we're working on improving item lists anyway, so the work is in progress!
Oh, the beloved item lists! :)
We're going to evaluate your request and see how we can address it.
Regardless, we're working on improving item lists anyway, so the work is in progress!
Development-wise, it's not a trivial thing to ask for. However, we have it on our radar in our long-term roadmap.
I'm changing the status to under review.
Hi Katarzyna,
as such we're not exploring such functionality within the export packages. However, we plan to introduce functionalities which in large part will address the anonymity of credentials.
I cannot say anything more at this point, but stay tuned :).
In case more columns are needed, we strongly suggest using dictionaries or other types of data sources.
Given the nature of fixed values lists (which is to address quick and simple scenarios), we're not going to develop it any further.
As for the dictionary data source functionality, you may achieve the same result by creating a custom (non-predefined) data source.
As for the REST data source, we need to evaluate whether a larger group of users would benefit from it. Therefore, feel free to enter your voices of support in this thread or at least give it a like, so we could address it accordingly.
Hi Sebastien,
as for the further development of the "old" (desktop) Studio - that's a "no go" as we're focusing on the new (web-based) version of it.
We'll take into account your suggestion for the web version, but to be fair with everyone, I'm labeling this suggestion as "not now".
Hi Sebastien,
as for the further development of the "old" (desktop) Studio - that's a "no go" as we're focusing on the new (web-based) version of it.
We'll take into account your suggestion for the web version, but to be fair with everyone, I'm labeling this suggestion as "not now".
It makes sense -> straight to the backlog :)
Hi Krystian,
it's one of those suggestions where we see about the same number of advantages as disadvantages. Right now we don't plan a development in this direction.
Hi Monica,
it's in our long-term roadmap to extend the flexibility of the forms. With that said, other projects have higher priority for the upcoming v. 2026 development cycle.
Therefore, to be fair with you and the rest of the Community, I'm changing the status of this request to "not now", but rest assured, further form functionality development what would provide flexibility of the design without compromising standardization is on our radar.