Details
-
Type:
Sub-task
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.4.0
-
Fix Version/s: None
-
Component/s: CiviHR, Core CiviCRM
-
Labels:None
Description
When an extension defines a new custom data group, the extension developer should be able to treat it as "his own" – i.e. the developer makes decisions about what fields to add, and the downstream administrator does not.
A minimalist approach:
1. Add a new column, civicrm_custom_group.is_reserved, which defaults to FALSE. Make sure the column is created for new sites and upgraded sites.
2. In the screen "/civicrm/admin/custom/group?reset=1", don't list reserved custom-groups
3. In the other admin screens ("Settings", "View and Edit Custom Fields", "Add/Edit Field"), throw a fatal error if someone tries to manipulate a reserved custom group.
4. (Last issue – don't let this block work) In the popup "Form Designer", don't display the option to add a new field for reserved custom groups.)
