Differences

This shows you the differences between two versions of the page.

Link to this comparison view

releases:lpdc:11.3.4561 [2026-06-22 21:57]
Pontus Netler created 		releases:lpdc:11.3.4561 [2026-06-22 22:10] (current)
Pontus Netler
Line 26: Line 26:
   * **The alternatives menu is always reachable with a right-click.** On a field whose arrow button opens the search dropdown, the menu of alternatives - recent values, the related-to-you shortcuts, open and unlink, and so on - could not be opened at all. A right-click on the field now always opens that menu, while the arrow button keeps its usual behaviour.   * **The alternatives menu is always reachable with a right-click.** On a field whose arrow button opens the search dropdown, the menu of alternatives - recent values, the related-to-you shortcuts, open and unlink, and so on - could not be opened at all. A right-click on the field now always opens that menu, while the arrow button keeps its usual behaviour.
  
-  * **Option-constrained fields no longer offer ways to set an invalid value.** For a field limited to a predefined set of options, the menu no longer shows "Search..." or "New...", since either could set a value outside the allowed set. Together with the valid-only filtering above, every choice the menu offers stays within the field's permitted options.+  * **Option-constrained fields no longer offer ways to set an invalid value.** For a field limited to a fixed, predefined set of options, the menu no longer shows "Search..." or "New...", since either could set a value outside the allowed set - and this now holds however the menu is opened, including the right-click menu on a field whose arrow opens a dropdown. A relation that is merely narrowed by an option query is not treated as such a fixed list: it keeps "Search..." and "New...", and its dropdown search now applies that option query so only the permitted records are offered. When a field's allowed options resolve to an empty set, the menu shows a disabled "No matches" rather than appearing empty. Together with the valid-only filtering above, every choice the menu offers stays within the field's permitted options.
  
   * **Filter validation explains a withheld related value instead of showing a bare number.** When you check a filter with the validation report, a condition pointing at a person or coworker record showed only that record's numeric id, with no name and no hint why - looking the same as a value that had failed to resolve. The report now marks such a value with the record's type and notes that the name is withheld for privacy (for example "60201 (Coworker - hidden for privacy)"), so it is no longer mistaken for a fault. The name itself is still kept out of the report.   * **Filter validation explains a withheld related value instead of showing a bare number.** When you check a filter with the validation report, a condition pointing at a person or coworker record showed only that record's numeric id, with no name and no hint why - looking the same as a value that had failed to resolve. The report now marks such a value with the record's type and notes that the name is withheld for privacy (for example "60201 (Coworker - hidden for privacy)"), so it is no longer mistaken for a fault. The name itself is still kept out of the report.
  • Last modified: 2 days ago
  • by Pontus Netler