Hide wf and status updates from Report Builder for non-admins
In system features (global settings), there’s one called “Report – Manager” that allows those roles to access the report feature in system, build reports, export them, etc.
o A subset of these features allow for wfs and statuses updates to be triggered (similar to bulk update)
We have a user base that could benefit from self-service reporting, but shouldn’t be able to perform bulk CRUD operations on db.
Suggestion: have a lower perm’d “Report – Builder” that splits off the “Update status” and “Trigger Workflow” features
o This would mirror the personal list view limitations for non-admin users
Elijah Biggs
shared this idea
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
As part of a larger discussion on Report Builder improvements, we have linked this for consideration.
-
Elijah Biggs
commented
One other suggestion for multi-environment clients. Introduce personal reports that don't get overridden by a T2P from lower environment. This would be similar to the personal list views (that don't get overridden by T2Ps)
It is overly complicated to build a report on a lower environment and configure a T2P to run the report on prod. The only alternative is to build the report twice