Files
Project-SDE-WP-Suite/docs/waves/decisions-2026-10-12.md

5.0 KiB

Decisions: October 12, 2026 (meeting with Nick)

Topic: mobile app (offline Field View), batch print, and related scaling questions. Recorded by Matt Mabrey from the meeting with Nick, 2026-10-12. Follow-up answers from Matt are in the section "Follow-up answers".

This file records the answers. It does not schedule any work. The features that come from these answers are logged in docs/waves/backlog.md as BL-062 to BL-068 for a future build. The path to a mobile version that works outside the VPN is in docs/waves/roadmap-mobile-scaling.md. None of these have a wave or a CR- or D- id yet. Assign the ids when a wave is planned.

Question numbers (Q2 to Q14) come from the decision table that Matt received. Q1, Q10, and Q11 were not in the table. They are not recorded here.

Answers

Q Decision needed Default that was proposed Answer
Q2 Days the app may open offline after the last sign-in (today: 12 hours) 7 days. Wipe a disabled account's data on the next online open. 7 days. The default wipe rule stands.
Q3 Must planners edit in the creator offline, or only crews in Field View? Field View only Only crews in the field. The creator needs no offline mode.
Q4 An offline edit meets a newer server version. What does the crew see? Keep both, show differences, crew chooses. Server wins if nobody acts. Merge with a notification. Log it. Update the owner. If the same field changed on both sides, the field value wins, and the app keeps a history of changes. This replaces the default.
Q5 Photo limit per photo and per package Resize to 1280 px, 50 per package 5 MB per photo.
Q6 Maximum packages in one batch print 50, with a message to narrow the filter 25 on phones. On desktop the user can scale the filter up to 50 or 100.
Q7 Where drawings go in the PDF, and at what size After the form, upload order, scaled to fit After the form, upload order, scaled to fit. Same as the default.
Q8 SVG drawings in the merged PDF Leave out, with a page that names the file Leave out, with a page that names the file. Same as the default.
Q9 What goes on every page Package no., print date, page X of Y Package no., print date, page X of Y. Same as the default.
Q12 Progress weight for Ready for QA (today 0, so a package drops from 75% to 0%) 0.85 0.85. Same as the default.
Q13 What happens to a package's drawings when the package is deleted Delete with the package Keep them (data retention). The storage quota is freed. Storage will move to cloud storage in a future deployment. This replaces the default.
Q14 Which cost-code list is correct (creator has 38, SOP has 39, 13 differ) One list in the SOP. Needs codes from Accounting or the PM. One list in the SOP. The PM supplies the codes.

Follow-up answers (Matt, 2026-10-12)

These answer the six questions that were open after the first record.

  1. Q5: the 5 MB limit is per photo. This matches the limit that already exists for drawings (D8, enforced in server/app.py: 5 MB a file, 2 GB per project).
  2. Q6: 25 on phones. Desktop users can scale up (50 or 100).
  3. Q4: on a conflict in the same field, the field value wins. The app keeps a history of changes.
  4. Q13: the quota is freed. Cloud storage will hold the kept files in a future deployment.
  5. Q14: the PM gives the codes.
  6. Scaling: Matt asked for a path to a mobile version that scales to multiple projects, outside VPN access, for field agents on phones and tablets on site. That path is in docs/waves/roadmap-mobile-scaling.md.
  7. Who uses it: all end users will eventually be in the Okta group.
  8. Scale: expect multiple customers. The data model needs a customer (organization) level above a project. See Phase 4 of the roadmap.
  9. Devices: company-managed.

Still open

  1. Q5: the count of photos per package, and whether the app resizes a photo before upload. Phone photos are often 3 MB to 8 MB. A 5 MB cap per photo with no resize will reject some normal photos.
  2. Q4: who "the owner" is (package owner, project owner, or the person who made the server change). Also: how long the history of changes is kept, and who can read it.
  3. Q13: how long a kept drawing is retained, who can delete it for good, and who can recover it. The quota is freed, so the retained bytes must not count toward the 2 GB project limit. Decide where they are counted instead.
  4. Q14: the date the PM gives the codes.
  5. Q6: who sets the larger desktop limit (each user, or an admin setting).
  6. The questions in roadmap-mobile-scaling.md, section 7 (nine open). The first two (one person on more than one customer, and the isolation model) change the data design. Answer them first.

Source

Meeting with Nick. Status column in the original table: "Open. Team builds to the default" for every row, as of October 12. The answers above came after that status.