dc
3467322e99
A range rule coerced both the cell value and its own value with parseFloat, so a special missing in either place compared as NaN. MINVAL rejected a blank and a special missing and MAXVAL accepted both, which made the two rules disagree with each other, and a range written in special missings - MINVAL .A with MAXVAL .C - compared nothing at all: every number failed and every missing passed, so .D was as acceptable as .B. Both sides are now keyed into the order SAS itself uses for a numeric variable: every missing sorts below every non-missing value, and the missing values are ordered ._ then the regular missing then .A through .Z. MINVAL .A with MAXVAL .C therefore takes .B and refuses .D, a blank fails a floor of .A, and a number sorts above every missing - it passes a floor of .A and fails a ceiling of .C. This supersedes the earlier "a range rule ignores a missing value" change in this branch: a missing is not outside the order, it is at the bottom of it. A rule value that is neither a number nor a special missing satisfies nothing, so the column fails until the rule is corrected.
Data Controller for SAS
Control your manual data modifications!
Alternatives to Data Controller include:
- 💾 Developing / testing / deploying / scheduling overnight batch jobs to load files from shared drives
- 🔒 Opening (and locking) datasets in Enterprise Guide or SAS® Table Viewer to perform direct updates
- ❓ Asking a #DBA to run validated code after a change management process
- 🌐 Building & maintaining your own custom web application
- 🏃 Running #SAS or #SQL updates in production
Problems with the above include:
- Legacy 'black box' solutions with little to no testing, documentation or support
- End users requiring direct write access to critical data sources in production
- Upload routines that must be manually modified when the data model changes
- Breaches due to unnecessary parties having access to the data
- Inability to trace who made a change, when, and why
- Reliance on key individuals to perform updates
- Building bespoke ETL for every new data source
- High risk of manual error / data corruption
Data Controller for SAS® solves all these issues in a simple-to-install, user-friendly, secure, documented, battle-tested web application. Available on Viya, SAS 9 EBI, and SASjs Server.
An individual Viya deploy can be done in just 2 lines of #SAS code!
filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/viya.sas";
%inc dc;
For a multi-user deploy, using a shared system account, please see deploy docs.
For further information:
- Main site: https://datacontroller.io
- Docs: https://docs.datacontroller.io
- Code: https://code.datacontroller.io
For support, contact support@4gl.io or reach out on Matrix!
Development
Lighthouse CI
This project includes automated Lighthouse performance and accessibility checks that run on pull requests. The checks ensure:
- Accessibility Score: Minimum 1.0 (100%) median score across all tested pages
The Lighthouse CI workflow:
- Sets up the development environment with SASjs server and mocked services
- Builds and serves the Angular frontend
- Installs Chrome and runs
lhci autorun(Lighthouse CI) against key pages - Uploads results as artifacts for review
To run Lighthouse checks locally:
cd client
npm install
npm run lighthouse
Configuration is in client/lighthouserc.js (URL list, desktop preset, Chrome flags, assertions).