SHORT: If we want this field editable we don't add permission. If we want permission anyway then we don't at this feature in this release.
LONG: If we add these edit fields we should not add separate permission or configuration for these fields. If we have to create permission based on fields of a form that it's a big task and shouldn't be included in this release. If we keep on adding permission and configuration then it will make things more complex in Mifos. Fields based permission makes things complicated when you don't have supporting framework. Usually we should have permission (CRUD - CREAT/READ/UPDATE/DELETE) like "Can view center" "Can create center" "Can edit center" "Can delete center" Mifos doesn't have notion of delete which is fine, if we go with field based permissions then things will be like "Can view center name" "Can view center xyz" 100 more center permissions ... We should not go with field/object based security as Mifos code does not have support for it, these things will make security code cleanup difficult later. We have done field level security in past but it has resulted in more damage. I would suggest that we stick with CRUD principal for Mifos permissions. i.e. if a user has edit permission then he can edit everything related to the center/client. Udai ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Mifos-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-users
