docs/admin-services.md

@@ -22,11 +22,3 @@ Button info as follows:
 |Update Licence Key| Link to the screen for providing a new Data Controller licence key|
 |Export DC Library DDL|COMING SOON!!  <br>Exports the data controller control library in DB specific DDL (eg SAS, PGSQL, TSQL) and allows an optional schema name to be included|
 
-## Licence Key Screen
-
-The licence key screen is where you apply or update your Data Controller licence key.  The following features are available:
-
-* **Paste both keys at once** - if you have received a combined key, simply paste it into the licence key field and both the licence key and activation key fields are filled in automatically.  You can toggle between the combined-key input and the traditional two-field layout.
-* **Preview before applying** - as soon as both fields are populated, the key details (expiry date, number of users, active features) are displayed so you can confirm the key is correct before clicking Apply.
-* **Protocol warning** - if you paste a key that was generated for a different connection type than the one you are using (http vs https), a warning is shown and the Apply button is blocked, preventing a key that will not work from being saved.
-

docs/cas-tables.md

@@ -39,10 +39,6 @@ Note that since the CAS connection is using a shared account, the CASUSER librar
 
 It can happen that a CAS table is configured in Data Controller but not loaded into memory. In this case, when a user selects the table, it will be automatically loaded.
 
-### REPLACE Load Type
-
-The REPLACE load type (which replaces all rows in the target table with the staged data) is supported on CAS tables.  This works the same way as it does for regular SAS datasets - see [MPE_TABLES](/dcc-tables/#loadtype) for general REPLACE documentation.
-
 ## Unloading
 
 After an approval, the in-memory version of the CAS Table will be updated.  To apply this to the underlying file on disk, the following code must be executed (eg in a POST APPROVE HOOK):

docs/deploy-viya.md

@@ -130,17 +130,6 @@ Now the services are deployed (including the service which creates the staging a
 * Admin Group - the members of this group will have full access to Data Controller
 * Compute Context - the context configured in Step 1
 
-!!! note
-    On the first-launch configuration screen, the **Groups** dropdown shows your own groups first, the **Contexts** dropdown groups contexts by their batch user, and a **Verify** button lets you confirm the startup service is running before continuing.  If no admin groups are found, a clear message is shown instead of the screen hanging silently.
-
-### Deploy Checks
-
-The deploy process runs additional checks during installation to catch configuration issues early.  For larger Viya environments, the deploy script is chunked for reliability.  The compute context is also automatically corrected during deploy if needed.
-
-!!! note
-    A debug comment is added to the compute context during deploy.  This is permanent - it is not removed by subsequent deploys.
-
-
 ### Optimisation
 
 At this point, every DC request will read the `services/public/settings.sas` file to get the DC library (and other) settings.  To avoid these API calls (which will speed up the app) we can simply move this code to the autoexec.  Steps as follows: