Primary Relationship

[jegelstaff]

See related issue(s)

[jegelstaff]

This needs to handle empty/new systems, where there are no forms, no connections. We should setup the Primary Relationship, with no links, as part of the install.

[jegelstaff]

This needs to handle empty/new systems, where there are no forms, no connections. We should setup the Primary Relationship, with no links, as part of the install.

Done. Simply always created on loading admin page. Formal DB update not required.

[jegelstaff]

• Need to present primary relationship in privileged position in UI, and make it not editable.
• Need to make all screens default to -1 instead of 0 for relationship
• Create link when making linked element in form
• Change link/delete link when target of linked element changes
• Delete link if linked element is deleted and there are no other links between the forms -- disallow deletion if linked element is used in a subform -- provide big warning when deleting elements that are used in relationship
• Allow creation of subforms to any form, make linked element creation part of process, wizard process to select format of subforms, and select link or create new link if necessary (and creation of element sets up link in PR)
• when subform is made, subform screen version of form is made automatically for use in popup/full form, and linking element is excluded. All other elements on one page.
• add option to the Advanced tab of the element editing page, to specify a one-to-one connection to any other element in any form. Wording needs perfecting.
• Remove relationship restrictions on saved view loading
• Make formulize_checkForLinks_oneToOneMetaData respond to inverse of one-to-many connections (check that nothing else keys off that) -- so that Massey won't need explicit one-to-one links for people in activities conditional one to one behaviour
• Make conditional one to one behaviour kick in based on inverse one-to-many connections (in formdisplay.php, where one to ones are added to the conditional connection)
• When making Primary Relationship, do not include elements that are not actually linked together (as in ESAT skills)
• Verify that programs linking to programs in ESAT is OK??
• Provide delete button on Details popup for onetoone links
• Enabling saving of primary identifier, necessary for automatic link creation when adding subform elements
• Add read out of the elements that actually do the joining, to the list of relationship connections
• Make default singular/plural creation apply plural/singular logic somehow??
• relationship UI needs revamping to use the "Each entry in X connects to One/Many entries in Y" format. One X --> one/many Y. As part of this, normalize the presentation and recording of relationship data (essentially, deprecate type 3, Many to One)
• Part of this that would make sense would be a "singular plural noun" setup part as part of the form creation process. ie: Provincial Record Form 12, noun "each entry is a: " 'Activity Log' plural: 'Activity Logs' or whatever. Let us use that for buttons in the screen creation, and relationships, etc
• Make singular/plural work smart enough to remove " Form" from the end of the name and put it back after.
• Properly show the Primary Relationship in the screen UI, even when the form is not contained in the relationship
• Test that cloning form works, and cloned screens are created correctly, with correct language

[jegelstaff]

Stretch goals:

• provide way of managing connections/links between forms, outside relationship UI? Or revamped relationship UI. Allow dragging forms to link them up, and prompt with wizard for connection details
• Add cookie to store user's pref for byname/custom sorting
• Default sorting to byname if no cookie
• Re-organize checkboxes to be cleaner looking vertical
• Remake form boxes to be simpler, highlight focus and give slide out options in panel
• Add a filter option to limit the forms that are shown
• Add metadata about entries, users, etc
• Provide one-to-one admin option in panel that triggers Primary Relationship one-to-one connection

Key thing is this would allow for more obvious one to one connection. But the utility of one to one is not obvious/easily surfaced in Formulize right now, so keeping it in existing relationship UI would be OK.

Make this an alternate sort/display order for the main form list.

[jegelstaff]

This needs reverting, we need the explicit value in the DB at all times, even though we're moving ahead with everything always being this way, and not worrying about the value, we want the data to be clean. (?) or have we/can we delete the field from the DB entirely and remove all references to it??

[jegelstaff]

We need to make the custom code detection smarter... if code folder has only one file, and there are code features to convert... needs to be its own function :(