An edit screen holds one row and is the only place where data is changed. It opens from "Add", "Edit" or "Copy" on a [[Invantive Estate/Screens/Lists|list]], and from "Edit" on a [[Summaries|summary]]. A [[Invantive Estate/Screens/Lists|list]] and a [[Summaries|summary]] never change anything themselves. ## Groups and Fields The fields sit in groups, and each group is a box that folds open and shut. The first group holds the fields that identify the row. The groups after it gather a subject, such as "Contact information", "Address", "Social media" and "Other" on a person. A group defined for the subject but empty for this row is left out. A field is shown as the kind of control its content asks for. A coded field becomes a picklist that offers the values allowed, an amount and a percentage get their own editor, a date gets a calendar, and a field that refers to another subject gets a button that looks that subject up. A field the database derives itself is shown but cannot be typed in. ## Required Fields A field that has to be filled shows a red marker with the text "This field is required." as long as it is empty. The marker appears while the screen is being filled in, so a missing value is visible before saving rather than after it. The database checks the rules of the subject once more when the row is saved. A rule that is broken is reported as a message that names the field, and the row stays open for correction. ## Defaults of a New Row A new row does not start out completely empty: - A row added on a tab of a summary starts with the link to the row of that summary. A person added on the tab "Persons" of an organisation therefore starts at that organisation. - On top of that come the defaults of the subject itself. The gender of a new person, for instance, starts at "Unknown". - A row made with "Copy" starts as a copy of the original, with the fields that have to stay unique emptied. On a person these are the logon code, the database user, the LDAP user and the initials. - A row opened with "New from Same Organisation" on a [[Invantive Estate/Screens/Search|search]] result starts with the code and name of the organisation of the person found. The action is offered only for a search result naming a person. A default is a starting point and nothing more. Every defaulted field can be overtyped before the row is saved. ## The Language of a New Person or Organisation A person and an organisation each carry a language. Invantive Estate uses it among others for the messages it sends them. Both start with a language of their own accord, which saves a choice on every entry. Available from release 27.0. A new organisation takes the "Language" field from the group "Default Preferences New User" of the "Settings" screen. Nothing sits above an organisation to derive a better guess from, so the settings are the only source. A new person takes the language of the organisation the person is added at. When that organisation has no language of its own, or when the person is added without an organisation, the same field from the settings is used. That order of preference is the one the database follows as well when it decides in which language to send a message: first the language of the person, then the language of their organisation, and last the language of the settings. Up to and including release 26.0 both fields stayed empty and had to be filled in by hand. ## Closing the Screen "OK" saves the row and closes the screen. "Cancel" closes it without saving. Closing the screen in any other way while something has been changed leads to the question whether the change is to be saved. After saving, the screen that opened the edit screen fetches its data again, so the new or changed row is in view straight away. ## See Also - [[Invantive Estate/Screens/Lists|Lists]] - [[Invantive Estate/Screens/Search|Search]] - [[Summaries]]