dc
d81967e6a1
Both were hangovers from the earlier deployment flow. adminGroup is a DC setting (DC_ADMIN_GROUP, shown on the System screen), not a tag attribute. Its only readers were the deploy form's default in deploy.component.ts and manual.component.ts, and both already fall back to SASAdministrators when it is absent, so the fallback is now the whole logic. hotLicenceKey was the Handsontable licence key. The customer's own key arrives in the decrypted licence (hot_license_key), so the client carries the free-tier default itself and no longer reads it from index.html. With neither attribute on the tag, the boot-screen dump has nothing to hide: HIDDEN_TAG_ATTRIBUTES is gone and every attribute is shown, so a wrong or misspelt one is visible. That closes the review finding on hiding adminGroup. The missing-tag branch also records why it carries no error state, closing the other carried finding.
70 lines
2.4 KiB
HTML
70 lines
2.4 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<title>Data Controller</title>
|
|
<!-- <base href="/"> -->
|
|
|
|
<!--
|
|
SAS VA data-driven content: earliest-possible message capture runs before
|
|
Angular bootstraps. It is the `va-early` global script bundled via
|
|
angular.json (src/assets/va-early.js) and auto-injected here at build time
|
|
— external (not inline) so it passes a strict CSP, and it self-guards on
|
|
?embed=va so it is inert in normal use. See
|
|
VaMessagingService.replayEarlyMessages.
|
|
-->
|
|
|
|
<!-- meta tags -->
|
|
<!--
|
|
NOTE: Data Controller must run entirely offline / on-prem. Never reference
|
|
external assets (fonts, images, scripts, styles, CDN links, or remote
|
|
og:/itemprop URLs) here or anywhere in the built product. All assets must
|
|
be bundled and served locally.
|
|
-->
|
|
<meta name="description" content="Capture, Review, and Approve" />
|
|
<meta itemprop="name" content="Data Controller for SAS®" />
|
|
<meta itemprop="description" content="Capture, Review, and Approve" />
|
|
<meta property="og:type" content="website" />
|
|
<meta property="og:title" content="Data Controller for SAS®" />
|
|
<meta property="og:description" content="Capture, Review, and Approve" />
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
|
<link rel="icon" type="image/x-icon" href="images/favicon.ico" />
|
|
</head>
|
|
|
|
<!--
|
|
## SASJS Adapter config details ##
|
|
|
|
* appLoc: The location in metadata or SAS drive where DC will be deployed
|
|
* serverType: either SAS9, SASVIYA or SASJS
|
|
* loginMechanism: Use 'Default' for regular (user/pass) logins, or 'Redirected' for 2FA/SSO
|
|
* debug: Whether to enable debug on startup
|
|
|
|
## Viya only settings ##
|
|
* dcPath: The physical location in which to deploy the staging area (Viya only)
|
|
* useComputeApi: Connection method (Viya only)
|
|
* contextName: Compute Context (Viya only)
|
|
|
|
The admin group is not configured here - it is a DC setting (DC_ADMIN_GROUP),
|
|
shown on the System screen.
|
|
|
|
-->
|
|
|
|
<sasjs
|
|
serverUrl=""
|
|
appLoc="/Public/app/dc"
|
|
serverType="SASJS"
|
|
loginMechanism="Redirected"
|
|
debug="false"
|
|
useComputeApi="null"
|
|
runAsTask="true"
|
|
contextName="SAS Job Execution compute context"
|
|
>
|
|
</sasjs>
|
|
|
|
<body cds-theme="light" class="m-0">
|
|
<my-app></my-app>
|
|
</body>
|
|
</html>
|