Skip to content

Maintain the Member/Employer/Local reference tables

As a Super User, I want to keep the code/lookup tables that back dropdowns across the rest of PRIZM current and correct, so that every other role sees accurate, consistent choices wherever those values appear (Demographics, Employer, Contract, and dues/rate screens).

Screen: Sidebar > MAINTENANCE > Administration / Member / Employer / Local

The Maintenance module is entirely Nonvisible to every role except Super User — all 7 other roles were crawled and confirmed to have no MENU-MAINTENANCE entry in their sidebar at all. Everything below is Super User's alone to maintain.

Maintenance groups its lookup tables into four outer tabs (Administration, Member, Employer, Local), each of which nests a second row of tabs for the individual code tables.

Administration — system-level config

  • Users — the account grid itself (see Provision a new staff user account) plus per-row Reset Password / Retrieve Password.
  • User Security — an "Add Local User" security-group screen; empty in UAT (no security groups configured yet).
  • Reference Tables — a single generic table that serves many different code types, switched via a "Reference Header" dropdown (e.g. 2FAMethod: BTH/Both, EM/Email, PH/Phone). Add Reference Detail adds a row to whichever header is currently selected.
  • Document Type / Document Type Security — the controlled vocabulary of document types (e.g. "Card SIgn") attachable elsewhere in the app, and which security group can View/Add/Delete each type.

Member — dropdowns that back Demographics and member records

  • Class, Department, Ethnicity Type — empty in UAT; populate before relying on these dropdowns elsewhere.
  • Member Status — the authoritative list of every status a member record can carry (31 real codes in UAT: UK/Unknown, ST/E Board Step up, DEC/Deceased, EXP/Expelled, RTW/Right to Work, WEL/Welfare Only, COB/Cobra, and more). Each row's Active / Is Withdrawal / Is Suspension / Hiring Hall Member / Auto Suspend checkboxes drive downstream business logic — for example, a status with Is Suspension checked affects suspended-member handling elsewhere in PRIZM.
  • Member Type — 9 codes (DIS/Disabled, OWW/Out of work, G/Retired-Gold Card, S/Suspended, R/Retired, D/Deceased, W/Withdrawal, I/Inactive, A/Active).
  • Role — 6 member-held roles (training, H&W Contact, President Bus. Mgr., Shop Steward, Legal Department, Business Agent), each with an Is Officer flag. This is a different list from the system login Security Role in Administration > Users — this one describes a role a member holds (e.g. "this member is the Business Agent"), not a system account's permissions. It's also the table that backs Members > Roles — see Manage a member's security roles.

Employer — dropdowns that back Employer and Jobsite records

  • Bargaining Unit At Employer, Department At Employer, Employer Building, Employer Type, Job Title At Employer, Work Location — all empty in UAT; populate before expecting these choices to appear on employer-related forms.
  • Contract Type — 1 row in UAT (SPECIAL / "Special Contract Type (OHF)").
  • Employer/Jobsite Contact Type — the richest of this group: 43 real rows (Accounts Payable H&W, Secondary BA, PAC/PEF, Primary, Labor Board Cert Number, Property Mgr1/Mgr2, Payroll, Health Welfare, and more) — the full enum of contact roles selectable at an employer or jobsite.

Local — dues, rates, and trade-code configuration

  • Bank Account — the accounts invoices/deposits post against (Bank Account Name, Fund, GL Code); 9 real rows in UAT. See the "Things to watch out for" note below — despite the name, these aren't literal external bank accounts.
  • Bargaining Unit — empty in UAT.
  • Dues Rate — the older, flat dues-rate model: 35 named rate types (COBRA FAMILY, ETF Book & Materials, Retiree Annual, HRA, H&W, Minimum Dues, and more), each with its own Effective Date, Period Type, and Member-Paid-Through rule.
  • Dues Rate V2 — the newer, wage-bracket model, scoped by a Select Date Range dropdown: 228 rows mapping a wage bracket to Monthly/Quarterly Dues with its own Effective/Expiration dates. Both models exist simultaneously — check which one a given dues calculation is actually reading from before assuming the other is authoritative.
  • Regions — empty in UAT.
  • Trade Code — the master trade-code catalog every Member/Employer/Contract "Trade Code" dropdown elsewhere in PRIZM pulls from; 821 real rows (WWOPE/Water Works Operator, WELD/Welder, WATOEA-G/Water Plant Class A-G, etc.).
  • Import Config — not a grid; a single settings panel of fuzzy-matching tolerance percentages (New Member %, Change Member %, Bad Translation %, Wage Percentage %, Employer Transfer %, Max Dues Payment %, Check Match %) used by the member-data import process.

File ImportUtility — a separate outer tab

Associates an import file configuration with a specific employer and/or jobsite (29 real mappings in UAT, e.g. "Able Engineering Services" → "ABLE - Clock Number"). Uses the same "Choose Employer" modal pattern as Employers/Contracts elsewhere in PRIZM.

Things to watch out for

Several of these tables are genuinely empty in UAT, not a filter bug

Class, Department, Ethnicity Type (Member); Bargaining Unit At Employer, Department At Employer, Employer Building, Employer Type, Job Title At Employer, Work Location (Employer); Bargaining Unit, Regions (Local) all show 0 rows in the UAT environment. Confirm with whoever owns that config before assuming it's broken — an empty reference table usually means it hasn't been populated yet for this environment, not that the screen is failing to load data.

Two separate 'Role' concepts live in this module

Maintenance > Member > Role (a member-held role like Shop Steward) and the Security Role dropdown on Administration > Users > Add User (a system login's permission set) are unrelated lists that happen to share the word "Role." Don't confuse one for the other when troubleshooting why a dropdown shows the wrong options.

Dues Rate is one 'manage dues rates at scale' problem, not one-off questions

Four separate tickets have landed on the Local > Dues Rate table over this project's history — a pagination failure that never reproduced on retest (closed not-recurring, but left open-but-dormant for months as a possibly-systemic flag before closing: IUOE-2457), a request to extend the table to higher rates (IUOE-2410), a recurring February Dues Rates Audit/rollup rate-change need (IUOE-2053), and a question about whether Dues Period can support multiple periods at once (IUOE-2251). Treat any new "how do I manage dues rates" question against this table as part of that same recurring maintenance pattern — pagination, range extension, periodic audits, and multi-period support — rather than a fresh one-off issue each time.

Reference Tables nests many code types behind one generic screen

Only 2FAMethod has been directly inspected under Administration > Reference Tables so far — the "Reference Header" dropdown almost certainly exposes other generic code types beyond that one. Check the dropdown's full option list before assuming a given code type isn't configurable here.

A \"Bank Account\" here is a logical grouping bucket, not a real external bank account

Despite the name, Bank Account rows (Bank Account Name / Fund / GL Code) don't represent literal external banking relationships or routing numbers — they're a logical way to group transactions for IUOE's own GL reconciliation, matching the signed Union BLR's own framing (User Story Scenario 2.1.1.7, "Create/edit bank deposit accounts... so that payments can be properly tracked to/from the correct account"). The "account" a deposit posts against (e.g. "Dues - Cash and Check," "Fed Pac - Fluidpay") is a named bucket tied to a Fund and GL Code, not a bank's own account number — see Post a payment and complete the deposit for where this gets picked from a dropdown day-to-day.

\"We need a new Bank Account for X\" is a Maintenance setup task, not a dev request

A real request to add a dedicated Bank Account for tracking Merchandise payments separately (so Merchandise deposits/GL activity could be reported on in isolation) was handled entirely as a Maintenance-screen setup — add the row here, then confirm deposits can be created against it and show up correctly in the Bank Deposit and GL Journal reports filtered by that account. Treat any similar "we need a new account for X" ask the same way: a config addition with a narrow verification step, not a feature build. (IUOE-2706)

Deleting a Bank Account has an open, unresolved report

A report that a Bank Account couldn't be deleted exists as an unconfirmed Phase-1 stub — if you hit a case where an existing Bank Account row won't delete, don't assume it's expected behavior (e.g. "in use" protection) without checking further; it may be the same still-open issue. (IUOE-1729)