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
It would be good if we could use the each report as part of a massive, per-row form generation system.
So that you could have a couple of text boxes, or drop downs at the very top of the report...
Then you could make some decisions on a per-row basis, like "include this row because I checked the checkbox" or "for this row I chose option C rather than option default of A for this row using a select2 box, etc" and then post the entire form (using a botton at the top of the page) to some form processing URL that the report designer specified.
When the report was generated directly as HTML, this was easy to assert, because you just added a <form... > element to the starting html and a to the ending html section and because the report itself was always a very long all inclusive HTML page, this was no problem.
But now the report is something that loads through AJAX, sometimes into front-end viewer which is itself loaded through AJAX, makes thinking about how to make this functionality work a little harder.
-FT
The text was updated successfully, but these errors were encountered:
It would be good if we could use the each report as part of a massive, per-row form generation system.
So that you could have a couple of text boxes, or drop downs at the very top of the report...
Then you could make some decisions on a per-row basis, like "include this row because I checked the checkbox" or "for this row I chose option C rather than option default of A for this row using a select2 box, etc" and then post the entire form (using a botton at the top of the page) to some form processing URL that the report designer specified.
When the report was generated directly as HTML, this was easy to assert, because you just added a <form... > element to the starting html and a to the ending html section and because the report itself was always a very long all inclusive HTML page, this was no problem.
But now the report is something that loads through AJAX, sometimes into front-end viewer which is itself loaded through AJAX, makes thinking about how to make this functionality work a little harder.
-FT
The text was updated successfully, but these errors were encountered: