Commit Graph
17 Commits
Author SHA1 Message Date
dc 6af7692f97 docs(embed): review pass before the release
- the link to va-messaging.service.ts opened with a backtick and closed with a
  quote, so it rendered as broken text
- the URL example was a plain URL wrapped in backticks inside a fenced block,
  which shows the backticks; it is a text fence with the bare URL now
- restored the space the "updated- all from inside the same report" sentence lost
- closed the sentence about brush columns, and spelled out "primary key columns"
- two causes the banner reports were missing from the table: an entry with no
  parameter before the "-", and a parameter mapped to two columns (the first
  entry wins). Both come from parseVaParmap, so the table now covers every
  message the banner can carry.

Checked against the merged code on release/7.20 (00df87f): the embed values and
their effects, the split at the last hyphen, the case-insensitive label match,
the plain-SAS-name rule, the anchor and period names, and the banner wording.
Tables are consistent, fences balanced, page is ASCII only, and both cross-links
(/filter/ and /developer-guide/browser-variables/) resolve.
2026-10-28 17:14:27 +00:00
dc 6367ed2f43 docs(embed): the object runs as the viewer, who must be a DC user
Found by testing a report against a freshly configured instance: the DC
object showed its login card inside the report because the viewer's SAS
identity was not registered yet, which reads as a broken embed rather than
a permissions problem.
2026-10-28 15:44:29 +00:00
dc 91c49a27c5 docs(embed): a configuration walkthrough for the VA Report Designer
Replaces the two-sentence section with the steps a report author needs:
where the URL goes, that the parameter has to be bound into the object's
query or VA never sends it, and how to tell a working mapping from a broken
one when the report runs. Also drops the note about intnx argument names,
which was explaining a decision rather than the behaviour.
2026-10-28 13:07:22 +00:00
dc 24e088d663 docs(embed): show the mapping, the warning banner and a date anchor
Screenshots taken against the demo estate with a licence key installed, so
no evaluation banner appears. The banner section now tabulates every cause
the editor reports, because the reader is the report author looking at the
Data Controller object and the URL is the only thing they can edit.
2026-10-28 12:59:22 +00:00
dc d4e7c26f13 docs(embed): the mapping key matches the parameter label only 2026-10-28 12:32:42 +00:00
dc 4623bfa5e2 docs(embed): document va_parmap date anchors 2026-10-28 11:53:23 +00:00
dc 73222aa9bd docs(embed): drop the jargon, name the header and navigation instead 2026-10-28 10:52:17 +00:00
dc 17bdecff89 docs(embed): describe everything va mode changes, not just the Filter button 2026-10-28 10:51:37 +00:00
dc 75a97e6300 docs(embed): say why the Filter button is hidden in va mode 2026-10-28 10:47:46 +00:00
dc b88002a752 docs(embed): document va_parmap, the mapping warnings and the Filter button per mode
The SAS Visual Analytics Embed page now covers mapping report parameters to
DC columns from the URL, which the name-based match cannot do for two report
objects filtering the same column from differently-named parameters.

- new "Mapping parameters to columns" section: the `va_parmap` grammar, the
  lower-case example, what overrides what, and the rules that matter to a
  report author (last-hyphen split, label-then-name key matching, one parameter
  to one column, no fallback to the name match)
- the warning banner is documented next to it, including that a parameter is
  ignored rather than filtered on the wrong column
- the `?embed=` table now shows the Filter button per mode, so it is explicit
  that `embed=true` keeps Data Controller's own filter builder while `embed=va`
  hands filtering to the report
2026-10-28 10:47:14 +00:00
dc c7626b2797 docs(developer): a page for the browser variables, and links from where they are used
browser_info and browser_url_vars were only described inside the troubleshooting
page, under Support Diagnostics. That is the right place to find them if you
already know they exist and are looking for a log line; it is not where anyone
looks when writing a hook, which is what they are mostly for.

The new Developer Guide page carries the whole subject: which services receive
the two tables, the column lists, the debug values per platform and the MPEINIT
log lines, reading them from a hook with the exist() guard, and the reminder that
they are client-supplied and so diagnostics rather than a security boundary.

Troubleshooting keeps three stub headings - browser_info, browser_url_vars,
reading-them-from-a-hook - pointing at the page, so the anchors that are already
published keep resolving, and the detail is not maintained twice.

Linked from the three places a hook author actually starts: the HOOK Scripts
section of the MPE_TABLES page, the pre-edit hook guide (where the editor's
inputs are listed), the two-rule-sets guide (post-edit hook), and the VA embed
page, where embed=va is exactly the kind of thing a hook wants to branch on.
2026-10-26 11:42:35 +00:00
dc-bot 1d0cfd6681 docs: document v7.13.0 features
- Live formulas (HARDFORMULA/SOFTFORMULA) in dcc-validations with operator-friendly explanations
- MPE_VALIDATIONS table doc: add HARDFORMULA/SOFTFORMULA to RULE_TYPE values
- Roadmap: mark Frontend Formulae and Regex Rules as delivered
- SAS VA Embed: document Live vs Confirm filter modes
- ViewBoxes: document edge/corner drag resizing
- Licensing: combined-key paste, key preview, protocol warning
- CAS Tables: REPLACE load type support and temp table cleanup
- Editor: native date/time pickers, paste-validation overlay, row status indicators
- Stage page: Formatted/Unformatted toggle on the approvals screen
- Viya deploy: configurator improvements, deploy checks, login page UX
- Index page: add live formulas and VA embed to features list
2026-09-03 17:25:40 +00:00
allan 0590191ff4 feat: updates for v7.10 release
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 2m31s
2026-07-13 18:23:00 +01:00
allan 964434af0a fix: link
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 58s
2026-07-01 13:14:29 +01:00
allan dec5f239de fix: embed va
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m4s
2026-07-01 13:12:22 +01:00
allan 80cabc7312 fix: va page
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m46s
2026-07-01 12:23:08 +01:00
allan ddd5866484 feat: 7.9 updates
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m48s
2026-06-30 13:42:06 +01:00