You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Me, sitting behind the back of our support engineer while he is trying to fix "unfetched attribute" error in the groovy report.
Description of the bug or enhancement
For complex reports debugging often is done iteratively:
(working in Report Editor)
change band script
press "Run"
input all required parameters (date from, date to, select entities, ...)
press "Run report"
check the document or exception - it doesn't work...
change band script
press "Run"
input all required parameters (date from, date to, select entities, ...)
...
It's quite tedious to input the same parameter values every try.
Can we improve user experience in this situtation and remember previously entered parameters?
I'm not sure how exactly it should work, because:
a) parameter specifications can change between test runs
b) sometimes user may mean to see "clean" input parameters dialog how it usually looks
E.g. it could be an additional button on bottom pane.
The text was updated successfully, but these errors were encountered:
Environment
Description of the bug or enhancement
For complex reports debugging often is done iteratively:
It's quite tedious to input the same parameter values every try.
Can we improve user experience in this situtation and remember previously entered parameters?
I'm not sure how exactly it should work, because:
a) parameter specifications can change between test runs
b) sometimes user may mean to see "clean" input parameters dialog how it usually looks
E.g. it could be an additional button on bottom pane.
The text was updated successfully, but these errors were encountered: