Document "is public" setting for custom field groups

[seancolsen]

The new setting for making custom field sets public/private got committed to core without any documentation.

This page in the User Guide needs to be updated.

https://docs.civicrm.org/user/en/latest/organising-your-data/creating-custom-fields/#custom-field-sets

How exactly does CiviCRM change its behavior based on this setting?

As far as I can tell, this setting has only two effects:

• Custom fields attached directly to events are hidden from the event info page if they are part of a private custom field set
  • from CRM-20318: Add is_public setting on Custom groups civicrm-core#10028
• Custom fields attached to some other entities (e.g. participation, contribution, etc... not sure of comprehensive list) are displayed in the registration email sent to participants, but only when this email comes from a back-office registration. These fields will be hidden if they're part of a private set.
  • from CRM-20507 - Allow only public custom groups to display on participant receipts civicrm-core#10661

[seancolsen]

See also: ticket to track changes to Core in order to add help text to the UI https://lab.civicrm.org/dev/core/issues/6

[dvhirst]

2018 03 23; 17:50 US/PDT - I'm on this one. At the stage of reviewing existing material. It looks like an image needs to be replaced, and some additional words created. I'll update this comment when I'm further along.

2018 03 24; 22:50 US/PDT - not much progress, further analysis of impact is needed, I'll work on it over the next couple of days.

[mattwire]

@monishdeb @jitendrapurohit Can either of you comment on this as it's not clear what the new option does and looks like you were involved in the PR that added it?

[jitendrapurohit]

Hi @seanmadsen @mattwire Thanks for the ping. This setting is only applicable to event custom sets, i.e -

• Non-public sets are not shown on the Event Info page.
• It will not be included in the event receipt template sent to the participant after registration.

I've raised a PR for the doc at #338

[seamuslee001]

This was addressed in #351 and also added via civicrm/civicrm-core#13060 closing