The last revision #54 builds "revisit" blocks and table editing. But sometimes the author has dozens of fields for a particular object, and the fields are used in rare combinations for particular documents. A table with 30 columns is unusable. Especially if you add the "Edit" button and it takes you to edit a bunch of attributes that you didn't need to provide initially and are not used in the output document.
Idea:
Merge fields like name and address into one column each with some manual heuristics, we don't want to waste 8 blocks on that
Have an optional style where the review is vertical instead of column based. We would show one "person" in a block, followed by the next "person". In a lot of instances, it would just be one person. Each field, other than the combined button for name and address, would need its own "edit" button too.
BryceStevenWilley
commented
1 year ago
The last revision #54 builds "revisit" blocks and table editing. But sometimes the author has dozens of fields for a particular object, and the fields are used in rare combinations for particular documents. A table with 30 columns is unusable. Especially if you add the "Edit" button and it takes you to edit a bunch of attributes that you didn't need to provide initially and are not used in the output document.
Idea:
Like: