September 29 mockup review
Review the request and procurement experience before shared-app implementation.
Browser mockup
Use example records to review these flows. Browser changes do not enter POs into Spectrum or send email. Shared-app integration and multi-user acceptance testing are separate steps.
Procurement review
Financial approval and entry into Spectrum are separate milestones. Review approved requests waiting for Procurement, mark an example as Spectrum ready, then confirm its status and the simulated requester notification. The pending-action view should show what still needs attention.
Delivery dates and taxes
Create a request with two lines. Enter the first delivery date, check that the next line defaults to it, then give the second line a different date. Save and reopen the request, and check the dates on the printable PO. Confirm the project tax defaults populate the first line.
For date sorting, the mockup uses the earliest known line delivery date. Individual date overrides should remain intact when the first-line date changes. Sourcing Need-By Date remains distinct from a vendor delivery promise.
PO and change identifiers
New base PO numbers use the two-digit year followed by five digits, without a hyphen. The built-in demo examples now follow this format too: rental 2600839, valve PO 2600712 and emergency 2600841. Saved demo references are updated when their identity is clear. Unrelated historical or imported numbers are preserved. Change requests should show a separate CO sequence alongside the original PO number, so the change is recognizable before opening the document.
Emergency requests should display their provisional PO number in the request list as well as details. Completing an emergency request should retain its reserved number.
Cost-code imports
Review the import preview with a representative CSV. Empty trailing rows and columns should not create a long mapping list. Populated but unrecognized columns should remain available for explicit review. Partial updates must preserve records that are absent from the file.
Agreed interim operation
- Procurement enters POs in Spectrum manually.
- Sourcing results can be returned by email. The requester decides whether and when to proceed with a purchase; sourcing completion must not imply an automatic purchase.
- Rod and Camillo avoid originating project requests until PM-review routing is verified in the shared app.
- Camillo can attach approved terms manually while the upload, selection and assembly flow is completed.
Per-line promised-date follow-up, Spectrum API integration, Stack AI extraction and analytics remain later work.
Before team testing
Agree the exact CO identifier format, final Procurement completion notification, approved terms assignments and controlled test recipients. Shared-service behavior must be verified with multiple users before rollout.