Report Fields Viewable But Not Modifiable by Applicants/Grantees
We would like to carry over internal report fields into Follow Ups that can be viewed by grantees for their information but not modifiable. This would particularly be helpful with fields like Grant Amount and Final Report Due Date in Grant Agreements and Final Reports.
posted October 25, 2012 by Katie Kaufmann, MRAC
-
Chris Dahl commented
Hi all,
This was released to production GLM as part of the 5.0.0
release. If you have additional feedback regarding this functionality,
please create a new "idea" item.
Thanks - and I hope you find the new functionality valuable.
-chris -
Chris Dahl commented
Hi all,
We are going to be looking at updating the report field functionality in the next 6 months.
Since this idea is really similar to the idea " https://community.foundant.com/foundant/topics/setting_permissions_for_report_fields ", I wanted to let folks on this thread know that I will be providing further updates on the "Setting Permissions ... " thread.
Thanks,
-chris -
Katherine commented
Hi Chris,
I just said as much on a similar thread, but this is definitely at the very top of our wishlist for future Foundant iterations. We already use a lot of report fields (I think there are around 80 in our RF Templates section), which is probably something that will change once I dig into revamping our system, but regardless I would happily take an additional performance hit if it meant having a read-only state!
Thanks!
-Katherine
-
Ideas commented
Hi all,
This is something we've heard about a few different times, but it hasn't yet been a high enough priority given other enhancements that have been needed.
One of the challenges is that this would add an extra "state" to the report field configuration on the process editor. While that in and of itself is not a big deal, it does have implications on the performance of that page, specifically when report fields are being configured. So at this point, we have to balance the negative performance implications for all customers with the enhancement that some customers would take advantage of.
I would ideally like to see us work on this as part of an overall effort to improve report field configuration. However, if it doesn't look like we'll get a chance to get to that, we may add this extra state and take the performance hit, but it's something that is going to require more internal discussion. I'd be interested to hear what people think about the current report field configuration performance (and how many report fields they are dealing with) versus the performance cost of adding another state to that configuration.
Thanks for the input, and all my best for a happy and healthy 2013,
-chris
posted December 27, 2012 by Chris Dahl, Foundant Technologies
-
Ideas commented
Great idea! It would really help protect information and data.
posted December 3, 2012 by Dee Ann Harris, Leightman Maxey Foundation
-
Ideas commented
This would be soooooo helpful, great idea.
posted November 30, 2012 by Carrie Hanson, West & Chaney Family Foundations