The big news items for Data Controller since the last release are:
Version 5 also brings some additional goodies!
Thanks to the new MPE_COLUMN_LEVEL_SECURITY table it is possible to configure:
Rules apply to the specified DC Groups. When this mode is activated, it is not possible to:
More information is available in the documentation.
Previously it was necessary to dig out the relevant services to refresh the Data Catalog (all versions) or the Table Lineage (SAS 9 EBI only).
We now present links during the deploy process to speed up the initialisation of these features.
In Viya and SASjs Server, the session encoding is always UTF-8. For SAS 9 EBI however, the session can vary depending on the Locale - from WLATIN1 through to WLATIN9 and beyond.
Thanks to some updates in our JSON generator we can now support UTF-8 outputs even where the SAS session is not UTF-8.
This has always been possible in Viya and SASjs Server (assuming you can write to the necessary folders) but for SAS 9 EBI it was previously necessary to have SAS Management Console or Data Integration Studio (or access to Batch Tools) in order to import the SPK.
Our new deployment process for SAS 9 EBI simply involves running a SAS Program, meaning that you can deploy to any folder in metadata (as a streaming app).
For a full deploy though, you would still need access to the Web Server, in order to deploy the frontend...
Since the version 4 release we have been capturing ALL change history in a single audit table.
This has resulted in some voluminous output!
It is now possible (on a per-table basis) to configure alternative audit tables, or to switch the feature off completely.
If your Excel is password protected, just provide the password during import to unlock and ingest it. More information here.
We are informated that sometimes you would like to have the option to have FEWER options for inputting data! Who are we to argue. You can now disable the 'EDIT RECORD' dialog using this option.
We have replaced the "groups" column in the SUBMITTED / APPROVE / HISTORY tabs with 'SUBMIT_REASON' - which is even more reason to describe your submits!
Using this macro we now automagically colour the primary key fields in the VIEW menu.
The logic differs from the EDIT menu in that it looks for an actual, UNIQUE + MISSING index on the target table, as opposed to picking up the BUSKEY from MPE_TABLES.
We zapped a few of these, notable ones:
We've made the following changes to the data model:
The following items are on our radar for 2022:
If you'd like to see something extra or something else entirely, you can also engage us to build it for you! Our team specialises in SAS App Development.