Skip to content

Upload an Ultra X file

As a Membership Staff member, I want to close out a per-capita period and generate an Ultra-X export file for a date range, so that the International's Ultra-X system gets a correct batch of the Local's member status/demographic changes for that period.

Screen: Utilities > Create Ultra X Upload (the crawl's current build still labels this tab "Per capita/Ultra-X" — it was renamed from "Personify" at some point in PRIZM's history; same screen).

Membership Staff has Add/Update here, same as Super User — one of only two Utilities screens (the other being Merge Duplicate Members) where Membership Staff matches Super User instead of being limited. Every other role is Not Visible on this specific screen: Accounting, Contract, H&W Staff, and ETF Staff only get the general "Import"/"Import Status" screens in their copy of Utilities, which is a separate, unrelated set of screens — don't conflate a general Accounting import with Create Ultra X Upload. Business Agent and Management don't have the Utilities module at all.

What this screen does

Key fields: Start Date, End Date — both required (red labels). There's no grid here; this is a form, not a list view.

Actions available: Close per Capita Month, Create Ultra-X File, Cancel.

Both action buttons look like real batch-processing triggers — "Close per Capita Month" almost certainly mutates period-close state financial-report-wide. This is treated as a destructive/ mutating action: never run it against a real financial period without sign-off, and the crawl that documented this screen deliberately did not click either button.

e2e/crawl/docs/utilities.md has little more field/action detail for this specific screen beyond the above — it's a two-field date-range form feeding a batch process, not a screen with a lot of surface area to document further. There's no confirmed click-by-click walkthrough of what a completed Ultra-X file looks like once generated.

What the Ultra-X file is supposed to contain

Per the signed Union BLR, an Ultra-X upload for a given date range is supposed to:

  • Include all approved changes occurring in the date range, from e-board approval through "final" status.
  • Include configured status changes, correctly mapped to the International's status-change action codes.
  • Include demographic changes (e.g. address changes) that occurred in the reporting period.
  • Be delivered as a CSV so it can be edited locally if needed before it's submitted upstream.
  • Not include members who transferred in during the period — a Transfer-In member has to be entered into Ultra-X manually, separately from this upload.

Things to watch out for

A date on an UltraX record is an effective date, not an entry date — by design

USR_ACTION_EFFECTIVE_DATE in UltraX reflects when a change took effect, not when it was entered into PRIZM. This has already caused confusion in testing — a Local-field edit traced to Demographics (which has no effective-date concept at all) was mistaken for a reporting bug until Local/Class editing was moved to the Member Change History tab instead (shipped in PRIZM 2.17/2.18). Local 399 doesn't use "Class" — it can be left blank. JayStar itself recommended a dedicated UltraX reporting training session over this exact effective-vs-entry-date distinction, since more than one ticket has mistaken correct effective-dating for a defect. (IUOE-2217)

A related comment carry-over gap is still open, Phase-1-stub only

A report that an overscale comment on a member didn't carry over into change history/UltraX reporting is tracked as part of the same change-history-gap family as the effective-date issue above, but is still a Phase 1 stub with no confirmed repro or fix — don't assume it's resolved just because the effective-date ticket shipped a fix. (IUOE-2202)

Close per Capita Month and Create Ultra-X File are both destructive/mutating

Neither button has been exercised against live data in this project's crawl — both are understood to be batch-processing triggers that change period-close state and/or generate an upstream file, not read-only reports. Never click either without explicit sign-off, and never against a real financial period.

This screen is a strong candidate for its own dedicated training session

Given the effective-vs-entry-date confusion above and the fact that Transfer-In members need separate manual entry into Ultra-X, this is exactly the kind of screen where a short walkthrough with real (non-production) data would prevent repeat tickets — JayStar recommended as much when the IUOE-2217 fix shipped.