Changes between Version 121 and Version 122 of ReleaseNotes

Timestamp:

22.05.2015 00:58:32 (10 years ago)

Author:

jri

Comment:

4.6 release notes, pt. 2

ReleaseNotes

@@ -14 +14 @@
 * **Refined //Contacts// model**: the intermediate `Address Entry` and `Phone Entry` topic types/instances are gone. A person/institution is connected //directly// to its `Address` and `Phone` topics via a custom association. The `Address Label`/`Phone Label` are attached to the custom association (#779).
 * Webclient usability:
-    * when clicking a topic in the detail panel which has more than one association to the selected topic only one association is revealed (instead of all), nameley the one that corresponds to the clicked list entry. This reduces the chance for selecting the wrong association on the canvas afterwards (#460).
+    * The detail panel's vertical scrollbar position is saved/restored on a per-object basis (#783).
+    * When clicking a topic in the detail panel which has more than one association to the selected topic only one association is revealed (instead of all), nameley the one that corresponds to the clicked list entry. This reduces the chance for selecting the wrong association on the canvas afterwards (#460).
     * The sensitive area of the detail panel's resize-handle is increased from 2 pixel width to 7 pixel width (#676).
-* In the //New Workspace// dialog the radio buttons to select the Sharing Mode show a tooltip that provides help for each option available (#784).
-
-Bug fixes:
+    * In the //New Workspace// dialog the radio buttons to select the Sharing Mode show a tooltip that provides help for each option available (#784).
+* DM never creates empty simple child topics. In particular a combobox menu is not extended by an empty item when the field (e.g. "Phone Label", "City") is left empty (#171).
+* In Number fields the Webclient does not fill in 0 automatically anymore as 0 and "not set" are semantically different (#171).
+
+Bug fixes:
+* The user can't select disabled menu items. In particular a user who is not permitted to create a Membership can't do so (#774).
 * A type can't be deleted if instances still exist. If tried an error message is displayed (#789).
+* The DB is not corrupted when an association definition is retyped into a non-association definition type and then retyped back into an association definition (#773).
+* The standard type's (Note, Person, ...) Association Definitions (and their View Configurations) are editable by logged in users (#771).
+* Interactively created types get creator info and creation timestamp (#772).
 
 Plugin Development Framework:
 * Core module:
+    * **Error handling**: when an error occurs at server-side the exception (including all cause exceptions) is transmitted to the client. The Webclient reports the error to the user. Server-side plugin developers can supply custom error objects. Client-side plugin developers (that is users of the RESTClient) can supply custom error handlers (#790).
     * The model object used to create/update a composite topic/association can contain the values (simple or composite) to be used to update the //relating associations// as well (#785).
-    * **Error handling**: when an error occurs at server-side the exception (including all cause exceptions) is transmitted to the client. The Webclient reports the error to the user. Server-side plugin developers can supply custom error objects. Client-side plugin developers (that is users of the RESTClient) can supply custom error handlers (#790).
-    * Topic references are supported for //Composition// as well (#786).
+    * The JSON format for a declarative migration is extended in order to create the entities in a specific order (#778).
+    * REST APIs: the `include_assoc_childs` query parameter controls weather the child topics of the requested object's //Relating Associations// are included in the response (#659).
+    * Orthogonality:
+        * //Topic references// are supported for //Composition// as well. Topic references are supported for all the 4 cases, that is composition/aggregration, one/many (#786).
+        * An update operation supports //topic deletion references// for composition-one and aggregation-one childs as well. Topic deletion references are supported for all the 4 cases, that is composition/aggregration, one/many (#171).
     * Bug fix: `ChildTopics` manipulator methods work for child topics defined with cardinality //many// (#788).