DV6 integration
You are hereThe named preview for feature/dv6-integration: every green DV6 card lands here. Microsoft sign-in first, then the Aeries lab login.
Open →Everything you need to test this build: pick a walkthrough, sign in with a demo account and follow the steps. The same guide stays with you in the Lab QA panel inside the app.
Each environment runs its own build and database. Your current one is highlighted.
The named preview for feature/dv6-integration: every green DV6 card lands here. Microsoft sign-in first, then the Aeries lab login.
Open →Shared lab on Aurora PostgreSQL through Babelfish. Tailscale only.
Open →Shared lab on SQL Server, the reporting reference. Tailscale only.
Open →Every feature card keeps its QA walkthrough current as it changes. Start one to open the app with its steps beside you.
Issue detail has one side panel: Assignee with Change, Due date and one Save, then Acknowledge, Resolve and Ask Aeries Assistant. Acknowledge and Resolve apply one required note to every currently open record of the issue after a preview; they are not a separate issue state. Acknowledge means reviewed and left as-is on purpose: the dialog says so before you save, and acknowledged records leave the Open count for their own Acknowledged tab, never shown as Resolved. Existing assignment and permission behavior remains. Assign an issue to a staff member with a due date and check the deadline on the dashboard. The My notifications box at the bottom right has been removed; there is no notification inbox on screen for now. Open the Action history tab beside Affected records, refresh it and load older entries; try switching tabs with the keyboard and reopening a copied history link. With history loaded, the three-dot menu at the top right of Action history exports every action you can see that matches the search, across all pages, as CSV. Grouping eight separate issues into one assignment, escalation to a coordinator and issue comments are not available yet.
Test as admin test sysadmin
Open an issue behind a centered three-dot loader, then inspect its first affected-record page after the summary and records are ready, with student names when available. Each record row is one compact line pair: a one-line title (student name, Student #id when no name is available, or the record key) over a byline with the problem, student ID and age (on narrow screens the problem gets its own line). View Data and any differing assignment appear once a row is expanded. Use the ellipsis beside the tabs for CSV export of the tab and search on screen, and for rule history. Expand records, save a Resolve, Acknowledge or Dispute with one Confirm, and scroll for later pages without hiding loaded rows.
Test as admin
The dashboard shows issue descriptions, affected record counts and overdue dates in a compact list. Try the filters, open an issue, and export the filtered list as CSV (.csv) from the three-dot menu at the end of the filters. Check that the list, issue details and downloads contain only the schools and records you are allowed to see. In the full-screen app, one sidebar parent and the page title follow successful navigation, including issue detail, direct links and browser history; mobile navigation closes the menu and moves focus to the page title. Full screen and inside Aeries show the same single header: Data Validations above the page title.
Test as admin sysadmin
Ask the assistant about an issue or affected record, then try reopening an earlier conversation from History. Review any proposed fix before confirming; if the assistant is not configured, the drawer explains that.
Test as admin
Try the new student demographics page, save a permitted personal-information edit and check it after reopening. From an issue, use View Data to find and focus the field that failed; known fields are marked and focused, while unknown fields have no guessed marker or fallback message. Address editing is not available in this preview. Oct 10: the header photo is larger and the summary row lines up with the name; Edit only makes inputs of fields the server will save, and every other field stays plain text with no per-field Edit in classic link or (read only) note (use Back to classic at the top of the page to change those); one Save commits student fields and custom fields together or not at all. Editing remains Partial: the backend scalar allowlist is Personal-only; Address, Contact, Background and Language are read-only. New: an administrator can add custom fields to this page on the Custom Fields screen (/app#/custom-fields); they appear in a Custom fields section at the bottom and save with the page. The twelve Personal fields now save the way classic does (name cleanup, classic change log and detail rows). The server can save student fields and custom fields in one all-or-nothing request; this page still sends them separately until its own update lands, so a partial save is still possible from the page. New: the Siblings page is rebuilt in the same style (/app#/students/{studentId}/siblings). It lists the students who share the family key and, in the approved isolated preview, lets permitted staff match the student to an existing family, create a new family key or remove the student from the family. Only that student's family key changes. Oct 11: a sibling's name is a plain link on mouse, keyboard and touch, with no preview card, and opens that sibling's Demographics page at the sibling's own school; the pencil that edits the family key now sits inside the Family key chip (still named Edit family key); only Inactive and Pre-enrolled students show a status badge, an active student shows none, and a status the server did not return reads Status unavailable; Address & contact no longer shows a Validated/Not validated badge or a Verified date. SIS-246: this page now takes its layout styles and its student reads from a shared record-page base that later rebuilt pages will reuse; nothing on the page should look or behave differently. Oct 11: read-only values on the Demographics and Siblings pages copy when clicked (or focused and activated with Enter or Space), with a brief Copied! confirmation; links, inputs, placeholders and the verification pass code are not copy targets. Contacts: open the read-only Contacts page by URL and compare its list and order with classic Contacts. SIS-321: Go to field now leads to a fix. A field a data validation fails on that this page cannot edit says why next to its value (not editable on this page yet, with a link to classic Demographics); Birth city and Reporting lang. can be edited right there, and after Save changes the page rechecks the validation and names the ones that cleared. SIS-353: student photos on Demographics and Siblings load together instead of one after another, and opening a page again reuses the photos the browser already has once the server confirms you may still see them. SIS-355: Edit follows the district's Required Fields setup for the thirteen editable fields, as classic Save does: a required field shows * and cannot be saved blank, and Birth state is required only when Birth country is US, CA or MX. Classic's advisory warnings appear as notes that do not block Save: Birth state does not match Birth country, and a birthdate over 75 years ago. A current code that is no longer in the code list is shown instead of a blank choice. SIS-354: only staff with Data Validations access to a rule's group and school see the validation panel and its count; each row has a Re-check validation icon that shows Re-scanning, then still failing or could not re-check, or removes a cleared record from the list with a green notice. SIS-352: the photo now runs the full height of the name, school and facts block; the per-field blue Edit links are gone (double-click a field, or use Edit at the top right, which now reads Edit); View Data opens the page and goes to the failing field once it knows which fields you can edit; Reporting and correspondence language read code first (01 - Spanish) in the view and the picker, and other coded fields show their descriptions the way classic does, even when you cannot edit them; Unpin brings you back to the field with a brief blue outline; Clear in Pinned fields removes all your pins after a confirmation.
Test as admin test sysadmin
Open Feedback on any preview page, from the QA sidebar or from the minimized Lab QA control, crop and mark the shot, and write a note. Add several items as you move between pages, then submit them together.
Test as admin
One searchable table combines Aeries, district custom and CALPADS rules. A single filter row, matching the dashboard issue list, offers search, Type (Aeries, CALPADS, Custom), Category, Enabled (including retired references) and Provenance (Pete starter or Aeries lab). Each rule is one readable row: code and name, Source, Category, one status badge and the severity the district set. A click anywhere on a row opens or closes it, and several rows can be open at once. Each open row has one header (rule number, severity and state, with Edit, History and the on/off switch), then Description, Why this rule exists and How to fix it, with Advanced SQL. Verified shared catalogue identities appear once; distinct district instances remain separate. Starter activation is unavailable here. PR-only: native Windows and signed-in PR-head acceptance remain pending. Oct 11: Advanced: View SQL is a disclosure heading with a chevron; Copy SQL is a standard outline button with a brief Copied! confirmation and copies the stored SQL exactly. Oct 11 (SIS-264): no rule of any kind shows a filled light-blue panel in its open row. What a rule checks is ordinary text under the heading What this rule checks; a reference entry, or an entry with no lines, shows only its note. The blue edge down the left of the open row stays. Oct 12 (SIS-323): Enable Selected is hidden whenever the filtered table has no rules (a search or filter with no matches, while loading, or after a load error) and shown, still disabled, when rules are listed. Oct 13 (SIS-358): Advanced: View SQL shows the SQL formatted for reading, with each clause on its own line, indented conditions, CASE branches and subqueries, and coloured keywords, text values, numbers, names and comments. It is display only: Copy SQL still copies the stored text exactly, and nothing is saved or run.
Test as admin
The preview review panel shows this round’s name, full database name, Jira items and a guide for this build. Try opening the guide and a feature’s Jira item; a missing guide is explained plainly.
Test as admin
School Info > Data Validation (beta) opens Data Validations inside Aeries (/DataValidationV6.aspx), with the usual Aeries menu and header around it. Open full screen moves the same page to /app, the chromeless app with its own navy sidebar, and Back to Aeries returns to the same page inside Aeries. Links clicked inside either view stay in that view; a pasted /app link stays full screen. Dashboard, Rule Browser, Field Mapping, issue and student hash routes survive refresh and Back in both. The former /DataValidationV6App.aspx entry redirects to /app with query values and browser-inherited fragments. The same 13 Stories, sidebar and walkthrough mappings remain. The existing What's new dialog and record actions are unchanged.
Test as admin teacher sysadmin
Run a CALPADS practice check before submission and review its errors on the dashboard. The Certification card now counts down to the next official CALPADS certification deadline only from a reviewed copy of the CDE calendar, labeled with its source and school year, and shows the district's own ready-by milestones separately (SIS-147). Desktop width only this round.
Test as admin test
SIS-97: the same source-authored purpose and concrete next step in the rule browser, finding detail and assistant context. Missing guidance and unreviewed drafts stay conspicuous. New custom activation requires both fields. Review-only PR; signed-in deployed acceptance remains pending integration.
Test as admin
Field mappings show how CALPADS fields match Aeries fields. Try reviewing a suggested match and changing a permitted mapping, then check whether rules using it are marked for review. Oct 10: Field Mapping and Custom Fields are now built from the shared form kit; a lab-only gallery at /app#/lab/form-kit shows every control state.
Test as admin
Create a custom rule with the step-by-step builder and test it before activation. Try choosing a field and condition, review the written explanation, and check the sample results before saving.
Test as admin
Lab/demo accounts only. Passwords are never stored here; use the lab password you were given.