docs(7.19): publish derived variables - banners off, nav titles clean, roadmap entry

Held until the release lands: the draft banner on both derived pages, the
(draft) suffix in the nav, and the Delivered Features entry they were waiting
for. Merge this with, or just after, dc/dc#348.

docs/derived-variables.md

@@ -6,11 +6,6 @@ description: Derived variables are computed columns that appear in the EDIT scre
 
 # Derived Variables
 
-!!! warning "Draft - not in a release yet"
-    This page describes a feature that is in development. It is published early so
-    the wording and the screenshots can be reviewed; the behaviour described here
-    ships in the next release.
-
 A derived variable is a column that does not exist in the target table, but is computed when the table is loaded into the [EDIT screen](/dc-userguide/#editor). It is read-only, it appears after the physical columns, and it can be filtered on like any other column.
 
 Derived variables are useful when users need to work with a value that is a function of the stored data - a banding, a concatenation, a calculation - without changing the table, the load process, or the ETL.

docs/roadmap.md

@@ -45,6 +45,10 @@ Described [here](https://docs.datacontroller.io/api/).
 
 Below are some examples of Features that have been requested (and delivered) into Data Controller.
 
+### Derived Variables
+
+Columns that do not exist in the table - a banding, a concatenation, a calculation - can be configured per table and appear in the EDIT screen, read-only and filterable, without changing the table or the load process. Nothing derived is stored.  See [docs](/derived-variables)
+
 ### Column Level Security
 
 The columns that can be VIEWed or EDITed are now configurable.  See [docs](/column-level-security)

docs/tables/mpe_derived.md

@@ -6,11 +6,6 @@ description: The MPE_DERIVED table is used to configure computed columns that ap
 
 # MPE_DERIVED
 
-!!! warning "Draft - not in a release yet"
-    This page describes a feature that is in development. It is published early so
-    the wording and the screenshots can be reviewed; the behaviour described here
-    ships in the next release.
-
 The MPE_DERIVED table is used to configure derived (computed) variables - columns that are created when a table is loaded into the EDIT screen, so that they can be displayed and filtered on without being stored.  More details are available in the [user guide](/derived-variables/)
 
 The table is itself registered in [MPE_TABLES](/tables/mpe_tables/), so it is maintained through the EDIT screen with the usual review and approve workflow.