Override role settings by report: maybe it should be
Anyone else try out the Override role settings by report?
When playing with changing reports, edit, add, grid edit we notice setting one Role to use a different form affects every report in that table. This means the developer must update all reports not intended to be affected by this change to the <Use Standard Behavior> setting. Currently the default is "Use Role Settings". The result is all the Grid Edit reports load the same report everywhere with one change.
The default is "Use Role Settings" but maybe it should be <Use Standard Behavior>
We do not see a Use Case where defining a Role/report/form setup will want to affect every report unless it handles security, which wins. Instead we see the intent of this feature is to target a specific workflow/process/pattern and NOT affect all others. The way it is currently defaulted, the developer must change all the reports or the Users will not understand why all their reports suddenly changed to a different report when in grid edit.
Steps:
1. Using a table with many reports embedded and grid edit is in use.
2. Enable the "Set how different roles use these forms" feature for a given Role.
Notice how all reports are affected by this change. Every Grid edit displays the same report columns.
Expected result:
Embedded reports opened in Grid Edit using the defined form. All other reports use <Standard Behavior> for Grid Edit unless specified. This makes the least amount of change to the entire App structure. Then if the developer wants to make it for all, it can be done by changing "Override role settings by report".
https://quickbase.uservoice.com/forums/111823-quickbase-product-feedback/suggestions/42933681-override-role-settings-by-report-maybe-it-should
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------
When playing with changing reports, edit, add, grid edit we notice setting one Role to use a different form affects every report in that table. This means the developer must update all reports not intended to be affected by this change to the <Use Standard Behavior> setting. Currently the default is "Use Role Settings". The result is all the Grid Edit reports load the same report everywhere with one change.
The default is "Use Role Settings" but maybe it should be <Use Standard Behavior>
We do not see a Use Case where defining a Role/report/form setup will want to affect every report unless it handles security, which wins. Instead we see the intent of this feature is to target a specific workflow/process/pattern and NOT affect all others. The way it is currently defaulted, the developer must change all the reports or the Users will not understand why all their reports suddenly changed to a different report when in grid edit.
Steps:
1. Using a table with many reports embedded and grid edit is in use.
2. Enable the "Set how different roles use these forms" feature for a given Role.
Notice how all reports are affected by this change. Every Grid edit displays the same report columns.
Expected result:
Embedded reports opened in Grid Edit using the defined form. All other reports use <Standard Behavior> for Grid Edit unless specified. This makes the least amount of change to the entire App structure. Then if the developer wants to make it for all, it can be done by changing "Override role settings by report".
https://quickbase.uservoice.com/forums/111823-quickbase-product-feedback/suggestions/42933681-override-role-settings-by-report-maybe-it-should
------------------------------
Jim Harrison
transparency = knowledge + understanding : The Scrum Dudes
------------------------------