System-wide relationship needs to be auto generated and maintained when users do things that impact other forms

[jegelstaff]

System-wide relationship is based on all linked elements connecting all forms.

Linked elements create one-to-many relationship links between the source (one) and the target (many). (Target is the form with the element, the form that is drawing values from the source.). These links are always display together, and NOT delete together.

Display together flag needs to be deprecated/removed/always on.

In addition to adding links to the relationship, creating a linked element creates a subform element in the source form (if one does not exist). Creating a subform element in a form creates a linked element in the target (if one does not exist) (and also creates the link).

[jegelstaff]

** Logic interpretations in code...

Display together is not in the UI and logic is removed from the system.

Screen admin UI updated to show the system wide relationship as default instead of "Form only" and system wide frid 9569 gets stored with the screens (new default for frid). But form-only still exists as an option.

checkForLinks and other relationship functions need to operate OK when there are no linkages in a relationship (because system wide might not have linkages for a long time, or ever)

When system wide relationship is in effect, all existing saved views are available.

Bug fixing-quality of life: Columns in the Entries tab of the list of entries need to only show the elements of the form one form away. Also need the Form name to show. Also need to be draggable into different order.

** For patching...

system-wide-relationship includes all linked elements. Source element is the one, linked element is the many. System-wide-relationship is number 9569.

** For ongoing config...

system wide relationship can be edited, but only after acknowleding warning that it affects the whole system and is maintained automatically.

Subforms can be created to any form. User is prompted through a process to specify the linked fields if there aren't any already (dropdown list for linked element). Doing so creates the fields and adds the link to the system wide relationship.

Linked dropdown boxes and non-multiple value autocompletes lead to creation of system wide relationship linkages, one to many, where source form is the one side. Also creates subform element in the one side form.

--

Optional??? Linked checkboxes and list boxes and multi value autocompletes lead to creation of linkages. A pair of linkages, one to many and many to one, ie: representing both directions. Need to test checkForLinks to see that it can figure this out!!

--

When elements are deleted, linkages that use that element, in all relationships, must be deleted.

ALSO: saved views no longer are restricted to the mainform they start with