Jedox Ideas
Let us know how we can make Jedox even better!
Let us know how we can make Jedox even better!
I think it would be very helpful if a native input field was created and added to the list of native canvas components. My vision for this would be a input field you could drag into a canvas which the end user could type into. This input would be stored in a variable/named range/etc and useable downstream in integrator or setdata formulas, etc. Currently to achieve something like this, you need to unlock a cell, and wrap it within a frame, and drag the frame into a canvas, which has several shortcomings. One of these shortcomings are that you cannot tab from one frame to the next in the event that your input form has multiple fields for the user to type into. They currently need to click each field individually. Most users are used to being able to tab from field to field. Formatting is also a pain point with the current method of using a frame. It is difficult to achieve similar formatting when used in conjunction with a native canvas drop down box, for example. I think this would greatly speed up the creation and flexibility of input forms we create, which are a frequent request from our clients.
0
Future Consideration
Also very useful (like in other low code platforms): if the input box can be specified to hold a certain data type. Along maybe with other settings (disabled and so on)
(see also screenshot)
I agree, that an input or additional text field (multi line) would be very beneficial.
Furthermore I would consider, that it would be much more easy, if this field could be directly be accessed through an expression. This way, there would be no need for a variable to save the value. In the end, variables are not a user friendly way to make a report interactive (imho). It is just a left over from older times. Nowadays are much better ways to accomplish this as this is also done in other modern software tools. I think expressions are the right way there to go. An input window, which lets you select available components and their values would be a very helpful for that.
Great idea. About this sentence: "This input would be stored in a variable/named range/etc and useable downstream in integrator or setdata formulas, etc. "
-> I would like a palo.data formula which directly writes the data back. The other options like variable, named range would be beneficial.
And this idea too: https://feedback.jedox.com/ideas/JS-I-1699
Please check out this idea as well: https://feedback.jedox.com/ideas/JS-I-1768