doc

documentation/qsrvpage.dox

@@ -23,7 +23,9 @@ which is also the PV name.
 So unlike records, the "field" of a group have a different meaning.
 Group field names are _not_ part of the PV name.
 
-A group definition is split among several records.
+A group definition may be split among several records,
+or included in separate JSON file(s).
+
 For example of a group including two records is:
 
 @code
@@ -43,6 +45,23 @@ record(ai, "rec:Y") {
 }
 @endcode
 
+Or equivalently with separate .db file and .json files.
+
+@code
+# some .db
+record(ai, "rec:X") {}
+record(ai, "rec:Y") {}
+@endcode
+
+@code
+{
+    "grp:name": {
+        "X": {+channel:"VAL"},
+        "Y": {+channel:"VAL"}
+    }
+}
+@endcode
+
 This group, named "grp:name", has two fields "X" and "Y".
 
 @code

documentation/release_notes.dox

@@ -2,6 +2,14 @@
 
 @page release_notes Release Notes
 
+Release 1.3.0 (UNRELEASED)
+==========================
+
+- Changes
+ - Add dbLoadGroup() iocsh function to read group JSON definitions
+   from a file.  Mappings in files must refer to full record names
+   instead of fields.  eg. 'recname.VAL' instead of 'VAL'.
+
 Release 1.2.4 (July 2020)
 =========================