Comment 5 for bug 1991487

I'm not necessarily the requested audience since I *do* want the funds editable post-activation, but...

In 99% of cases, I don't think it's a problem for the fund to be editable post-activation. In Dojo it was, so this is a regression. Having said that, I looked at the available fields in EDI attribute sets and there *is* an option to INCLUDE_FUND. If that setting was used, then yes, I don't think fund should be editable. Anything that's sent via EDI should be static.

But I don't know what the use case for sending funds to vendors would be. If it's for the vendor to process items differently, we're already able to send copy IDs, call numbers, collection codes, line item notes, shelving locations, owning library etc etc. Whatever info is contained in a fund is probably best sent in some other data point that doesn't affect fund tracking.

So in my opinion I see two options right now:

1. A new flag/setting should be created to govern whether fund can be edited or not. This would protect safe use of the EDI attribute.
2. Remove the INCLUDE_FUND option from EDI attribute sets and then fund should be editable, governed by the already existing fund permissions.

My two cents is I would prefer option #2.