Follow-up to the previous commit on this branch, both wording fixes.
- The sentence this branch deleted was the page's only description of the row
count when no search is active - and that is the case where the count really
can exceed the rows displayed (viewdata reports count(*) for the filtered
view while the grid stops at DC_MAXOBS_WEBVIEW). State it, instead of leaving
the page silent on the path readers use most.
- "returns the first 500" claims an ordering the search does not apply: the
search is a WHERE clause with no ORDER BY, so which 500 come back is whatever
the engine hands over first. Say "returns 500 of them".
Checked against viewdata.sas and mp_searchdata.sas on main: the search path
passes outobs=DC_MAXOBS_WEBVIEW to mp_searchdata, which caps the result dataset
in the same data step that builds it, and viewdata takes its row count from that
dataset - so for a search the count and the rows are capped together.
frontend.zip now holds the frontend files at their root (dc/dc #147, released in
v7.14.2), so unzipping no longer produces a client/dist folder to navigate into.
Step 2 now says to create the app folder and unzip the archive into it, naming
the file that should end up there. Step 3's URL example matches the folder the
reader created, and the intro line drops "to the root of" - it contradicted the
subfolder instruction directly below it.
The row count next to the table name is the capped count, not the total
number of matches. A search that matches more rows than DC_MAXOBS_WEBVIEW
returns the first 500 and reports 500, so the count does not rise above the
cap even when many more rows match.
The example claimed `smith` finds `Smithson`, which only holds for a case
insensitive match. The search is a case sensitive CONTAINS match - DC passes
the search value straight to %mp_searchdata, which uses the SAS `?` operator -
so `smith` finds `Goldsmith` (a lowercase substring) and not `Smithson`.
The screenshot showed the siphonophore search returning 3 rows, but the
NOTES column - the only column the value appears in - was clipped off the
right edge, so the image did not show why those rows matched.
Re-captured at 1920x900 (all nine columns on screen, no clipping) from the
mocked instance, with the capture gated on an assertion that the matched
cell is inside the grid viewport.
The "Full Table Search" section said only that a search box exists. It now
states the behaviour that users actually hit:
- the search covers every column at once, character columns by case sensitive
CONTAINS and numeric columns by exact match
- the Numeric toggle switches to exact numeric matching
- an applied filter scopes the search
- results are capped by DC_MAXOBS_WEBVIEW (linked to the options page), and the
row count next to the table name reports the match count
- a search with no matches shows the "No data found with given conditions"
panel
Adds a screenshot of the search in action (docs/img/full-table-search.png),
captured from a running instance via the Cypress suite in the dc repo.
- dcc-validations: add MATCH() example showing why spaces matter around column names; document that new rows are 'A' from creation
- roadmap: move delivered Frontend Formulae and Regex Rules to Delivered Features section; reword 'necessary' heading
- deploy-viya: add trailing newline
- 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
allan
dc