Page Comparison

Form is associated to all CPs

Yes

No

System-level JSON is enhanced to show the custom field in any CP to avoid the CP-specific JSON dictionary configuration for custom fields. This is subject to the condition that the system-level dictionary doesn't have any custom fields in it.

CP should not have any CP level workflow attached so that it will use the system level workflow as default.

Form is attached to specific CP

Yes

No

CP-specific custom fields are displayed on respective add/edit/overview pages. This is to avoid any additional configuration for custom fields within the dictionary of CP JSON. 

This allows you to define a system-wide dictionary and yet define CP-specific custom fields without requiring to create/maintain a CP dictionary.

This will only work if you have not manually configured the custom fields within the “dictionary” section of the system level JSON.

Form is attached to specific CP

Yes

Yes

CP-specific custom fields are displayed on respective add/edit/overview pages. This is to avoid any additional configuration for custom fields within the dictionary. 

This will only work if you have not manually configured the custom fields within the “dictionary” section of the CP level JSON.