Fed Submit Release Log

2.0.0.509 changes

2.0.0.508 changes

2.0.0.507 changes

2.0.0.506 changes

2.0.0.505 changes

2.0.0.504 changes

2.0.0.503 changes

2.0.0.502 changes

2.0.0.501 changes

2.0.0.500 changes

2.0.0.499 changes

2.0.0.498 changes

2.0.0.497 changes

2.0.0.496 changes

2.0.0.495 changes

1. Title overlay rendering incorrectly on Fed Submit Mobile - `TopActivity.java` was updated to fix an issue with the title overlay display.
2. TIFF/JPEG codec support restored in Windows OpenCV build - The `opencv` submodule was bumped to re-enable TIFF and JPEG codecs in the Windows build, which had previously been disabled.

2.0.0.494 changes

1. `fsMobileTelemetrySimulator` (new project) - A standalone simulator that generates realistic mobile-transaction telemetry (`NormalScenario`, `LiveMode`, `SimulationModel`, `ModelValidator`, `SqlPersistence`, `StartupChecks`) for testing the new mobile telemetry dashboard without needing live field data. Ships with a database-create SQL script, a `Verify-SimulationRun.sql` verification script, a `README.md`, and a `BUILD_AND_DELIVERY_REPORT.md`. Refined over several follow-up commits (verification pass, simulator implementation updates).
2. Mobile transactions dashboard page - A new **Mobile Telemetry** page (`MobileTelemetry.cshtml`) added to the Telemetry dashboard, backed by a new `MobileTelemetryRepository` and `MobileOverviewModel`, giving a first look at mobile transaction volume and status alongside the existing site telemetry.
3. Agency filtering on the mobile telemetry dashboard - The Mobile Telemetry page can now be filtered by agency, with an accompanying `MobileTelemetry-AgencyReconciliation.md` doc describing how mobile transactions are reconciled to the correct agency.
4. Dashboard timed out opening a site with a very large heartbeat - Sites with unusually large heartbeat files could cause the site-detail page to time out. `DashboardRepository.cs` and the new `TelemetryTextParser.cs` were reworked to parse large heartbeats more efficiently, and a proper error page (`Pages/Error.cshtml` / `.cshtml.cs`) was added so a failure now surfaces a clean message instead of a timeout.
5. Repeated/recurring exceptions were inflating telemetry trends and health scores - Telemetry counted every occurrence of a repeated exception rather than counting each distinct exception once. `DailySummaryAccumulator.cs`, `TelemetryParser.cs`, `BatchRepository.cs`, `HealthScoreService.cs`, and `TelemetryIngestionService.cs` were updated to count **distinct** exceptions for both health scoring and telemetry trend reporting, so a single noisy/looping exception no longer disproportionately drags down a site's score or skews trend charts. Redundant/recurring reporting of certain exceptions was also cut down at the source.
6. Truncating very large heartbeats to 20,000 lines was losing the summary footer - When a heartbeat file was truncated to the 20,000-line cap, the important summary information at the bottom of the file was being discarded along with the excess middle content. `BatchRepository.cs` now retains the bottom portion of the file (where the summary lives) in addition to the head, when truncating.
7. Possible AV interference during image autocrop at Nolan - A site (Nolan) reported an image-processing issue suspected to be caused by antivirus software interfering with file writes. `FsImage.vb` hardens the write/confirm step before autocrop runs and now logs the file name on error, to better diagnose (and reduce the chance of) AV-related write timing issues.
8. Ingest history window extended - `TelemetryMonitor`'s mailbox backfill window increased from 180 to 225 days, so ingest history now effectively starts from 2025-12-31.
9. IB Scan Ultimate SDK upgraded to 4.4 - Updated native libraries (`libIBScanUltimate.so`, `libibscanultimatejni.so` for both arm64-v8a and armeabi-v7a) and the `iBScanUltimate-release.jar` on Fed Submit Mobile / Slapshot.

2.0.0.493 changes

1. InstallShield now packages the Release build configuration (previously Debug for historical reasons) - Installers are updated to package the Release build. Portable PDBs are still included, so full debugging capability is retained; no functional changes.
2. Installers were missing DLLs — 2.0.0.491 and 2.0.0.492 installs are broken; fixed here - The FedSubmit, IDMS, and RemoteID InstallShield/WiX packages (`Net481FedSubmit.wxs`, `Net481Idms.wxs`, `Net481Fscp.wxs`, `Net481CardServices.wxs`, `Net481CardWinServices.wxs`) were regenerated after reports of missing DLLs at install time; each of these installers was missing several required files in the 491 and 492 releases. Root cause: `fqboot.vbproj` referenced `Microsoft.SqlServer.DacFx`, which transitively pulls in `Microsoft.SqlServer.Types` (the native `SqlServerSpatial170.dll`, which is architecture-specific). `fqboot` only built `AnyCPU`, so consumers built as x86/x64 (e.g. FedSubmit) ended up pulling in `fqboot`'s `AnyCPU` output along with its `x86\`/`x64\`/`arm64\` subfolder copies of the native DLL, duplicating and in some cases conflicting with the root-level copy expected by the installer harvest step — resulting in the wrong (or missing) `SqlServerSpatial170.dll` being packaged. `fqboot.vbproj` now also builds dedicated **x86** and **x64** platforms (`<Platforms>AnyCPU;x86;x64</Platforms>`) alongside `AnyCPU`, so each consumer references the matching-architecture build of `fqboot` and only the single correct native DLL is copied into its output. All five installer `.wxs` files were regenerated against the corrected build output.
3. **If you installed 2.0.0.491 or 2.0.0.492, re-install using this (493) build** to pick up the corrected installer packages.
4. New `Telemetry` helper for no-PII Firebase analytics - A new `Telemetry.java` helper class adds structured Firebase Analytics event logging designed to avoid capturing personally identifiable information.
5. Telemetry constraints applied and wired to first three call sites - `Telemetry.java`, `Globals.java`, and `MtxHelper2.java` updated to apply the agreed-upon data-collection constraints and instrument the first three call sites. A new `AnalyticsDataCollection.md` doc records what is and is not collected.
6. Advertising ID and ad-consent defaults disabled - `AndroidManifest.xml` updated to disable the Advertising ID collection permission and set conservative ad-consent defaults, consistent with the no-PII analytics approach.
7. Better heartbeat delivery for infrequently-connecting sites - Sites with infrequent connectivity were sometimes missing their heartbeat window. `FTPRoutines.vb`, `HandleHeartbeatUtil.vb`, `Heartbeat.vb`, and `MentalixMAPI.vb` now retry with explicit TLS when the default negotiation doesn't succeed, and add a backup heartbeat attempt at process exit for very short sessions, giving low-frequency sites a better chance of registering a heartbeat.
8. Dashboard health scoring accounts for infrequent-heartbeat sites - `DashboardRepository.cs` / `HealthScoreService.cs` now treat a site with an infrequent-but-healthy heartbeat pattern as healthy in the download/health score, rather than penalizing it for the longer interval.

2.0.0.492 changes

1. MOBE transaction support in IDMS - `Submit.vb`, `IdmsBase.vb`, `IDMS.proto`, and `GrpcIdmsService.cs` add support for the new MOBE transaction type end-to-end. MOBE transactions now appear in the transaction view list. Two new engineering docs (`MobeAddSubmissionProof.md`, `MobeEnrollmentImplementation.md`) capture the design and submission-proof trace.
2. Mobile enrollment initial integration with contact capture - Checkpointed integration of mobile enrollment with the existing contact-capture flow on Fed Submit Mobile; the end-to-end enrollment flow is now working, including the biometric capture process and transaction handoff (`ExportBiometricCaptureProcess.java`, `MainViewModel.java`, `MtxHelper2.java`, `TopActivity.java`).
3. Mobile enrollment as an optional mode in Settings - A new setting on Fed Submit Mobile lets an agency enable/disable mobile enrollment as an available capture mode, with supporting UI in `SettingsFragment`/`SettingsManager`/`TopViewModel` and new strings/preferences.
4. Autoenroll coordination and cross-network locking - IDMS-launched autoenroll now waits for in-progress matching to complete before proceeding, and autoenroll locks transactions so multiple autoenroll runs across the network cannot race each other (`VfingEnroll.vb`, `IdmsBase.vb`, `fsIdmsGrpcWS/Service1.cs`).
5. Enrollment trace - Additional tracing added around the enrollment flow to aid diagnostics.
6. IDMS now pushes TOT specs to the mobile client via gRPC - New gRPC calls (`IDMS.proto`, `GrpcIdmsService.cs`) and a new `MobileSpecReader.vb` deliver transaction-type (TOT) specifications from IDMS to Fed Submit Mobile, backed by a new `MobileSpecTests.cs` unit-test project (`fsIdmsGrpcWS.Tests`).
7. **MOBE rule specs added** and mobile spec queries refined over several follow-up commits.
8. Demographic field specifications for IDMS-downloaded fields - Additional specification rules for demographic fields downloaded from IDMS to Fed Submit Mobile.
9. `MOBE_MOBILE_SPECIFICATION_SOURCE_TRACE.md` - New engineering doc tracing the source of each mobile specification value back through IDMS.
10. Ingest service running-state report and uptime - The Telemetry ingest dashboard (`TelemetryDashboardStarter`) now reports whether the ingest service is currently running and its uptime, via a new `IngestServiceMonitor` and `IngestServiceStatus` model surfaced on the dashboard home page (`Pages/Index.cshtml`).
11. OrderForm crashed on price-list items marked "Quote" instead of a listed price - Recently added price-list items have a `NULL` `Domestic Price` to indicate the item is quote-only rather than fixed-price. `OrderForm.vb`'s `AddPriceTableRow1` was calling `FormatCurrency` directly on the (null) price, which failed. Both the base price cell and the derived GSA price-with-discount cell now check `IsDBNull` and display **"Quote"** instead of attempting to format a null value.

2.0.0.491 changes

1. RISC and TXDPS responses properly received and displayed - `MtxHelper2.java` and `TopViewModel.java` significantly reworked to parse and surface search responses returned from both the RISC and TXDPS paths. A new `ExternalResponseClassificationTest` unit-test suite covers the response-classification logic.
2. "Stop Waiting" button - A button is now shown during active searches that lets the operator cancel waiting for a pending external response (RISC or TXDPS) without aborting the entire session.
3. DPS submit now conditional on RISC being enabled - The TXDPS submit step no longer fires unconditionally; it is only triggered when RISC is enabled in settings, matching the expected contactless pilot workflow.
4. Return-candidate presentation overhauled - `HitAdapter.java` substantially rewritten with new card-style result/source badge drawables, redesigned `hit_item`, `header_item`, and `footer_item` layouts, and color/style tokens for result presentation. The upper-left corner home-screen overlay issue was also addressed.
5. IDMS now authenticates Mobile ID clients via Firebase ID token - `GrpcIdmsService.cs` and `MtxHelper2.java` updated so the mobile app sends its Firebase ID token with each gRPC request; the IDMS service validates it before allowing access. This replaces the prior unauthenticated mobile path and ties each mobile search to a verified user identity. The mobile user’s email is now extracted from the token and logged against the search.
6. Mobile user email logging fixed - A bug where the authenticated user’s email was not logging correctly for mobile sessions was identified and resolved in `GrpcIdmsService.cs`.
7. `MobileSearches` database table - `IdmsBase.vb` and `GrpcIdmsService.cs` add a new `MobileSearches` table that records each authenticated mobile search with its owner identity, start status, and timing. Provides a durable ownership record that survives server restarts and allows the mobile client to reconnect to in-progress or completed searches.
8. `ListMySearches` gRPC endpoint - New RPC added to `IDMS.proto`, `IdmsBase.vb`, and `GrpcIdmsService.cs` so the mobile app can retrieve the list of searches belonging to the authenticated user (including status and result summary). `StartStatus` is correctly set to `Completed` when the transaction finishes.
9. `GetMySearchExternalResponses` gRPC endpoint - New RPC added to `IDMS.proto`, `IdmsBase.vb`, and `GrpcIdmsService.cs` that returns the durable external responses (RISC, TXDPS) stored against a search, allowing the mobile app to fetch results for searches that completed after the app was backgrounded or reconnected.
10. `GetIdmsStatusReply` and search-status message tuning - `IdmsBase.vb`, `IDMS.proto`, and `GrpcIdmsService.cs` significantly updated to carry richer status information (agency status, search status, response timings) in the IDMS status reply. Agency status and search-status display messages refined over several passes.
11. “My Searches” screen on Fed Submit Mobile - New `MySearchesActivity`, `MySearchesAdapter`, `MySearchesClient`, and `MySearch` model classes added to the Android app. The screen lists the authenticated user’s past searches with status badges and links to external responses. A new **My Searches** icon and nav entry added to the dashboard.
12. `AgencyIdmsQueueTrace.md` engineering doc - New documentation (`docs/AgencyIdmsQueueTrace.md`) added covering the full IDMS queue trace, hybrid state management, and detailed reporting of agency-queue transitions to aid support and diagnostics.
13. TCN free-up retried corrupt/missing EFT files on every restart - `FreeUpTcnForReuse` in `PubGlobals.vb` kept retrying TCNs with unreadable or missing EFT files after every service restart because there was no durable record that they had already been identified as bad. Two changes fix this:
14. A new **`EftStatus`** column (`VARCHAR(20) NULL`) is added to the `Submission Transactions` table at startup (idempotent `IF NOT EXISTS` guard). When a TCN’s EFT is found corrupt (FPU error codes `-121` buffer overflow, `-122` unexpected EOF, or `-123` corrupt field — `-122` was previously missing from the check) the row is immediately stamped `EftStatus = 'CORRUPT'`; a missing EFT file is stamped `EftStatus = 'LOST'`. Both writes use an independent connection so the mark persists even though the caller rolls back the outer transaction.
15. The step-1 candidate query now filters `AND ([EftStatus] IS NULL)`, so already-marked TCNs are excluded from all future restart cycles without accumulating in the in-memory skip sets.
16. **`Microsoft.Data.SqlClient` updated to 7.0.2** (from 6.1.2) — Required several consequential project-level changes to resolve compile issues introduced by the new client API. Installer manifests (WiX `.wxs` files) updated accordingly across all six installers (FSCP, FedSubmit, CardServices, CardWinServices, IDMS, RemoteID).
17. Broad .NET 10.0.10 package sweep - Multiple packages pinned to `10.0.0` were advanced to `10.0.10`: `Microsoft.Extensions.DependencyInjection`, `System.Collections.Immutable`, `System.Data.OleDb`, `System.DirectoryServices` (and `.AccountManagement`, `.Protocols`), `System.Drawing.Common`, `System.Management`, `System.Resources.Extensions`, `System.ServiceProcess.ServiceController`, `System.Speech`, `System.Threading.AccessControl`.
18. **`Microsoft.Xaml.Behaviors.Wpf`** → **1.1.142** (from 1.1.135)
19. **`Svg`** → **3.4.8** (from 3.4.7)
20. **`Microsoft.SqlServer.DacFx`** → **170.4.83** (from 170.2.70; the conditional `netstandard2.1` override removed — single version now covers all TFMs)
21. Installer manifests updated again to reflect the package sweep.

2.0.0.490 changes

1. RPISC EBTS transaction assembly - `IdmsBase.vb` `BuildRiscBase`/`BuildRisc` now build an RPISC transaction for the contactless path: a contactless flag and a `TOT_RPISC` constant force `TOT=RPISC`, omit `2.096 RPR`, and exclude Type-10/Type-17 records (an RPISC transaction is Type-1 + Type-2 + Type-14 only). `NSR`/`NTR` remain `00.00` per EBTS 11.2 (1.011/1.012 apply only to Type-4/Type-7; a Type-14-only transaction carries its resolution in 14.009/14.010).
2. Mandatory `14.901 FCT` stamped on contactless Type-14 - `FCT=1` is written on each contactless Type-14 record (mandatory when `14.003 IMP=43` per FBI Contactless Fingerprint Pilot spec v1.2 / ANSI-NIST SP 500-290e3). `NistType14Record.vb` preserves the FCT value and copies the permitted RPISC demographics.
3. EBTS 11.2 declared in the NIST session domain - `fpuSession.vb` bumps `1.013 DOM` from EBTS 11.0 to the current CJIS standard **11.2** for all .NET-built transactions (required for the RPISC pilot). A new **`EBTS_VERSION`** environment variable overrides the default (e.g. `EBTS_VERSION=11.0`) with no rebuild required, following the existing `WANT_NIST_*` override style.
4. RPISC response handling and independent RISC tracking - `IdmsBase.vb` / `TransactionProcessing.vb` now accept `RPISCR` responses and track the contactless RISC path independently of the standard RISC path.
5. RPISC validation on both submit paths - `TxdpsRuleSpec.vb` and `IdmsBase.vb` validate RPISC on both the desktop and the IDMS submit path.
6. RPISC routing through RISC submit / enrollment-exclusion paths - `Submit.vb`, `VfingEnroll.vb`, and `VfingMatcher.vb` route RPISC through the RISC submit path and exclude it from enrollment.
7. RPISC excluded from the matcher - `FsMatcherMT.vb` / `IdmsBase.vb` exclude RPISC transactions from the matcher load and local-candidate filters (contactless pilot submissions are not matched/enrolled locally).
8. gRPC endpoint hardening for RISC - `GrpcIdmsService.cs` now validates task ownership and guards against null RISC responses on the gRPC endpoints.
9. Contact + contactless capture both working - Contactless and fingerprint-scanner capture are now available on separate buttons, with settings controlling which (or both) appear. A crash when attempting more than one capture/search flow was fixed.
10. Agency setting for hardware finger-capture choices - On a contact scan there is no longer a need to select the capture type. The IB logo and SDK version were moved from the contact dialog into the About dialog.
11. Settings consolidation - Contactless recalibrate and calibration validation moved into Settings; the clumsy in-capture calibration functions and the contactless-express disable option were removed; contact spoof settings moved to the Settings dialog. Contactless instruction display can now be turned off via a setting, and the settings screens have more detailed explanations.
12. **Minimal demographics entry** added to Fed Submit Mobile (unneeded Skip button removed from demographics entry).
13. Startup / login flow - New splash screen at startup that shows the login screen if credentials are not yet approved, plus an optional biometric login screen at every startup (with opt-out). Logout now clears data; Reset clears preferences and attempts to return to the initial install state; a new screen shows all preferences at once.
14. Navigation & UI polish - Back button now works from the various contexts, the dashboard switched to an icon-based layout with improved icons and a better busy/searching dialog, and search now reports elapsed time alongside total hits at the end.
15. IB Scan Ultimate for Android updated to 4.3.0.
16. Type-14 index-only enrollment was dropping the right index finger - In `VfingLoad.EnrollNistFile`, the Type-14 loop tested the right index with `<>` instead of `=`, so in index-only mode (the default) it admitted every position *except* the right index; the thumb/index gate then narrowed to left index plus both thumbs, guaranteeing the right index was never enrolled. This affects 1000 ppi contact tenprints (which land in Type-14), not just contactless. The Type-4 path was always correct. Effect was degraded matching (subjects matched on ~half the intended evidence with lower fused scores), not an outright failure — which is why it survived since 2015. Fixed for future enrollments; already-enrolled subjects keep their template set until re-enrolled via `DoEnrollAll2`.
17. Uninitialized `deleteType7` in `nistdump GetNistFile` - The y/n prompt condition was inverted: the answer was only parsed when `gets_wrapper()` failed or returned empty, so a real answer never set the flag and `deleteType7` held indeterminate stack garbage. A nonzero garbage value would silently delete Type-7 records from the EFT rewritten to `submit.eft`. The answer is now parsed on success/non-empty and `deleteType7` is initialized to `0` at declaration.
18. `NumCompared` undercounted match threads - `FsMatcherMT.vb` now counts every match thread in `NumCompared`, not just threads that found a hit, giving accurate comparison totals.
19. Remote ID search aborting on transient failures - Fixed the Remote ID search aborting on transient progress-poll failures; the terminal search-results fetch is now retried, and a splash biometric hang at startup was fixed.
20. Contact print capture saved duplicate fingers - Fixed on Fed Submit Mobile.
21. TXDPS: ADD and AOL fields reject disallowed special characters - `TxdpsRuleSpec.vb` now allows only spaces (no other special characters) in the ADD and AOL fields per TXDPS specs, addressing a recent Lake Jackson MNC rejection.
22. Two RPISC regressions fixed - `IdmsBase.vb` regressions introduced by the RPISC validation and demographics commits were corrected.
23. FedSubmit services auto-restart on failure - `bsvc.vb` / `FsSearchItemsInit.vb` add automatic service recovery: the fs services auto-restart on failure and surface an actionable *"not available"* message instead of an opaque error. The same Windows service recovery actions were also applied to the `fsIdmsGrpc` service (`ProjectInstaller`).
24. `14.005 TCD` written and TOT/NSR/NTR derived from capture - `MtxHelper2.java` / `IdmsBase.vb` now write the mandatory `14.005 TCD` and derive `TOT`/`NSR`/`NTR` from what was actually captured.
25. `buildWorld` restarts the fs services it stopped - `buildWorld.bat` and `buildWorldFast.bat` now restart the FedSubmit services they stopped, including on build failure, so a failed build no longer leaves services down.
26. Android WSQ re-certification prep - Fixed the Android WSQ cert harness for the current `adb`, added a pending-cert rollover script, and bumped the ARM64 WSQ implementation number to **53042** for the 16 KB re-cert. Type-14 imagery is now compressed, annotated fingers declared, and all positions relayed.
27. RISC channel emulator (in progress) - Early scaffolding for a transparent RISC-channel emulator was added for testing; one-job/database test-design artifacts were removed to reset the emulator to a transparent-channel scope. (Internal test tooling; not part of the shipping product.)
28. **Noisy exception / logging cleanup** and multiple dashboard note updates across the release window.
29. Release automation: Bitvise remote commands base64-encoded - A recent `release_manager.ps1` change introduced a quoting issue: remote commands containing spaces, quotes, and shell metacharacters were passed directly as native arguments, but Windows PowerShell does not escape embedded double quotes, so the command line handed to `sexec.exe` (and ultimately the remote `bash -c`) became malformed — producing *"syntax error: unexpected end of file"* and Bitvise exit code 1001. Remote commands are now base64-encoded (`echo <b64> | base64 -d | bash`) so the argument crossing the PowerShell → sexec → remote bash boundary contains no quotes or metacharacters.
30. Release automation: `-SkipFtpUpload` and `-PublishOnly` resume modes - `release_manager.ps1` gained two switches for recovering a partially-completed release: `-SkipFtpUpload` skips the FTP upload step and runs only the remote `update.sh` against files already on the server; `-PublishOnly` is a resume mode that runs only the Bitvise publish/remote steps (reusing the already-built version with no bump) and deliberately skips git, build, website, WP changelog, the version/changes prompts, and release-log regeneration so it can never create a bogus new version entry.

2.0.0.489 changes

1. Slapshot SDK upgraded to 5.1.10 - Full upgrade of the Slapshot capture SDK on the Fed Submit Mobile (Android) app: new `slapshot-core`, `slapshot-capture`, `slapshot-capture-face`, `slapshot-native`, `sciometrics-*`, `opencvlibrary`, and `wsq-android` binaries; refreshed Javadoc; and switched to **Mentalix LicenseSpring key activation** (`ls_activation.lic`) for the SDK. `ContactlessCaptureActivity` and `MainViewModel` were substantially reworked to line up with the new SDK API. Verified end-to-end on device (capture + calibration).
2. Additional match diagnostics for multi-modal searches - `Matcher.vb` now emits substantially more diagnostic information for multi-modal (finger + face) match runs, making it possible to trace which modalities and thresholds contributed to a hit or a miss.
3. `.iss` silent-install response files were not copied to the FedSubmit web folder - The `release_manager.ps1` change in 487 stages `FedSubmit64.iss` and `idms.iss` next to the built exes for the Help → Update self-installer, but `webtools/update.sh` (which runs on the download server after the artifacts are uploaded) never copied them into the `FedSubmit/` folder or the versioned `FedSubmit/$release/` subfolder — so the self-updater had nothing to fetch. `update.sh` now conditionally copies both `.iss` files into both destinations (best-effort — a missing `.iss` just falls back to interactive install, matching the release-side behavior).
4. MAS upload CSV: "Order Date" header now marked required - `OrderForm.vb` was emitting the header as `"Order Date"` without the trailing asterisk that MAS uses to denote required columns. Corrected to `"Order Date*"` so MAS accepts the upload.
5. Slapshot 5.1.10 build & capture-licensing crashes fixed - Several issues that prevented Capture Biometrics from working end-to-end on the new SDK:
6. Firestore vs. gRPC protobuf duplicate classes - `protobuf-javalite:4.35.1` and `protolite-well-known-types:18.0.1` both shipped `com.google.protobuf.*` classes and resources, causing duplicate-class/duplicate-file build errors. Excluding `protolite` outright broke Firestore (removed `com.google.type.LatLng`). Now depends on a stripped copy of `protolite` (`protolite-wkt-stripped-18.0.1.jar`) with only the overlapping classes/resources removed; `javalite` is a strict superset of what was dropped.
7. Missing `ViewModelProviders` - Slapshot 5.1.10 still calls `androidx.lifecycle.ViewModelProviders`, which was removed in lifecycle 2.3+. Added `lifecycle-extensions:2.2.0` (the last artifact shipping it); can be dropped once Sciometrics builds against a modern lifecycle.
8. License activation race on first launch - `MainViewModel.init()` was activating the LicenseSpring key on an RxJava IO thread while `ContactlessCaptureActivity.onResume()` created `SlapshotCameraCaptureFragment` in the same lifecycle pass; the fragment's `checkLicenseAndThrow()` in `onCreateView()` is fatal, and first-time activation (~1.2s network round-trip) always lost the race. Capture requests are now deferred until licensing reports its outcome via a new `getInitializedLive()` `LiveData`. Activation exceptions are no longer swallowed; failures surface as *"Error licensing device"* rather than a crash.
9. Stale native libs - `app/src/main/jniLibs` was a hand-copied snapshot where 10 of 14 libraries were 3–4 months behind, and `libmtximage.so` collided with the `:sdk` module's copy (AGP was picking the stale one). `jniLibs` now points at the canonical `fpdll.Android` output, and `pickFirst` is used for the library both modules supply.
10. Calibration paths now gated on licensing, not just capture - `ContactlessCaptureActivity` was routing capture through the new "wait for license" gate introduced by the 5.1.10 fix above, but the `startCalibration()` and `startCalibrationValidation()` entry points were still fired directly from observer lambdas and could beat activation. Both were extracted into named methods and are now routed through a single `runWhenLicensed()` helper, so any Slapshot UI flow started while licensing is still in flight is deferred (or dropped with a log entry if activation ultimately fails). Verified on device.

2.0.0.488 changes

1. Exclude specific finger positions from match - A new `IDMS_MATCH_EXCLUDE_POSITIONS` environment variable lets a site drop chronically troublesome positions (typically the little fingers) out of the matcher. Set the machine-wide variable to a comma-separated list of position names, e.g. `setx IDMS_MATCH_EXCLUDE_POSITIONS "LeftLittle,RightLittle" /M`. Matching for the remaining positions is unaffected.
2. Face information included in multi-modal match hits - When a match is produced by combining fingerprint and face modalities, the hit record now carries the face score/details alongside the finger data so downstream review can see both.
3. Dashboard home page shows officer count - The dashboard's home page now includes a total officer count alongside the existing summary metrics. Backing data in `Sites.csv` now carries both **officer** and **civilian** counts per site.
4. Android app renamed to Fed Submit Mobile - The Slapshot Android app has been rebranded to **Fed Submit Mobile**: new launcher icon and artwork (`Fed-Submit-Mobile.png` / `fed_submit_mobile_icon.png`), updated app label and login/top-screen layouts, and refreshed `strings.xml`. No functional changes to matching or submission behavior.
5. TXDPS: alias last name rejected for multiple hyphens - TXDPS enforces "Last name may contain only 1 hyphen" via MNC validation. The earlier fix covered only the primary name field; the alias name field could still submit a value with two or more hyphens and be rejected downstream. `EftsChecks.vb` now applies the same single-hyphen rule to the alias last name when `AppMode = "TXDPS"`, catching the error before submission with the message *"Only a single hyphen is permitted in alias name."*
6. Brownsville: DXGI rendering error was masking the real exception - In `Application.xaml.vb`, the DXGI/DirectX exception handler was casting `ex.Exception` (the top-level dispatcher exception) to `COMException` when logging. In the Brownsville-reported case the DXGI `COMException` was actually an *inner* exception, so the outer cast produced an `InvalidCastException` that replaced the real error in the log. The handler now captures the specific inner DXGI `COMException` during the walk of `InnerException`s and logs its HRESULT/message directly, preserving the actual failure detail.
7. Batch Job Manager crash on Update: "The ConnectionString property has not been initialized" - `COMMONDB` (the connection string) and `FSCPCommonDB` (the SQL object) are both populated from the same source, but historically the string was set by a racy separate read while the object was set by the async `AsyncFsConnectCommon` startup task. If the object won the race but the string read lost, `New SqlConnection(COMMONDB)` in `GetProcessDetailText` failed deep inside a `Fill` with an opaque SQL error, crashing Batch Job Manager when the operator pressed **Update** before startup finished. Fixed in two places:
8. `bsqlcomm.FsConnectCommon` now assigns `COMMONDB = sqlConn` inside the same `SyncLock` that establishes `FSCPCommonDB`, so the string and object can never diverge. `ClearCommonDB` also nulls `COMMONDB` so a `NextDB` switch can't leave a stale value.
9. `fsBatchJobManager.DoUpdateManifesto` adds a defensive guard: if `COMMONDB` is still empty when Update is pressed, it forces a synchronous `UpdateCommonDb()`; if it is still empty after that, it throws an actionable `ApplicationException` that the outer handler reports cleanly instead of the opaque SQL error.
10. Fed Submit: cleaner message when another user's session is holding the app open - When Fed Submit starts and finds an existing instance running under a different Windows user account, it cannot terminate that process from the current session. Previously it emitted a raw suppressed error. `KillNonResponsive` now returns a `blockingMessage` describing exactly what the operator needs to do (ask the other user to close the program, log off/switch to that user, or restart the computer), and the caller displays it as a clean informational message instead of an exception report.
11. Autocloseoff / long-query stability improvements - Additional adjustments in `BaseSqlDb`, `FsBoot`, and `HandleHeartbeatUtil` to keep the "auto close off" state consistent and reduce false long-query reports in the heartbeat path.
12. "Edit and Resubmit" now reports the real cause when the EFT file is missing - `FsfViewForm.vb` and `ViewTransactionFormWPF.xaml.vb` previously swallowed a missing-EFT case into a generic *"Error attempting to edit and resubmit"* report. Both now catch `MissingEftException` explicitly and show the operator a clear message including the missing file path: *"Cannot resubmit: the fingerprint image file (EFT) for this transaction is missing from disk."*
13. HTTPS downloads: 2-minute read timeout added to bound stalled transfers - `bftp/FTPRoutines.vb` now sets a 2-minute read timeout on the HTTPS download response stream so a stalled server-side transfer no longer hangs the download indefinitely; it fails fast and lets the normal retry path take over.
14. Guard against listbox / model desync on Texas offense remove - (carried forward from 487 verification) `OffenseDetail.xaml.vb` bounds-check remains in place.
15. TXDPS EBTS 11 schema: add SR (Sex Offender) category - `fbi_ebts.xsd` extended so Fort Worth SOR submissions no longer fail schema validation on the SR record type.
16. TXDPS EBTS 11 schema: add MARK / SCAR / TATTOO bare SMT category codes - Requested by TXDPS Collin County; these bare category codes are now accepted by the schema.
17. Moved from .NET 9 to .NET 10 builds - Solution and shared build props updated; package references bumped to their .NET 10 targets, plus related dashboard/ingest updates. A follow-up `net10 build cleanup` commit tidied up remaining warnings and stale references.
18. `buildWorld.bat` output overhaul - `buildWorld` now writes a reduced, human-readable console/text log alongside a full MSBuild binary log (`.binlog`) for diagnostics, rather than dumping the verbose output to console. A new companion script, `buildWorldVerbose.bat`, restores the prior fully-verbose console behavior when needed.
19. `coldbuildall` cleanup / speedup - Redundant steps removed; overall cold-build wall time reduced.
20. Java / Android toolchain modernization - Multiple related updates:
21. Updated Gradle to **9.3.0**.
22. Migrated to the **Gradle daemon toolchain** so builds pick a consistent JDK across all build machines.
23. JDK references now go through `JAVA_HOME` (currently JDK 25) instead of hard-coded paths.
24. Removed legacy `ANT_HOME` references (unused since ~2015).
25. Android: `ANDROID_PLATFORM` corrected to use `minsdk` rather than `latest`; **minSdk raised to 33**, compile/target raised to **37**. Additional Slapshot-specific Android build cleanup.
26. Small AI-suggested fix in the (currently unused) A86 build path.

2.0.0.487 changes

1. Help → Update Fed Submit self-update button - A new **Help → Update Fed Submit** menu item allows operators to silently install the latest Fed Submit release without running the full interactive installer. When clicked, the application downloads the current installer and the matching silent-install response file (`.iss`) and launches the installer with `/s /f1<Name>.iss`. The `.iss` file is generated per-release (see release-automation notes below) so it always matches the ProductCode of the installer being run, avoiding the dialog that InstallShield shows when the recorded ProductCode doesn't match the exe.
2. Crash when opening the password-change form while it is already open (rare multi-user race) - `Magic.vb` uses a `Dictionary` (`MagicFormList`) to track open form view-models by name. `FrbasedAddForm`, `FrbasedShowForm`, and `FrbasedShowDialog` all called `MagicFormList.Add(frmName, ...)`, which throws `ArgumentException: An item with the same key has already been added` if the form was opened a second time before the first instance had finished closing — a race that can occur when two operators are logged on simultaneously and both trigger a password change, or when the form is re-opened in rapid succession. All three call sites now use the indexer (`MagicFormList(frmName) = ...`), which silently overwrites the stale entry instead of throwing.
3. `ArgumentOutOfRangeException` crash when removing a Texas offense entry - `OffenseDetail.xaml.vb` removed the offense from the model using `RemoveAt(selIndex)` unconditionally. If the WPF `ListBox` selection index was momentarily out of sync with the model collection (e.g. after a rapid add/remove cycle), `selIndex` could equal `Offenses.Count`, causing an out-of-range exception. The remove is now guarded with a bounds check (`If selIndex < Offenses.Count`) before calling `RemoveAt`.

2.0.0.486 changes

1. "Most recent heartbeat" query producing LongQuery log spam at SQL Express sites - The query that locates the most recent successfully-sent heartbeat was structured as a backward `Do While` loop, issuing two `ExecuteScalar` calls per iteration (one to check for a matching `Send Heartbeat` entry, one to step to the next-earlier `HEARTBEAT` row). On sites running SQL Express with `AUTO_CLOSE` enabled, each statement pays a fixed database open/close cost regardless of table size, causing the loop to accumulate ~66 LongQuery entries per heartbeat cycle even though the underlying `[Event Log]` table is only a handful of pages. The loop has been replaced with a single correlated `EXISTS` query: a `TOP 1 DESC` seek on the `IX_elog_Heartbeat` index with a correlated `EXISTS` subquery against `Send Heartbeat` entries that terminates on the first match — virtually always the most recent heartbeat — eliminating the LongQuery noise entirely.
2. Compact exception messages incorrectly using the outer (generic) exception text - A prior cleanup to `GetCompactExceptionMessage` in `EventMsg.vb` left the outer exception as the primary text source and appended the innermost exception as a secondary note. For wrapper types like `HttpRequestException`, the outer message is a generic placeholder (`"An error occurred while sending the request."`) while the real cause lives on the innermost exception. The logic is corrected: the innermost exception is now used as the primary source when its message differs from the outer one, with the `"Exception"` suffix stripping and compact formatting applied to the innermost type name.
3. Fed Submit now offers to restart itself after configuration is saved - Configuration values are cached in the process-wide `CLocal`/`CShared` singletons at logon and never re-read, so changes made in the configuration form did not take effect until the operator manually exited and relaunched. Fed Submit now prompts `"Restart Fed Submit now?"` after the Done button is pressed and configuration is persisted. The restart is handled cleanly: `RestartApplication()` launches a new instance with the original command-line switches plus `/waitforpid=<pid>`, then exits via `CommitSuicide` (releasing the single-instance mutex); `WaitForRestartPredecessor()` in `App_Startup` makes the new instance block until the old process exits before contending for the mutex, ensuring a deterministic hand-off. If a Create Transaction window is open at the time the operator clicks Done, the automatic restart is suppressed and a manual-restart reminder is shown instead so an operator is never interrupted mid-capture. Non-Fed Submit hosts (e.g. MSDPS) are unaffected and keep the original advisory message.

2.0.0.485 changes

1. Epson card scanner (DS-50000 / Expression 13000XL): diagonal sawtooth shear on scanned images - TWAIN memory-transfer strips were copied flat at the driver's DWORD-padded row stride (e.g. 4952 bytes for a 4950-pixel row) into a line buffer laid out at the packed scan-line width, causing rows to drift within each strip and reset at strip boundaries — producing a characteristic diagonal shear pattern that repeated at every strip seam. `EpTwainGetNewImageData` now copies row-by-row, converting the driver stride to the packed stride. The fix is a no-op when the driver does not pad (width already a multiple of 4).
2. Epson card scanner: vendor image-processing capabilities re-enabled after pixel-type negotiation (Appendix F compliance) - `ICAP_PIXELTYPE` negotiation causes the Epson TWAIN driver to silently reset its vendor image-processing capabilities (`COLORENHANCEMENT/2`, etc.) back on. The `disableCapabilities` + audit sequence is now re-run after the final pixel-type negotiation in `EpTwainScanSetup`, and the attach-time disable is reordered to run after `EpTwainInquire`. Capability verification now requires a clean read-back (`TWRC_CHECKSTATUS` is no longer treated as success); capabilities that cannot be read back are reported as `"unverified"` rather than silently assumed disabled. This corrects Appendix F compliance failures for the DS-50000 nfir=0 500/1000 ppi certification path.
3. Epson scanlib: heap overrun, chunk-seam stripes, and vertical smear in IAFIS chunk smoothing - Three bugs in `sclibutil.c`: (1) the smoothing working buffers were allocated using `IgetWidth` (the full image width) rather than `outwidth` (the crop/output width), causing a heap overrun when `outwidth < IgetWidth`; (2) the previous-row pointer was not carried across chunk boundaries, so the first row of every chunk was smoothed against an all-zero row rather than the last row of the prior chunk, producing faint horizontal stripes at strip seams; (3) the row-swap after each output line was missing, so every row was blended against the same initial row rather than the accumulating prior row. All three are fixed; working buffers are freed in `ScLibImagIAFISCorrectTerm`.
4. FTP/HTTPS download: chunked-FTP reconnect failure no longer aborts the update - When the `DownloadBigFile` path failed to reset the FTP connection before attempting a chunked download, it returned `False` immediately without trying the HTTPS fallback. The reconnect failure is now treated as a soft error: the chunked attempt is skipped and execution falls through to `TryDownloadViaHttps`, giving the site one further chance to complete the download.
5. FTP/HTTPS download: FTP connection left dead after a successful HTTPS fallback - After `TryDownloadViaHttps` succeeded, the `RebFTP` object's underlying connection was still in the disconnected state left over from the reconnect attempt that triggered the fallback. Any subsequent `DownloadBigFile` call on the same object would immediately fail with "Not connected to the server." The FTP connection is now re-established (connect + login) after a successful HTTPS fallback so that the object is ready for further use.
6. DNS `SocketException` errors no longer counted as unexpected exceptions - `SocketException` errors with codes `HostNotFound` (11001), `TryAgain` (11002), and `NoData` (11004) represent DNS resolution failures that self-recover and should be logged compactly, but they were not covered by the existing transient-exception filter in `IsKnownTransientException`. They are now matched by error code (not message text) and routed through the compact warning path alongside other transient network errors.
7. Dashboard: sites that have downloaded and installed an update but are not yet on the newest release show ◯ instead of — - Previously the version column used a green ✔ for "running latest" and a muted `—` for everything else. Sites where `Current == EventApp` (the update mechanism is healthy and in sync, but a newer build has since been published) were indistinguishable from sites that are not downloading at all. A hollow circle (◯, grey) is now shown for the "in sync but not newest" state, reserving the `—` for sites where no staged update exists and the installed version is behind. The legend in the page header has been updated to explain all three states.

2.0.0.484 changes

1. NullReferenceException crash when clicking Add Criminal Arrest in view mode - When a transaction was being *viewed* (not open for editing), mutating controls such as "Add Criminal Arrest" remained enabled. Clicking them crashed with a `NullReferenceException` because `TransactionCreateModel.NF.t2.CRIM_ARRESTS` is `Nothing` outside of an active edit session. A centralized `IsEditing` / `RegisterEditOnlyControls` mechanism was added to `TransactionUserControl`: Add and non-selection Remove buttons are now registered as edit-only and are disabled whenever no transaction is open for editing. The gate is applied on construction and re-applied on `Loaded`. Affected controls: `CriminalArrestDetail`, `CriminalCourtDispositionDetail`, all `CA*Set` panels, `SmtInfo`, `OptionalBioInfo`, `WisconsinOtherInfo`, `MississippiDrvrEmpResDet`, `CAVitalSubjectData`, `VitalSubjectData`, `CAOptionalBioInfo`, `ApplicantTab`, and `RegistrationTab`. "More…" popup-opener buttons remain enabled so detail is still viewable in read-only mode.
2. Image Record Device (2.IMA) Make/Model/Serial subfields displayed without separators - The three IMA subfields (Make, Model, and Serial) are joined internally by the NIST non-printing unit separator and were being displayed run together with no visible delimiter. `EftSetDisplayConverter` (already used on the CA TransConfig screen) has been applied to the IMA binding on both the generic Optional tab (`OptionalTransProcInfo.xaml`) and the RPIS tab (`RPISInfo.xaml`), and `ValidationStep="ConvertedProposedValue"` was added so the Type-2 validator receives the reconstructed EFT value rather than the pipe-separated display string. IMA now displays as "Make | Model | Serial".
3. Deleting a transaction with a missing or corrupted EFT blob caused a failing scheduled job with noisy error logging - When a stored transaction could not parse its EFT blob, `NF.t1.TCN` was empty. The delete path in `ViewTransactionFormWPF` passed the empty TCN to a SQL lookup that immediately failed, and a `DoNotRetainDeleteTransactionJob` was still enqueued with a blank TCN — causing it to repeatedly dequeue, fail with an unhelpful error, and retry. Fixed at three points:
4. `TransactionCreateModel.DoNotRetain` now skips job creation when the TCN is `Nothing` or empty, logging a brief diagnostic instead.
5. `ViewTransactionFormWPF` now attempts a direct DB fallback (`ROW_NUMBER`-keyed query) to recover the TCN when NF parsing yields nothing; if the fallback also fails the delete is aborted with a user-visible message rather than passing an empty string to SQL.
6. `DoNotRetainDeleteTransactionJob.Execute` now validates the TCN at job start and calls `MarkFailNoRetry` immediately rather than hitting the database with a guaranteed-to-fail query.
7. HTTPS auto-update downloads not retried on transient server errors - The HTTPS fallback download path (`TryDownloadViaHttps` in `FTPRoutines.vb`) previously made a single attempt and returned `False` on any failure, causing the update check to give up immediately on a temporary server hiccup. The download now retries up to three times with exponential back-off (500 ms → 1 s → 2 s). HTTP status codes `503 Service Unavailable`, `500 Internal Server Error`, and `429 Too Many Requests` are treated as transient and trigger a retry with back-off. Network-level exceptions also retry. Final failure (after all attempts exhausted) is still logged as an error as before.
8. EBTS 11 XML: `MNU` `PersonIDCategoryCode` reconstructed incorrectly for non-MSDPS transactions - The `NiemPersonOtherIdentification` constructor that splits a NIST `MNU` value into `PersonIDCategoryCode` and `IdentificationID` had the two sub-units swapped. For MSDPS transactions the value is stored as `code` + unit-separator (Chr(31)) + `value`; the old code assigned `items(0)` to `ID` and `items(1)` to `Code` — the opposite of the correct mapping — so the category code ended up in the ID field and vice versa. Additionally, non-MSDPS transactions store the value in hyphen-delimited format (`TX-1234567`), which the old code did not handle at all; it treated the entire string as a single token, producing a blank `Code`. Both formats are now handled correctly: the unit-separator path assigns `items(0)` → `Code` and `items(1)` → `ID`; the hyphen-delimited path extracts the leading two characters as `Code` and the remainder (stripping a leading hyphen if present) as `ID`. This was causing EBTS 11 XML validation errors for BJSO and other non-MSDPS sites.
9. EBTS 11 XML: repeating fields capped to schema `maxOccurs` limits - The EBTS 11 schema imposes per-field caps on several repeating elements in `EbtsRecordSubject`. When a NIST record contained more entries than the schema allows, the XML serializer would produce a document that failed schema validation. Excess entries are now silently discarded in the outbound XML using LINQ `Take`; the NIST record in the database is the authoritative store and is never modified. Known caps enforced: `AKA` (PersonAlternateName) = 10, `DOB` (PersonBirthDate) = 5, `CTZ` (Citizenship) = 10, `MNU` (PersonOtherIdentification) = 4, `SOC` (OrganizationIdentification) = 4. This was causing EBTS 11 XML validation failures for Bastrop and other sites with subjects carrying many aliases.

2.0.0.483 changes

1. Neurotec license failure no longer disables sequence checking for the rest of the session - If the Neurotec local license server was temporarily busy at the moment the Extractor or Matcher was first initialized (e.g. another process was releasing its license), the failure was treated as permanent: sequence checking was silently skipped for every transaction until the operator logged off and restarted the program. The failure is now treated as transient: after a 5-minute cooldown the license acquire is retried automatically. Once it succeeds, sequence checking resumes normally with no operator action required.
2. Neurotec license failure no longer logs a redundant error for every finger - A 10-print scan enrolls all 10 fingers on concurrent threads. With no thread synchronization, all 10 threads simultaneously detected the failure and each independently logged the "extractor unavailable" message, flooding the telemetry log with duplicate entries. A double-checked lock now ensures the failure is detected and logged exactly once, regardless of how many threads call the extractor at the same moment.
3. Telemetry ingest service no longer hangs indefinitely on a stalled Azure/Graph/SQL call - Each poll cycle is now wrapped in a hard 5-minute cancellation timeout. Prior to this change, a hung Azure.Identity token refresh (which can block 30–60+ minutes under its internal retry policy), a stalled Microsoft Graph HTTP response, or a blocked SQL call could freeze the ingest service silently and indefinitely until a manual service restart — sometimes going undetected for days. The timeout ensures the service always self-recovers within a predictable window.
4. Telemetry ingest service backs off when consecutive failures accumulate - After 5 consecutive poll failures the service logs a `CRITICAL` warning (identifying it as a persistent connectivity issue rather than a transient one) and extends the poll interval up to 10 minutes. This prevents flooding the Windows Event Log with repeated error entries while SQL Server or Graph is recovering. The service logs a recovery notice and returns to normal polling as soon as a cycle succeeds.
5. Dashboard home page now reliably auto-refreshes after browsing away - The `<meta http-equiv="refresh">` tag used for the 60-second auto-refresh was silently suppressed by two common browser behaviors: (1) **bfcache** — navigating to a site detail page and pressing Back restores the home page from a frozen in-memory snapshot where the refresh timer is not running, leaving the page stuck on stale data; (2) **background-tab throttling** — Chrome, Edge, and Firefox aggressively throttle or skip meta-refresh in inactive tabs. The meta tag has been replaced with a small JavaScript handler that covers all three cases: a `setTimeout` for normal foreground use, a `visibilitychange` listener that reloads immediately if the page is overdue when the tab regains focus, and a `pageshow` listener that reloads unconditionally on a bfcache restore.
6. Dashboard MNC/MRJ reporting significantly enhanced - The site detail page now provides substantially more context when a No-Candidate-Match (MNC) or Match-Rejected (MRJ) result is returned:
7. MNC and MRJ events from the past 14 days are listed individually in the site detail panel, with click-through navigation directly to the relevant heartbeat entry.
8. The matching heartbeat is automatically highlighted and scrolled into view when navigating from an MNC/MRJ flag. Both the mail subject and the raw log body are searched for the highlight phrase, resolving cases where MNC/MRJ identifiers appear only in the subject line.
9. MNC lines are highlighted in purple and MRJ lines in pink in the heartbeat log viewer, making them immediately visible within a long log.
10. Badge counts on the dashboard home page now reflect the 14-day rolling window.
11. Release Verification: match-comparison dialog opens on double-click of Match Score column (not Subject Name) - The results-grid double-click handler previously selected its action by hard-coded column display index, and a column reorder caused the "Match Score" and "Subject Name" columns to swap. The handler now keys off the column header text, so double-clicking "Match Score" opens the match-comparison dialog and double-clicking any other column opens the transaction — correct regardless of column order.
12. Multi-finger fusion diagnostics for Release Verification matching - When the `IDMS_MATCH_DIAGNOSTICS` environment variable is set, the matcher now logs per-candidate fusion detail for identify operations: fused score, probe finger count and positions, how many fingers actually contributed to the fused result, and per-finger mated-minutiae count and rotation angle. This makes it straightforward to confirm that all expected fingers are fusing (vs. only one finger contributing or a missing-finger penalty reducing the score). Off by default; no log output unless the env var is set.
13. Neurotec image-dimension error reporting improved - When a fingerprint image exceeds Neurotec's maximum supported vertical dimension the error is now reported with the actual image size and the limit, making it actionable without needing to look up the constraint. The over-size image is also saved to a diagnostic temp file for offline inspection.
14. OrderForm release automation script - A new PowerShell script (`deploy_orderform_smee.ps1`) automates the OrderForm deployment to SMEE: backs up the existing installation, copies the x64 Release build, and verifies the result. Supports `-DryRun` for pre-flight validation without touching any files.
15. OrderForm automatically copies monthly commission spreadsheet to accounting share - Each time the daily OrderForm close process runs, it now checks whether the current or previous month's commission spreadsheet (`TM-commission-<Mon><YY>.xlsx`) has been posted to the encrypted closing drive (`\\aristotle\encrypt\Closing\<year>\<month>\`) and, if so, copies it to the accounting share (`\\adonis\Accounting\Closing\<year>\<month>\`), creating the destination folder if needed. Repeated runs are idempotent — the copy is skipped if the destination already exists. Errors during the copy are reported in the daily email body without aborting the rest of the close process.
16. Canon SDK `INVALID_HANDLE` events silently ignored after camera disconnect - When a camera is powered off or its USB connection is dropped, the Canon SDK can fire a property-change callback on an already-closed handle (`INVALID_HANDLE`). The camera-disconnect event (`INTERNAL_ERROR` or `COMM_DISCONNECTED`) has already been delivered and the operator already notified by that point; the subsequent stale-handle event is now silently discarded in `ExceptionHandling.cs` rather than being logged as a secondary error, eliminating the redundant `INVALID_HANDLE` entries in the telemetry log.

2.0.0.482 changes

1. Fixed WCF Release Verification searches spinning at "100% but no results" (regression from 480) - The per-task hardening in 2.0.0.480 removed the old "taskId 0 → current search" behavior. That broke the WCF Release Verification path: its progress poll calls `FindSearchJob`, which now returned nothing, so `IDMSSearchProgress` returned 0, progress never reached the start count, and the search spun at 100% without ever fetching results. The gRPC clients send a real task id (and `IsValidTask` rejects 0), so they were unaffected — which is why this case was missed in the 481 fixes. A deliberately narrow compatibility fallback (`ResolveJob`) was restored, used only by the read-only per-task methods (progress, results, RISC):
2. It falls back **only** for taskId 0 — never for −1 (the "busy"/no-job sentinel), and never for a positive-but-missing id, which is genuinely gone and must not resolve to another job.
3. It falls back **only** when exactly one job is registered; with more than one job the request is ambiguous, so it returns nothing rather than cross-route to another client's search.
4. **Job lifecycle stays strict where it matters.** `IDMSSearchEnd` remains exact (used by the gRPC End path, so a stray `End(0)` can't tear down another client's job); a separate WCF-only variant permits the taskId 0 fallback. Because all current WCF clients guard End with taskId > 0, a zero-task client never calls End, so the results-fetch now removes the job after returning results on the taskId 0 path — closing the resulting leak without a client change and keeping the job table clean so the next zero-task search isn't ambiguous. The `taskId > 0` callers keep their normal End-driven lifecycle, and gRPC ownership validation is unchanged.

2.0.0.481 changes

1. Release Verification: a failed IDMS search is no longer reported as "no record found" - The new per-task validation added in 2.0.0.480 (reject when the task/client id don't match) exposed several latent bugs in the Release Verification clients that the old "taskId == 0 → most-recent job" behavior had been masking. For a release-verification system this is the critical one: a service-reported progress/results failure (e.g. "Bad clientID and/or taskID") was being ignored and the search still reported success/no-match. Such failures are now tracked and surfaced as a failed search, and the gRPC results reply's `Failure` field is now checked (previously only the WCF path checked it). Fixed across the deployed fsApps client and fsnet:
2. **Task id now reaches the caller (fsnet).** `TransmitAndEnroll` took the task id `ByVal`, so it never propagated back: the WCF path then ran progress/results/End with task 0 (spinning forever, with `IDMSSearchEnd` skipped) and the gRPC enroll error was dropped. It is now passed `ByRef` (matching fsApps), with both the task id and enroll error set from the gRPC start reply, and each request uses the per-search local task id rather than a possibly-stale class-level field.
3. **Progress requests now carry ClientID + TaskID** instead of relying on the `clientId = 0` ownership bypass.
4. **Failed searches now release the server job.** The `Catch` blocks tore down the transport before the `Finally` ran, so `IDMSSearchEnd` was skipped (and could throw a null-reference) on any failed search. The transport is now left intact through the catches; the `Finally` best-effort ends the task (guarded) and then tears down, so the server job is released whenever the channel is still alive.
5. Configurable matcher thread count (`IDMS_MATCH_THREADS`) - The Neurotec matcher's maximal thread count can now be capped via the `IDMS_MATCH_THREADS` environment variable. A non-negative integer overrides the default; an unset, blank, or invalid value leaves the default in place and is noted in the debug log (which also records the initial and applied thread counts). The override is now applied before the matcher is initialized so it takes effect.

2.0.0.480 changes

1. Fixed plain/slap prints (FBI 8x8) printing low and clipped at the card bottom - On some Cross Match Guardian captures, a misaligned silicone membrane leaves a thin full-width dark line at the platen edge. The auto-crop's white-trim anchored the crop on that line and never removed the white gap below it, so the print-box height clamp kept *line + white gap + upper fingers* and discarded the lower fingers, jamming the ridges against the card edge. A thin edge-line guard now skips a thin leading artifact (≤ 0.10") followed by a clear white gap (≥ 0.15") and advances to the real content on all four edges, bailing out if sustained content sits at the edge so genuine prints are never trimmed. The fix is ink-density based (robust to threshold noise and a faint line + halo) and is a pure crop with no rescaling, preserving FBI 1:1.
2. Print Preview now matches the printed output - Preview rendered slaps with a hardcoded top crop, duplicating the original native bug (membrane line + white gap retained, fingers pushed low). It now uses the same guarded native auto-crop for the four-finger slaps, keeping the existing pinky-side/height clamp.
3. Fixed a dead branch in `RenderPDF` where the right-four case re-checked the left-four condition, so the right-four width clamp never ran.
4. Fixed Release Verification right-index-only search returning an empty probe - With only the right index captured, the finger image was held in a fixed right slot while finger positions were packed by finger count, so the image was paired with an uninitialized finger-position code (FGP 0). The IDMS server's finger-range filter then dropped that record, producing an empty probe template and a "Failed to create template" error. Finger images are now packed by finger count so image and position stay aligned for any single finger; two-finger and left-only captures are unchanged, and right-only now works. Applied to all three Release Verification clients.
5. Fixed stale quality label on the Release Verification Clear button - Clearing a captured index finger cleared the image but left the prior capture's quality label text and colored border, so a cleared finger still showed a stale "Very Good (nn)" indicator. The Clear handlers now reset the label content and revert the border to its pristine state.
6. Friendlier message when a probe yields no usable biometric - When the probe produces no extractable biometric, the IDMS service returns a raw SDK string ("Failed to create template: None") that the clients surfaced under an "Unexpected error from IDMS service" header. This is now translated into a plain-English, modality-neutral message ("No usable biometric could be extracted … fingerprint, photo, or iris") across all three Release Verification clients and the Android (Slapshot) client. Modality-specific extraction failures still hit their own branches first, and the full SDK detail still goes to the logs.
7. IDMS searches now queue instead of being rejected - The matcher uses process-wide static state, so only one search can run at a time. Previously a second concurrent search was rejected outright. A process-wide search slot now lets a second search wait its turn (bounded at 120s) and then run normally, falling back to an "Another search is in progress" reply only if the wait is exceeded (guarding against a wedged search). The slot is released exactly once on every exit path, and inline enrollment still happens under the slot so the synchronous empty-probe error contract is preserved. Task identity was hardened alongside this: task IDs are now generated atomically, and an unknown/zero task ID resolves to "no job" instead of silently routing to the most recent job (which would be wrong once searches queue).
8. Major IDMS search performance improvement - The same per-hit columns (NIST, TOT, name, SID, ID, date) were previously fetched two to three times per hit across the search stages — roughly 4N + 5C individual round-trips per search. They are now fetched once via two chunked, parameterized batch queries (500 TCNs per chunk to stay under SQL Server's parameter limit) and reused by the downstream stages, which now do zero database round-trips. A typical search drops from about 1,770 round-trips to 2, with identical results (TCNs, scores, order, TOT, SID).

2.0.0.479 changes

1. Cleared stale palm/finger "UP" annotations on recapture - The live-scan → Fed Submit annotation channel was set-only: the create form's loops only ever called the annotation setters with `setting:=True`, so when prints were skipped (e.g. "Unable to Print" palms) and then recaptured, the recaptured prints were not in the UP/XX lists and nothing ever cleared their flags — leaving the toggles checked even though the prints had now been captured. (The image side already replaced the old print correctly; only the annotation leaked.) `LiveScanTimerWPF` now records every print successfully captured this pass (via an optional `ByRef capturedClean` list, so existing callers are unaffected), and `CreateTransactionWPF` clears UP and XX for each captured print before re-applying skip/partial annotations. Skipped and partial prints are still re-flagged by the existing loops. Full-palm cases (right/left) intentionally remain unaffected, since full palms are never captured or skipped by live-scan.

2.0.0.478 changes

1. Fixed exception spam when navigating validation errors (regression from 477) - The Errors-list navigation rework in 2.0.0.477 walked the visual tree as a fallback for any object that was not a `FrameworkElement`/`FrameworkContentElement`. A `Grid` surfaces its `RowDefinition`/`ColumnDefinition` objects as logical children, and those are neither elements nor `Visual`s, so `VisualTreeHelper.GetChildrenCount` threw "… is not a Visual or Visual3D" for each one. The exception was suppressed but still logged, flooding the heartbeat (dozens per click in the error list) and slowing the focus recursion. The visual-tree fallback is now guarded with a `Visual`/`Visual3D` check, so definition objects yield no children and the recursion stops cleanly. Navigation behavior is unchanged — those objects hold no focusable field.
2. Fixed live-scan Skip button being silently ignored - The live-scan drivers kept a private `NextButtonEnabled` gate field that was updated per-print in the scan loop, while the visible button (`skin.NextButtonEnabled`) was only set once at task setup. The two could diverge, so a Skip click landing between prints — or on a task that never re-enabled the private field — did nothing. `skin.NextButtonEnabled` is now the single source of truth across all three guarded drivers (EssentialsSDK, LsIb, LsJenetric): the skip handler is gated on it and the visible button is toggled per-print in the scan loop. A dead duplicate disable in the EssentialsSDK/IB `Finally` blocks was also removed.
3. fsLiveScan host program cleanup - Several robustness and correctness fixes to the live-scan host:
4. Removed an unreachable duplicate `id500` branch in `LiveScanDeviceType`.
5. `UpdateSerialNumber` now uses a parameterized `LocalConfigSettings` UPDATE instead of string-concatenating the serial and machine values.
6. `StartUpForm` now disposes the single-instance mutex on all paths (only the owner releases it) and guards the directory name before writing `error.txt`, so an early failure can no longer mask the real exception.
7. `StartUpForm` now calls `Fpu.Term()` on the non-FSRV path to match the FSRV path, so both capture paths release `Fpu` deterministically.
8. `SaveThePrints` now honors `MTX_SAVE_LIVESCAN_PRINTS` on the callback path (previously dead because the TCN was not available there).

2.0.0.477 changes

1. Fixed Errors-list navigation in the Create Transaction dialog - Clicking an entry in the Errors list is meant to switch to the offending field's tab and focus that field, but it did not work reliably. Several root causes were corrected: the recursive focus helpers discarded the result of their nested calls (so a match found in a nested container reported failure and the scan kept running), the tab-skip test compared the same property to two values with `And` (always false, so image-only tabs were never skipped and `tiSMTsTab`/`tiSmtsTab` never matched), and focus was set synchronously inside the `SelectionChanged` handler so the ListBox click immediately stole keyboard focus back. The two near-duplicate helpers were replaced with a single recursive routine that propagates its result, selects every tab on the path, and queues the focus via the dispatcher so it survives the click. The search now walks only the logical element tree instead of descending into every control's template, which had made navigation extremely slow.
2. Fixed Errors-list focus on double-click and re-click of an already-selected error - `SelectionChanged` does not fire when the already-selected error is clicked again (or on the second click of a double-click), so those cases are now handled explicitly, and field focus is deferred at Background priority so it survives the second click of a double-click.
3. Fixed template parsing breaking on a blank line after a comment - A blank line immediately following a comment line no longer breaks parsing of a `.tpl` (or `.crd`) file.
4. IMA field now displays separators correctly - The IMA field now renders strings containing `|` characters as the intended separators.
5. Fixed FPUTIL_VERSION mismatch (`Expected: 3.3-186, Actual: 3.3-187`) - `Mentalix.FUPI.Interop` carried its own stale copy of `fputildefs.vb` that had drifted from the authoritative `fpbase` copy and the native `fputil.dll`. The duplicate file was removed and the single `fpbase` copy is now linked into the project so the version definitions can no longer diverge. The interop package version is now derived from `FPUTIL_REVISION` (`3.3.<rev>`), so a native-revision bump always produces a new package version and lands in a distinct NuGet cache folder — eliminating the "same 1.0.0, different content" stale-cache mismatch.
6. Fixed x64 demo/example deployment in the Fingerprint API Bundle installer - The 64-bit conversion left sample/example installer components shipping stale 32-bit DLLs and missing newly required dependencies, so the prebuilt demos crashed on launch. Each component was reconciled to its real x64 build closure, per-example launcher scripts now prepend `lib\x64` (and the Intel redist dir where needed) to `PATH`, and each example folder's own 32-bit DLLs — which shadowed `lib\x64` and caused `0xc000007b` — were stripped. The reconcile now runs automatically as part of the release build so a normal build can no longer ship a stale component.
7. Search Transaction redesigned as a criterion row builder - The drag-and-drop field palette was replaced with an explicit "Add Criterion" row builder. Each row is `[AND/OR | Field | Operator | Value | x]` (the first row reads "Where"), which is more discoverable, keyboard-friendly, and supports OR between criteria while reusing the existing query engine unchanged. This change also includes:
8. Date-of-birth range/equality search now works - `DateOfBirth` is an 8-character EBTS string stored as `YYYYMMDD` at most sites but `MMDDYYYY` at some. The column is now normalized to `YYYYMMDD` in SQL and compared against `yyyyMMdd` bounds, so `BETWEEN` sorts chronologically regardless of how the value was stored.
9. New "Response Type" search field - Matches the response's Type of Transaction (e.g. `SNF`) via the existing Response Transactions join; results remain the matching submission transactions.
10. Template engine: city/state/zip and last-name punctuation tokens (TPL rev 14) - Added two range-relative punctuation tokens to the template `fmt` column so a template can request per-line punctuation without the engine knowing any agency/state field semantics: `csz` (City, State Zip-Xzip) and `lcomma` (comma after the first subfield, e.g. `Last, First Middle Suffix`). Subfield assembly now trims each subfield, drops empty/whitespace-only subfields, and emits a separator only between two non-empty subfields — avoiding a dangling hyphen when X-ZIP is absent, a stray leading comma when the city is blank, and double spaces from empty middle subfields (per the CA BID-9 spec). `FTREV` was bumped 13 → 14; a template declaring rev 14 will not load on a pre-14 engine.
11. Template engine: general field-format patterns - Added a pattern language (selected when a field's `fmt` contains `[`) that places arbitrary literals around or between a field's subfields and drops them cleanly when a piece is empty: `%1`–`%9` reference subfields, `[ ... ]` is an optional group emitted only when every `%n` inside is non-empty, and `\x` is a literal character. This resolves empty-subfield ambiguity that `csz`/`lcomma` cannot express in general (e.g. `[(%1)]%2` → `(US)Y` with the parentheses suppressed when no country is present).
12. Template engine: `#` character-mask format token - A `fmt` value containing one or more `#` is now treated as a character mask: each `#` is replaced by the next alphanumeric character of the field value and every other mask character is emitted literally. This gives templates a simple way to punctuate fixed-length values such as phone numbers and SSNs (`(###)###-####` → `(123)123-1234`, `###-##-####` → `123-45-6789`). Only letters/digits are consumed (NIST separators, whitespace, and existing punctuation are skipped), literals are held until the next `#` consumes a character so short values leave no dangling separator, and `\#` escapes a literal `#`. No template-column change and no `FTREV` bump.
13. Template engine: last-N characters via negative field start - In the substring path, a negative `fieldstart` now counts from the end of the value, so `fieldstart=-N` with `fieldlen=N` prints the last N characters (e.g. the CA SID/CII "print last eight characters" requirement). Positive `fieldstart` is unchanged, and bounds clamping was added so a value shorter than the requested window yields the available characters instead of reading past the end.

2.0.0.476 changes

1. Reduced noisy ready-file purge errors during EAR import cleanup - READY files are empty sentinel files and can legitimately already exist in the purge folder from a prior cycle. The purge path now discards the source READY file when the destination sentinel already exists, and uses the quieter purge move helper for EAR/EARACK archive moves. This avoids unnecessary error noise while preserving the retry behavior for meaningful file moves.
2. Quieted transient SFTP remote delete permission errors - When an SFTP server reports `Cannot delete remote file` with `Unable to access object permissions` during remote file cleanup, the system now treats it as a transient warning and retries on the next cycle instead of logging a full exception stack. This was observed on Tyler Tech EAR pickup directories.

2.0.0.475 changes

1. Fixed manual submit failing to create TXDPS job when a LocalAFIS/JMS job is pending for the same TCN - The duplicate-submission guard used `HasPendingJob(tcn, "Submit")` to block a second submit job from being queued. However, all submit job variants (LocalAFIS, JMS, PhotoExport, TXDPS, etc.) are stored with `JobType = "Submit"` in the jobs queue, so this check would match a LocalAFIS job created by `HandleNonSubmitExports` and incorrectly suppress the TXDPS submission job. The guard has been removed; the TXDPS job is now always queued unconditionally, matching the pattern already used for LocalAFIS and JMS jobs below it.
2. Fixed EBTS 11.0 XML write errors for SMT and subject elements - Two classes of EBTS 11.0 serialisation failures were corrected:
3. The `PersonPhysicalFeature` element emitted `PhysicalFeatureDescriptionDetail` as a child, which the FBI EBTS schema does not permit at that position (expected `PhysicalFeatureCategoryCode` / `PhysicalFeatureSize`). The element namespace was also wrong (`biom` instead of `ebts`). Both have been corrected.
4. The `EbtsRecordSubject` element properties lacked explicit `Order` attributes, allowing the XML serialiser to emit them in an undefined order that could fail schema-order validation. Explicit `Order` values have been added to all properties.

2.0.0.474 changes

1. Fixed SiteMessage regex parsing in telemetry dashboard - When a heartbeat contained a blank `SiteMessage:` line (no text after the colon), the regex pattern used `\s*` after the colon, which matched across newlines and incorrectly captured the following line as the message body. The pattern now uses `[ \t]*` (horizontal whitespace only) to prevent cross-line matches. This ensures blank site messages are parsed correctly and do not pull in unrelated heartbeat content.
2. Preserved LCM.xml fallback banner when no site message is published - When the site-specific message endpoint returns 404 (no message published for this serial number), the download logic was incorrectly clearing the existing banner by returning an empty string. It now returns `Nothing` so the legacy `LCM.xml` banner can reassert as the fallback. An explicitly published empty string (from the dashboard) is a separate case handled by the JSON payload itself and will still clear the banner as intended.

2.0.0.473 changes

1. Fixed heartbeat exception when export responses folder is inaccessible - The heartbeat writer threw an unhandled exception if the JABS export responses folder path did not exist or could not be enumerated. The folder check is now wrapped in a try/catch so a bad path is reported as an informational note (`ExportResponsesCached check failed: …`) rather than crashing the heartbeat write.
2. Cleaned up date entry validation in fsExpunge search - The Quick Search date fields now validate input before allowing the search to proceed. If a date field contains text that cannot be parsed, a descriptive warning dialog is shown and focus is returned to the offending field. A start-date-after-end-date condition is also caught and reported. Previously, invalid date text was silently ignored or passed to the query, producing unexpected results.

2.0.0.472 changes

1. Fixed RefreshSmts NPE on post-save navigation with empty stran table (INC3201725) - When a freshly installed workstation saved its first transaction, the navigation logic attempted to load RowNumber=0 due to a stale cached TotalRecords value, returned zero rows from SQL, and crashed on a null reference in RefreshSmts. The setter now refreshes TotalRecords synchronously from the database before clamping when the requested value exceeds the cached count, aborts navigation with a diagnostic log entry if the table is genuinely empty, and adds defense-in-depth null guards in RefreshSmts matching the existing RefreshMugshots pattern. LoadTransactionByRecordNumber now logs a diagnostic heartbeat event when a zero-row query occurs, improving incident diagnosis.
2. Removed Angle Offset field from SMT capture form - Angle offsets are only valid for FACE-type photos per the ANSI/NIST-ITL 1-2011 spec section 8.10.21 ("This shall only be used for frontal facial images"). The field has been removed from the SMT form to prevent operators from accidentally entering a value that would be rejected by JABS or other downstream systems.
3. Fixed noisy exception on null image passed to autocrop after prior failure - When a prior capture failure left a null image reference, a subsequent autocrop attempt threw a secondary exception that polluted the log. The autocrop path now checks for a null image and skips silently.
4. Fixed HTTPS update download file name construction error - An error in the construction of the download destination path when fetching updates over HTTPS caused the download to fail. Fixed.
5. IDMS connection logging improved - Connection failures and retries to the IDMS service are now logged with more detail and surfaced to the user with a clearer message.
6. Noisy camera exceptions quieted further - Additional transient camera exception messages are now suppressed from the log after a prior failure has already been recorded, reducing log clutter during sessions where camera hardware is unavailable.
7. Site-specific notes can now be published from the telemetry dashboard and delivered to workstations - Support staff can write per-site notes in the dashboard and publish them to the website. When a workstation checks for updates, it now pulls the site-specific note from the website (based on the workstation's hardware serial number) and displays it prominently in the main window. Notes are stored on the website as the source of truth and cached in the telemetry database. Multi-line messages are supported.
8. Workstations poll for site-specific notes every 15 minutes - The application now automatically refreshes site-specific notes from the website every 15 minutes, so recently published notes appear without requiring a manual update check or application restart.
9. Dashboard polls for site-specific notes every 15 minutes - The dashboard index page now automatically refreshes site-specific notes from the website every 15 minutes, so recently published notes appear without requiring a page reload.

2.0.0.471 changes

1. Fixed non-standard photo dates in FS-XML import - Some FS-XML photo records contained date values in non-standard formats that caused parsing failures during transaction import. The system now handles these edge cases gracefully and normalizes the date values appropriately.
2. Fixed site identification issue with dual-location agencies sharing email addresses - When a site operated both juvenile and adult facilities using the same email address for heartbeat reporting, the telemetry system could not reliably distinguish between the two locations, resulting in incorrect site consolidation in the dashboard. Improved site identity matching now correctly separates these cases using multi-factor matching logic.
3. Added detection and reporting for special 10M serial numbers - The anomaly detection system now recognizes and flags transactions from devices with special 10M serial numbers that indicate test or evaluation hardware. These transactions are properly categorized and excluded from aggregate statistics as appropriate.
4. Display oldest ingest date prominently in dashboard - The site status dashboard now displays the oldest ingestion timestamp at the top of each site row, providing better visibility into data freshness and aiding in troubleshooting stale data issues.

2.0.0.470 changes

1. Fixed JABS Booking Agency role initializing incorrectly for the Arrest role - The Booking Agency combo for JABS non-arrest transactions had an incorrect role code of `"A"` (Arresting Agency) instead of the correct blank value. Sites using the JABS booking workflow saw the wrong role pre-selected, which could cause JABS validation failures on submission. Fixed.
2. Fixed JABS default first names not loading for Booking Agent, Offence Agency Agent, and Arrest Agent - Three Shared Properties keys were missing an underscore character (`JABS_BAGENTNF`, `JABS_OAGENTNF`, `JABS_AAGENTNF` → `JABS_BAGENT_NF`, `JABS_OAGENT_NF`, `JABS_AAGENT_NF`). As a result, default first-name values configured in Shared Properties were silently ignored and the fields were left blank on new JABS transactions. Fixed.
3. Fixed SMT import crash when loading transactions from CardinalTracking/XML - When importing transactions from an XML source (e.g. CardinalTracking) containing SMT photo records, an off-by-one array index (`_Type10_SMTs.Count` instead of `_Type10_SMTs.Count - 1`) caused an `ArgumentOutOfRangeException` immediately after adding the SMT entry, aborting the import. Fixed.
4. Improved handling of 4-channel JPEG files - Some cameras produce JPEG files with a 4-channel (CMYK) color space that the image decoder did not handle, causing import or display failures. These files are now converted to 3-channel RGB on load.
5. Transaction volume now uses annual average reported in heartbeat - The dashboard previously computed monthly transaction volume by diffing total-transaction counts between two heartbeats approximately 30 days apart. This was unreliable for sites with multiple workstations (each with its own local database) or following a database reset. The dashboard now uses the annual average transaction count reported directly in the heartbeat (`Annual Ave. Transactions: NNNN`), which is computed client-side from the full database history and is immune to cross-workstation and DB-reset artifacts. The 30-day delta method is retained as a fallback for older heartbeats that do not include this field, with a sanity check that discards the fallback if the two heartbeats' annual averages differ by more than 3×.
6. Site ingestion handles multi-workstation and split-site scenarios more robustly - The site lookup-or-create logic was rewritten with a three-phase strategy that distinguishes between: a single known site row (updated in place); a multi-row site with a catch-all row that absorbs workstations not explicitly pinned; and a genuinely new machine at a split site (inserted as a new row). This prevents spurious duplicate site rows and ensures customer name, code, hostname, and product name are updated correctly without overwriting good data with blank values.
7. Telemetry Ingest can now run as a Windows service - The `Mentalix.TelemetryMonitor` ingest process can now be installed and run as a Windows service. It will be configured to run this way on the CETO server.
8. Tables version report notes updated - Additional hardware and Windows 10 notes added to the tables version and site reports in the dashboard.

2.0.0.469 changes

1. Fixed MNC errors caused by linefeed control character in Place of Birth field - Transactions were generating spurious MNC errors because a linefeed control character (LF) was being stored in the POB field via a corrupted template default or import. ValidPOB now rejects values containing control characters, and the template-loading path validates the default POB through ValidPOB before applying it.
2. Fixed NPE crash in CreateMugshot/CreateSMT save flow - A partially-filled SMT record (missing Photo Type or NCIC code) was silently producing a Type-10 record with a null PhotoType, causing a null pointer exception in NistFile.Smts/Faces getters on post-save reload. The save flow now validates both fields before proceeding and the NF.Faces getter is guarded against a null NF reference.
3. Fixed EBTS 11 XML SMT category code mapping - MapSmtToCategory rewritten to use prefix-based matching on the first whitespace-delimited NCIC token rather than substring matching, fixing false positives (e.g. "SC EAR" falling through to MARK) and false negatives (e.g. "RTAT FHD" classified as TATTOO instead of SCAR). Added UTAT, RSC, RTAT, BURN variants. PhysicalFeatureCategoryCode XML namespace corrected from ebtsNS to biomNS.
4. Single quote in logon name no longer causes log noise - An errant single-quote character in a Windows logon name was causing a SQL exception that polluted the log.
5. Signature pad exception report cleaned up - Noisy ePad load failure exceptions are now reported at an appropriate level, reducing log clutter when no signature pad is attached.
6. Iris capture timeout logging toned down - Repeated iris capture timeout messages are now suppressed after the first occurrence.
7. SQL compatibility level update now runs on remote servers - The automatic SQL compatibility level upgrade was previously skipped for remote SQL Server instances; it now runs regardless of server locality.
8. Heartbeat index improved to speed up most-recent-heartbeat query - A targeted index was added to the heartbeat table to reduce query time for the most recent heartbeat lookup.
9. Regular receive check log label corrected - A misleading label in the response receive logging was cleaned up.
10. Recent upgrades report added to dashboard - New report page shows which sites have recently received version updates with previous/current version columns.
11. Tables version report added to dashboard - New report page shows the database tables schema version across sites.
12. Trip/MNC/MRJ errors now badged on site names in dashboard - Sites with active Trip, MNC, or MRJ errors are highlighted with badges on their site name in the main dashboard list.
13. TXDPS-only toggle added to telemetry trend charts page.
14. Version aging display improved in site list.
15. Telemetry ingestion log entries now include timestamps.
16. Releases and sites links added to dashboard navigation; site notes updated for latest releases.

2.0.0.468 changes

1. Fixed JABS JABS_ABS_VERS field value format - The 2.501 field introduced in release 464 was being written as "FS 2.0.0.xxx" (with a space after "FS"), producing a value one character longer than intended. The JABS ANS spec allows a maximum of 15 characters; the extra space was unnecessary and inconsistent with the field's purpose as a compact version tag. The value is now written as "FS2.0.0.xxx" without the leading space.
2. Dashboard site note configurations updated for recent releases.

2.0.0.467 changes

1. Restored response receive error logging suppressed by 461 noise cleanup - The log-noise reduction work in release 461 was too aggressive: it gated SFTP directory-not-found and already-removed warnings behind the `suppressExceptionLogs` flag, silently swallowing them even when a real directory error occurred during response polling. These conditions are now always logged as `WARNING` so that receive-side directory problems are visible in the log regardless of suppression settings. A log entry is also now written when a manual receive is triggered, providing a clearer audit trail.
2. Transient IDMS connection exceptions no longer flood the log - Noisy transient IDMS connection errors (in both the core utility and the ReleaseVerification view model) are now suppressed at the expected transient level, reducing log noise without hiding genuine connectivity failures.
3. Dashboard charts updated with additional data parsing and new chart configurations.
4. Dashboard site row display, notes, and help page cleaned up; `appsettings.json` site configuration expanded.

2.0.0.466 changes

1. Fixed EBTS11 write error (regression from 462) - Corrected a bug in the EBTS11 output format that was introduced by a fix in release 462. The format now writes correctly.
2. FedSubmit log can now be saved to text file - Added a "Save Log..." option to the FedSubmit top-level menu that exports the recent portion of the application log to a `.txt` file. This simplifies troubleshooting by making it easy to share diagnostic information without navigating to the full log directory.
3. Out-of-memory log spam suppressed - When the application enters an out-of-memory death spiral, redundant log messages are now deduplicated to prevent log file bloat and reduce I/O pressure during critical memory conditions.
4. Heartbeat cold-start query performance improved - Optimized the query that retrieves the most recent heartbeat record on application startup, reducing initial load time.
5. Dashboard marks sites not yet in Sites.csv - The telemetry dashboard now visually flags sites that are reporting heartbeat data but are not yet registered in the canonical `Sites.csv` file, making it easier to identify and onboard new deployments.
6. Sites.csv updated with 11 new site entries.

2.0.0.465 changes

1. Fixed Neurotec licensing failure after extended uptime - The biometric verification service (`vfing`) was calling `NLicense.Obtain()` every time an Extractor or Matcher was constructed, because `Dispose()` decremented the shared counter back to zero without releasing the license. This caused the local license server to be contacted on every ReleaseVerification scan and every restart, making the app vulnerable to transient `NotActivatedException` failures after 10+ days of uptime (root cause of the Burnet County issue). Fixed by replacing the counter-based gate with a boolean flag so license acquisition fires exactly once per process lifetime.
2. SQL Server reindex check was incorrectly skipping maintenance - The SQL Server readiness-for-reindex check had a logic bug that frequently caused index maintenance to be skipped unnecessarily, holding off the reindex job until the 7-day expiration elapsed. The check has been corrected.
3. GSA order form now enforces 5-digit ZIP codes - The GSA order form previously accepted extended ZIP+4 formats, but only 5-digit ZIP codes are supported by GSA. Validation now enforces this limit.
4. Scanner communication break handling improved - Cleaned up how scanner communication interruptions are detected and handled, reducing erroneous error states when the scanner temporarily loses contact with the host.
5. Hardware acceleration disabled during scanner visualization - Hardware acceleration is now disabled while the live scanner preview is active, reducing resource pressure and improving stability during capture sessions across all scanner skin variants.
6. SQL Server 2026 recognized in heartbeat and dashboard - Added SQL Server 2026 (version 17) to the list of known SQL Server versions reported in heartbeat data and displayed in the telemetry dashboard, including updated compatibility level handling.
7. Developer site notes added to telemetry dashboard - A new site notes capability allows developers to attach insight and resolution notes to specific sites in the telemetry dashboard. Notes appear on the site detail page and are linked (with dates) from the main site list.
8. Low disk check added to dashboard main page - A one-click low disk check button is now available on the telemetry dashboard main page for quick triage without navigating to a site detail.
9. Telemetry charts improved - The charts page has been significantly enhanced with improved data models, release exception point tracking, and site note annotations overlaid on chart data.
10. Dashboard and ingestion service updates - General improvements to the dashboard repository, telemetry ingestion service, and mailbox reader for more robust data handling.

2.0.0.464 changes

1. Fixed download failures at multiple sites due to last-chunk timeout - Resolved an issue where file downloads were regularly failing at several sites (SPD, Alamo, Cameron, and others) because of a timeout on the final chunk of a download. Downloads now complete reliably.
2. FTP download retry on idle disconnect - Added a second attempt on FTP downloads to cleanly handle cases where the FTP connection had gone idle and was silently dropped, preventing spurious download failures.
3. **Fixed JABS Type-10 photo POSE/POA handling** *(Refs: INC3201725, JABS Help Desk guidance May 2026)* — Corrected JABS submission failures caused by invalid or missing POSE/POA values on FACE (Type-10) records. Per JABS Help Desk clarification (David Tran, May 2026), `POSE` (10.020) is required for every FACE record and `POA` (10.021) is only valid when `POSE=A`. NPS transaction 65696791 was rejected because a user entered "no" into the Angle Offset field, which violated the required numeric format. The following corrections were made:
4. **UI validation**: The Angle Offset field is now disabled unless the selected pose code is `"A"`, preventing entry for non-angled poses. Changing pose code automatically clears any previously entered angle offset, including in Edit-and-Resubmit flows. Keystroke-level input filtering blocks non-numeric input (e.g. "no"), and a range check on focus-loss flags out-of-range values (outside −180 to +180). An inline tooltip documents the JABS spec requirement.
5. **Submit-time validation**: At submission, each FACE record is checked to ensure `POSE` is present; when `POSE=A`, `POA` must be a valid integer in `[−180, +180]`; when `POSE` is anything else, `POA` is forced blank to prevent stale values from leaking through.
6. **JABS_ABS_VERS field added**: Field `2.501` is now populated with the FedSubmit version string (`"FS " + FileVersion`, truncated to 15 characters per the JABS ANS 5–15 spec), as requested by the JABS Help Desk for support tracking.
7. **Version stamping corrected**: Version stamping defaults moved into `Directory.Build.props` so all projects report the correct canonical version. Previously, `FedSubmit.exe` and `fstransaction.dll` were reporting `1.0.0.0`.
8. CR43 response export failures handled gracefully - When a CR43 response export to `ResponseExportDir` fails, the job is no longer immediately marked as failed without retry. Instead, the export is silently written to the alternate cached responses export folder, consistent with how other export failures are handled.
9. ResponsesExportDir now included in heartbeat output - The configured `ResponsesExportDir` path is now reported in heartbeat data, improving visibility into export configuration across sites.
10. Telemetry dashboard now includes an interactive map view of sites, with geo-data added to the site list. Map is no longer limited to TX, and the Plano headquarters address has been corrected.
11. Minor noisy log and exception reporting cleanup to reduce diagnostic noise.

2.0.0.463 changes

1. Fixed JABS photo crash identified in 461 - Resolved an additional crash in JABS photo handling that was reported after the 461 release.
2. Fixed chunked file download failure - Corrected a bug where chunked downloads of two sets of chunks would fail because the end of the first chunk set was not being properly recognized, causing the download to abort prematurely.
3. Routine maintenance queries no longer block heartbeat - Long-running maintenance queries are now prevented from spanning and delaying the heartbeat cycle, improving overall system responsiveness.
4. JABS transaction retention enforced - Enabled retention for JABS transactions and ensured the retention code is always explicitly set to `'Y'` in JABS mode, guaranteeing records are retained per JABS requirements.
5. Heartbeat query performance improvement - Optimized required heartbeat queries to run faster even when indexes are not available, reducing delays in environments with degraded index state.
6. Telemetry dashboard updated with per-site download volume by month and improved identification of sites with download problems.

2.0.0.462 changes

1. EBTS 11 SMT entry fix - Corrected a longstanding issue (present since 456 and earlier) with SMT (Scars, Marks & Tattoos) record handling in EBTS 11 submissions. The previous attempt to fix this with a hard entry limit was not the correct solution; the underlying problem has now been properly addressed.
2. Improved Neurotec latent/sequence match reliability - Cleaned up issues with Neurotec fingerprint matching that could cause sequence match problems; consequential stability improvements in the matching pipeline.
3. Improved abandoned transaction reporting - Multiple rounds of heartbeat cleanup to eliminate false reporting of abandoned transactions and improve accuracy of detection.
4. Improved login timeout handling - Refined database login timeout logic to better handle slow or delayed SQL Server connections at startup.
5. Quieted camera interface errors on exit - Suppressed noisy exceptions logged when the camera/fingerprint scanner interface was still active at the time the user exited the application.
6. Quieted scanner not-ready exceptions - Suppressed spurious exceptions logged when a scanner was not yet ready during initialization.
7. Reduced noisy index check logging - Extended the index check timeout to prevent log noise from checks that exceeded the previous threshold under normal conditions.
8. Quieted Matcher initialization noise - Cleaned up additional spurious log output during fingerprint matcher initialization.
9. Additional transient/access error log suppression - Further reduced noisy logging from transient file transfer access errors.
10. Telemetry tuning for improved detection and reporting of successful retries on transient issues.

2.0.0.461 changes

1. Fixed SQL syntax error introduced in 460 cleanup - A code cleanup change in the 460 release inadvertently introduced a SQL syntax error on exit; this has been corrected.
2. Reduced noisy error logging - Suppressed several categories of spurious log noise:
3. Exception reports originating from stale callbacks no longer generate unnecessary log entries.
4. Corrupt EFT message errors from transient conditions are now handled quietly.
5. Transient file transfer errors (FTP/SFTP) are no longer logged as exceptions.
6. Improved error message clarity in submission processing.
7. Telemetry dashboard now only marks a site as update-ready when the latest version download was fully successful.
8. Telemetry ingestion now processes data in reverse chronological order so recent dashboard data is visible almost immediately on startup.

2.0.0.460 changes

1. More comprehensive fix for JABS photo pose field handling - Based on updated JABS documentation, expanded the fix for photo pose settings to correctly handle all cases where JABS customers do not permit the photo pose field, preventing submission failures.
2. Reduced noisy error logging on application exit - Suppressed spurious error messages that were being logged when the Transaction Manager closed, keeping logs cleaner.
3. Added release badging assessment to categorize and track real-world deployment success rates across sites.

2.0.0.459 changes

1. Fixed crash during JABS transaction creation - Added null guards in transaction creation to prevent unhandled exceptions that were occurring for JABS customers under certain conditions.
2. Reduced changelog refresh interval to 5 minutes (from 1 hour) so newly released versions reset site update status more quickly.

2.0.0.458 changes

1. Fixed Auto Close OFF failing due to timeout - The database "Auto Close" disable operation was timing out before completing, causing the process to repeat indefinitely without ever succeeding; the timeout has been corrected.
2. Texas: Removed multiple-hyphen allowance in last name - Updated validation to comply with Texas's updated requirement that last names may no longer contain multiple hyphens.
3. JABS/Parks: Suppressed photo pose field for incompatible customers - Added a configuration-based option to omit the photo pose field for customers (e.g. JABS/Parks) whose systems reject or are broken by its presence.
4. EBTS 11: Enforce maximum of 9 SMT entries per specification - Scars, Marks, and Tattoos (SMT) entries are now capped at the EBTS 11-specified maximum of 9, with a warning logged when the input exceeds that limit.
5. Improved HTTPS download reliability - Hardcoded a base HTTPS download location and refined fallback logic to ensure file transfers succeed in environments where other methods are unavailable.
6. Improved response export failure reporting - Expanded the error information reported when a response export fails, making it easier to diagnose the root cause.
7. Telemetry dashboard updates including search capability, an update-ready indicator on the home page, and segregation of internal/long-expired Mentalix sites from active site prioritization.

2.0.0.457 changes

1. Fixed crash when photo/capture date is not set - Resolved an unhandled exception that could occur during transaction creation when a photo date was not populated.
2. Fixed duplicate TCN (Transaction Control Number) issue - A regression introduced in 2.0.0.453's double-submission fix was inadvertently generating duplicate TCNs; this has been corrected.
3. Corrected WSQ compression error diagnostic cleanup - The cleanup logic for WSQ compression error reporting was not functioning properly; diagnostic information is now captured and displayed correctly.
4. Fixed incorrect response message type in transaction log - Miscellaneous transaction responses were being recorded with the wrong message type in the activity log.
5. NCIC pre-EBTS11 field name normalization - Added automatic conversion of legacy NCIC field name constants that use the letter "O" to the correct EBTS 11 format using the digit "0", improving compatibility with older data sources.
6. Improved recovery from graphics driver / DirectX errors - Enhanced handling of DirectX/Direct2D exceptions caused by outdated GPU drivers or GPU resets, reducing unexpected application crashes on affected systems.
7. HTTPS fallback for file downloads - Added HTTPS as a fallback transfer method when primary download attempts fail, improving reliability of automatic updates and file retrieval.
8. Reduced noise in error logging - Transient response timeout errors are now recorded as informational log entries rather than full exception stack traces, keeping logs cleaner and easier to review.
9. Telemetry dashboard updates including health scoring improvements, site identification enhancements, and report cleanup.

2.0.0.456 changes

1. Additional Release Manager Updates for Online Release

2.0.0.455 changes

1. Correct automated release management script

2.0.0.454 changes

1. Fix problem introduced in 453 release for job submission status logging
2. Update IB Scanner driver software
3. Add release manager script to automate and speed up complete release process

2.0.0.453 changes

1. Fix to ensure the PrincipalContext uses the already-validated user credentials to connect to Active Directory, rather than the machine's potentially stale Windows credentials. This eliminates the spurious "incorrect password" exceptions that were cluttering the logs.
2. Attempt to prevent multiple user submissions of a transaction that has not errored.
3. Conservative update of database compatibility level when way out of date + limit sql server memory when using full sql version so not to start memory
4. Cleanup display of Response forms

2.0.0.452 changes

1. Fix lookup column resolution and mode-specific filtering across lookup tables for fields like Sex, Hair Colors, Eye Colors, …

2.0.0.451 changes

1. Receiving responses via IMAP had been broken
2. XML/XSD correction to XML print files for validation
3. Printing TXDPS charges on fingerprint cards had not been updated for recent charges
4. Fields that use ‘|’ to split into subfields did not validate correctly

2.0.0.450 changes

1. Citizenship import fixes
2. Cleanup multiple display of XML import errors/warnings
3. Add TRN to more reports
4. Print Operator number on blank CR45d form

2.0.0.449 changes

1. New version of matching SDK
2. Attempted fix of failed sequence check / obtain license blocking user from continuing operation

2.0.0.448 changes

1. Add TRN to Completed Transactions report.

2.0.0.447 changes

1. Print Preview didn't allow going to a previous page
2. Mugshot interface fixes for recapture
3. Move stale TXDPS responses (older than 90 days) to local archive and purge them so we don't get future repeated messages for them.

2.0.0.446 changes

1. row information was not correctly written by fpuCardWrite()
2. Texas_CTZ did not import from file creating tflu transaction

2.0.0.445 changes

1. Fixed problem with lost OCA and ORIA fields in a TFLU import

2.0.0.444 changes

1. New matching SDK required additional files

2.0.0.443 changes

1. The fpuCardNewStandard() did not create the bar chart, step tablet, printer and scanner information in the correct area
2. Import from Fed Submit XML did not work correctly for some fields
3. Add a fast fail on FileExists checks for UNC paths where the path isn't reachable
4. New version of matching SDK

2.0.0.442 changes

1. 2026 copyright messages
2. Fix for problem with fsReceive service when transient network issue arises
3. Fix minor issues with blank CR-45 print form

2.0.0.441 changes

1. OpenMP fix for problem introduced by Microsoft
2. EFT files incorrectly assessed as Virigina for EBTS 11 XML validation checks
3. Double-click import fix
4. When freeing TCNs for reuse, skip not only missing EFT, but also bad EFTs

2.0.0.440 changes

1. Update PNG support to version 1.6.50
2. Update zlib support to version 1.3.1
3. Add support for importing .png mugshot photos
4. Update build environment to Visual Studio 2026
5. Camera exception cleanup
6. Fix problem with NFIQ support on some machines
7. EBTS11 writer did not handle multiple SMT properly
8. Check for errant entry of spaces within social security number
9. Add import from FTP/SFTP server to xml import
10. Fix multi-click issues on import

2.0.0.438 changes

1. Fix for problem scanning palm cards
2. Fix for problem writing XML NIST files

2.0.0.437 changes

1. Fix for problem with signature pad.

2.0.0.436 changes

1. Fix for receive problem introduced in 435 release.

2.0.0.435 changes

1. Fixes for JABS create transaction.

2.0.0.434 changes

1. Attempt to fix problem in the Iris interface reported in the 433 release.

2.0.0.433 changes

1. Attempt to fix problem in the Iris interface reported in the 432 release.
2. Fix for problem saving transaction introduced in 430 release.

2.0.0.432 changes

1. Attempt to fix problems in the Iris interface reported in the 431 release.

2.0.0.430 changes

1. Make sequence checker and quality check update results as progress made + clean up sequence checking including skipping unnecessary checks when prints not available.
2. Attempt to silence transient SftDirToLocalDir exception
3. IIDS transactions have an object reference not set error when attempting to save the transaction

2.0.0.429 changes

1. Fix for matching medium sized photos
2. Fix for Mugshot issue in Create

2.0.0.428 changes

1. New matching algorithm version.

2.0.0.427 changes

1. Fixed problem importing an RMS file.

2.0.0.426 changes

1. Memory issue fix potentially affecting Release Verification Match display and Print Preview
2. Release Verification was limiting results to 1 match
3. Segmentation fix for poor quality card scan prints

2.0.0.425 changes

1. Mid-Willamette fixes
2. Edit and Resubmit fix

2.0.0.424 changes

1. Memory leak cleanup/speedup
2. Fix fingerprint tab issues + improve test to only go to 4-4-2 tab on 4-4-2 transactions + wait for sequence/quality and display in test
3. Fix EAR import/cancel/import issue
4. Various FBI Application Mode fixes
5. Add MAP-EXP for Mid-Willamette Valley transactions

2.0.0.423 changes

1. Fix problem downloading TXDPS responses intruded in 422 release
2. Fix flatbed scanner problem intruded in 421 release

2.0.0.422 changes

1. Fix rare race condition in Progress bar display
2. Attempted improvements in Camera error handling - retry on potential transient errors + improve messaging + improve cleanup
3. Attempt fix paper bin combo crash when conflict with underlying driver mutating list
4. FBI mode view fix
5. Fix RemoveAt in ascending loop in most common IRIS-related exception
6. OpenCV 4.12
7. Add staging area in SftpDirToLocalDir to prevent consumer/producer partial completion problems
8. Downsample imported mugshot/smt to limit of 2048 maxWidth to prevent out of memory on absurd large files
9. Handle camera take photo double-click + adjust retry count more sensibly based on error type
10. Upgrade to Integrated BIometrics SDK 4.2.1

2.0.0.421 changes

1. Upgrade to latest Barcode library
2. When default print template resides in TXDPS folder, users can't print from View form with an applicant template
3. In some situations the Texas Offense description selection didn't work properly
4. EBTS11 fixes
5. Fix for issue that occurs when using ImportReady before a TOT is assigned
6. T2_CTZ fields were not properly imported from Fed Submit XML when not in Texas mode

2.0.0.420 changes

1. Some RMS fields were not properly imported

2.0.0.419 changes

1. Fix for problem where imported FBI number has a value of 0
2. Imported empty SMTs resulted in blank SMT entries in NIST file

2.0.0.418 changes

1. FBI numbers were not properly imported into Fed Submit from EAR files

2.0.0.417 changes

1. In some situations SMTs were not saved to the NIST file.

2.0.0.416 changes

1. Improved handling of SMTs for view and create

2.0.0.415 changes

1. Fix problems with Texas SOR transactions

2.0.0.414 changes

1. Fix problems changing tabs in View form

2.0.0.413 changes

1. Fix various problems with Edit and Resubmit
2. Fix parsing problems with new Texas SNF responses

2.0.0.412 changes

1. Removing an offense on the Texas Offense tab was broken
2. Edit and Resubmit did not work properly if the Offenses had been viewed in View Transaction
3. After saving a transaction, next create transaction was broken

2.0.0.411 changes

1. View dialog displayed AON instead of AON_Desc

2.0.0.410 changes

1. Rebuild Index code broken / runs every time in thumbnail generation and not really necessary with ServerDB level reindex approach
2. Create Transaction broken in 409 release

2.0.0.409 changes

1. The PhotoSource, PoseSource on both the SMT and Mugshot images were inadvertently tied together.
2. Fix view problems for transactions with more than 1 offense.
3. Use ComboBox filtering for the AON field

2.0.0.408 changes

1. Creating transaction from RMS import didn't work with new validation strategy
2. Edit and Resubmit of TFLU didn't allow new offenses to be added

2.0.0.407 changes

1. Remove validation from the AON description field

2.0.0.406 changes

1. MNC check for invalid 12345678 texas drivers license number
2. Switch to a simpler field validation check to improve performance and reduce memory leaks

2.0.0.405 changes

1. In Texas mode, only first offense had an optional DOO
2. Misc fixes to Texas offense handling in Create transaction
3. Improve reporting of J2k read errors

2.0.0.404 changes

1. Camera error handling improvements
2. ComboBoxes didn't work properly for lookup when typing more than 1 character
3. Cleanup at end of Create caused problems with subsequent Create bindings
4. Fix rare Fed Submit close popup issue

2.0.0.403 changes

1. Remove VB6 style string parsing (.trim$, etc.)
2. LDA value was not saved properly for Texas Offenses

2.0.0.402 changes

1. Fix for issue caused by repeated double-clicking a transaction in transaction manager
2. Fix memory leaks in fpuJ2kLoadFile when error occurs an image is not read successfully
3. Add SQL server memory logging to heartbeat and attempt setting minimum to 1GB of memory

2.0.0.401 changes

1. Fix for MRJ issue on FBI values where bogus values were imported from an RMS
2. Fix for rare Delete Transaction dangling TCN issue.
3. Don't allow type 10 records with a width or length less than 100 pixels
4. Add wait cursor when waiting for the view form to be displayed after double-clicking on a transaction manager/release verification/search transaction
5. Fix for errant Texas_ADA entries for years < 1753
6. Improved performance of reading/displaying fixed table information
7. Fixed issue importing UTF-16 style XML files

2.0.0.400 changes

1. SMT images were not properly imported from XML files

2.0.0.399 changes

1. GRPC Idms server startup improvements
2. Better handling of failed Neurotech license situation

2.0.0.398 changes

1. Prevent multiple fsLiveScan instances from starting
2. Button color fix

2.0.0.397 changes

1. Improve error reporting when importing mugshot and smt images
2. Right little segmented slap image mistakenly was displaying copy of right index
3. Fix on DOB vs DOO check following a resubmit
4. Button color fix

2.0.0.396 changes

1. DoNotRetain setting should not prevent transaction from submitting.
2. In some cases flatbed scanner initialization took too long, resulting in message pump errors
3. Release Verification searches that were Iris or Photo-based, did not properly save
4. More robust handling of GRPC IDMS startup
5. Reduce memory footprint
6. When printing CR43 to PDF from view dialog and user selecting output file, print should be done in client not queued for print service that might not even have chosen output file name accessible
7. Enroll error with exception diagnostic not necessary after vfing init failed
8. In TXDPS mode, delete responses from server that are not ours and more than 6+ months old

2.0.0.395 changes

1. Fix display of livescan interface

2.0.0.394 changes

1. Create Transaction did not display mugshot angle offset
2. Improvements in auto-logoff
3. check for latest LiveScanEssentials version at runtime
4. Properly report situation where wrong HID scanner is selected in configuration
5. Show PalmTab when selecting "Scan Palms"
6. Fix sizing of fsLiveScan Window for some high definition resolutions
7. Fix issue where user saves without selecting a PhotoType or Pose of a mugshot image

2.0.0.393 changes

1. Add auto-logout functionality add for case where another user logs into machine and current Fed Submit session is not creating a transaction.
2. Reworked Mugshot and SMT photo interfaces to display resolution and dimensions
3. Fix problem where bacpac files from previous release were not overwritten with new version.

2.0.0.392 changes

1. Cleanup ugly abbreviated names in user interface (e.g. Soc. Security Number)
2. Write the OCA value to the 2.009 field instead of the TRN value at TXDPS’s request
3. PhotoCrop errantly used View image instead of larger original image to crop resulting in very low resolution cropped images
4. Improved ComboBox failed entry reporting

2.0.0.390 changes

1. Fix for killing another Fed Submit session at startup
2. Remove index creation option that wasn’t compatible with older SQL versions

2.0.0.389 changes

1. Fix broken (in 388) Texas Decrypt
2. SMT photos should not have a 10.013 field

2.0.0.388 changes

1. Apartment state fix for Codes table update
2. Fix for SQL remote server determination
3. For Fed Submit XML import, check for cached copy of import (image) when available rather than going back to xml specified server copy
4. Additional tuning of camera failure retries
5. Fix heartbeat broken issue during first 10 minutes after program start
6. Fix for MNC based on LIY + 2 years over current year
7. Update Epadink signature pad SDK to latest version

2.0.0.386 changes

1. Accept DOO value as blank since that is valid. For errant DOB or DOO, don't throw exception, just log error as reported to user
2. Do not abort creation of TCN column in JobsQueue when the serialized job is corrupt

2.0.0.385 changes

1. For TXDPS, filter out type 17 records from a submission when none of the type 17s where able to be successfully captured.
2. Improved handling of running Fed Submit while another Fed Submit process is already running.
3. Improved IDMS startup
4. Previously heartbeats might not report all events if the heartbeating program terminated while the heartbeat was generated.

2.0.0.383 changes

1. Camera error cleanup
2. Attempt to fix MNC: on Critical Err: Date (ER2_DOO) ''12301899'' must be greater than or equal to the comparing date (EH_DOB) ''09031989'' plus 10 years
3. Attempt to cleanup handing of reported MNU related exception after JMS import
4. EBTS 11 supports multi-part MiddleName and does not support PersonFourthImportanceName and PersonFifthImportanceName from EBTS 10 and earlier

2.0.0.382 changes

1. Fix problem receiving responses
2. New Crystal Reports engine

2.0.0.381 changes

1. Fix broken JobsQueue stored procedure updates
2. Fix problem upgrading indexes at startup
3. Fix for problem when sftp connection is closed by server
4. Shared property handling - rewrite to try to reduce chance of contention issues, ensure thread safety, update cache with new property changes

2.0.0.380 changes

1. Fixed problems adding TCN column to JobsQueue table when JobsQueue table is large
2. Do not attempt retry of print jobs when NIST file is corrupted (ERR_NISTREAD_FIELD_ID or ERR_NISTREAD_BUFFER_OVERFLOW)

2.0.0.379 changes

1. Fixed problem creating SOR transactions in TXDPS mode

2.0.0.378 changes

1. Add TCN column to JobsQueue table to speedup TCN recycling

2.0.0.377 changes

1. Chunked download support for new releases where large downloads are prohibited
2. EBTS 11 XML output improvements
3. In Transaction Create, enforce character type restrictions for type-2 fields
4. FBI mode was errantly using JABS ruleset
5. If a TXDPS transaction had an invalid ORI in the 410 field, editing and resubmitting did not fix the problem
6. In WDOJ mode, partial Additional DOBs were incorrectly added during edit and resubmit

2.0.0.376 changes

1. Speed up for TCN recycling
2. Transaction Manager transactions should be ordered by Date and not NIST number

2.0.0.375 changes

1. Fix problem with ftp exceptions after failed recursive download of empty folder
2. EBTS 11 schema fix
3. Operator could not see offense text when typing

2.0.0.374 changes

1. Heartbeat cleanup

2.0.0.373 changes

1. EBTS 11 fix
2. Attempted database performance improvements

2.0.0.372 changes

1. Techshare cleanup

2.0.0.371 changes

1. Update Techshare endpoint for CCSO Juvenile

2.0.0.370 changes

1. For Texas transactions, View Transaction did not properly show Ethnicity values of Unknown
2. Remove old unused SQL indexes

2.0.0.369 changes

1. mtxtwain.dll was missing from the 368 release

2.0.0.368 changes

1. SQL Indexing improvements
2. Better attempt to prevent multiple Fed Submit instances from different users
3. Improved TCN recycling
4. New SFTP/email library version

2.0.0.367 changes

1. NFIQ 2.3
2. Increase timeouts for TCN recycling

2.0.0.366 changes

1. Don't change the ORI to end with "H1" for APR transactions where the agency ORI does not end with "00"

2.0.0.365 changes

1. Fix problem with Citizenship ComboBox in OPM and JABS mode.

2.0.0.364 changes

1. Fix for rare ComboBox problem (Non-static method requires a target)
2. EBTS11 read/write fix for 1.004 field

2.0.0.363 changes

1. Fix for error that occurs when the Transaction Manager date range combo box is changed

2.0.0.362 changes

1. New barcode library version
2. Fix for Microsoft problem introduced in 361 release

2.0.0.361 changes

1. Added downgrade script for Firewire L Scan Essentials customers.

2.0.0.360 changes

1. L Scan Essentials 8.2.3

2.0.0.359 changes

1. L Scan Essentials 8.2.2

2.0.0.358 changes

1. L Scan Essentials 8.2.2

2.0.0.357 changes

1. Various accessibility improvements for ComboBoxes, TextBoxes, Tab Order, etc.
2. Update .NET Framework to version 4.8.1
3. Logon Window attempts to start as topmost window.

2.0.0.356 changes

1. Improved keyboard navigation throughout product
2. Miscellaneous accessibility improvements

2.0.0.355 changes

1. Fix to prevent reindexing tables after a tptables update, when reindexing tables is not allowed.
2. Ebts 11 XML support

2.0.0.354 changes

1. Attempted fix for domain name issue with GRPC version of IDMS service

2.0.0.353 changes

1. Fix for domain name issue with GRPC version of IDMS service
2. Fix problems with old TABLESDB path in clientdbs.xml

2.0.0.352 changes

1. Switch output form from BMP to TIF for FSCP Scan to File flow

2.0.0.351 changes

1. Attempt to fix problem recycling tcns for CCSO

2.0.0.349 changes

1. Fix for OSBI AST improperly set for a Municipal offense
2. Fix for issue with failed Azure tptables updates

2.0.0.348 changes

1. Fix for OSBI LVN AST requirement
2. Remove municipal statute dropdown in OSBI mode
3. IDMS improvements

2.0.0.347 changes

1. Support new OSBI LVN workflow
2. In OSBI mode, add statute dropdown for municipal statutes

2.0.0.346 changes

1. Fix OPM problem with OPM_CRI validation

2.0.0.345 changes

1. Fix OPM problem adding a new SON/SOI/IPAC value

2.0.0.344 changes

1. Fix installation issues with gRPC version of IDMS service

2.0.0.343 changes

1. Fix issues with simultaneous IDMS searches
2. Editing old TXDPS transactions could result in Demographic Check failures on the DOA field

2.0.0.342 changes

1. Fix issues with certificates used by Grpc IDMS service

2.0.0.340 changes

1. Active Directory support didn’t work in FSCP mode
2. Release Verification did not work correctly after importing a NIST file and then importing a left or right index
3. Initial support for Grpc version of IDMS Service
4. Update IB support to version 3.9.4
5. Update Rebex support
6. Avoid writing to \temp, \tmp, or \local folders
7. Don’t retry SaveFile errors when attempting to save to a local file
8. Eliminate segmentation debug files except when environment variable is set
9. In some cases, Rebex email did not work

2.0.0.339 changes

1. Search command didn't work properly with new FilterTotCondition

2.0.0.338 changes

1. Rebex license fix

2.0.0.337 changes

1. In FSCP, using ScanToFileFlow – usbe barcode from prescan as final barcode
2. In FSCP, using ScanToFileFlow – allow barcodes anywhere on the card.

2.0.0.335 changes

1. The 2.005 (retention code) setting was not properly initialized from settings.
2. The 2.005 field was not properly written to the NIST file in many "N" settings
3. Fed Submit is NIGC certified

2.0.0.334 changes

1. View Transaction did not reload and display data in some situations
2. New FTP/SFTP/Email API version
3. NIGC support for Web Services transaction submission
4. Submit Transaction Form could go into an infinite loop after submitting a transaction

2.0.0.333 changes

1. FSCP error message improvements when batch scanning with missing demographics files
2. Display of Type 7 front/back images didn’t work in FSCP

2.0.0.332 changes

1. Photo Report on the View Transaction Mugshot tab was broken
2. Display of Type 7 front/back images didn’t work in FSCP

2.0.0.331 changes

1. Barcode fix for new barcode new version
2. FSCP fix issue with batch processing form

2.0.0.330 changes

1. Barcode fix for new barcode new version
2. FSCP fix issue with batch processing form
3. Allow Municipal charges with a GOC values in OSBI mode

2.0.0.328 changes

1. New barcode recognition version
2. Optimizations for slow SQL connections
3. Allow GOC selection in OSBI mode for Municipal charges
4. Detect/report issue with double-click in transaction manager

2.0.0.327 changes

1. In Release Verification, return an error when attempting a search before the IDMS server has finished priming.
2. Table update problem fix.
3. Fix problem with certain reports
4. Fix synchronization problem creating work table

2.0.0.326 changes

1. Fix column name issue for two new columns in shared config table

2.0.0.325 changes

1. Startup optimizations
2. IDMS service fix error that occurs when db transaction doesn’t have all type 1 fields
3. The ReleaseVerification, SearchTransaction, and TransactionManager "Generate Report" functions were broken
4. Fix issue showing first transaction before selected transaction in View form

2.0.0.324 changes

1. Texas SIDs can now begin with a ‘2’
2. Some DOB issues were not properly conveyed to user during demographic checks
3. Improved barcode rectangle display for FSCP
4. BatchLog scrollbar did not appear on FSCP batch scanning dialog

2.0.0.322 changes

1. Fixed problem with R3 usage in FSCP
2. When opening J2K files (for example opening mugshot thumbnails) some temporary files were errantly not cleaned up

2.0.0.320 changes

1. When deleting a transaction, its template should be deleted from the Match database
2. Updated KBI batch scan flow to support a prescan to determine barcode/template before final scan
3. Exception processing flow for KBI batch scans
4. New report for KBI batch scans
5. FSCP reports were broken

2.0.0.319 changes

1. OPM FAUF and FANC transactions should not have a TSR field (2.043)

2.0.0.317 changes

1. Suppress corrupt NIST errors while freeing up TCNs
2. Add configuration switch to control whether or not database reindexes should be performed
3. Move database reindex to asynchronous thread during heartbeat

2.0.0.316 changes

1. Attempt to reduce problems on machines with low memory and not in WDOJ mode.
2. Attempt to handle exceptions when preack file cannot be moved to purge folder due to permissions.

2.0.0.315 changes

1. EAR file renaming should not occur during EAR import.

2.0.0.314 changes

1. Avoid exception when DOO isn’t entered in Texas DPS mode.

2.0.0.313 changes

1. Double-clicks were not properly ignored on some buttons (e.g. Import from RMS)

2.0.0.312 changes

1. Signature Pad OCX was not properly registered.

2.0.0.311 changes

1. Reduce heartbeat error messages for OSBI failed connections when VPN isn't active

2.0.0.310 changes

1. FSCP Batch Scan form now displays crop boxes and barcode boxes during scan

2.0.0.309 changes

1. Palm tab was not visible after Create from RMS in OSBI mode
2. Allow palm capture for Handgun application in OSBI mode

2.0.0.308 changes

1. Fix for problem with Edit and Resubmit introduced in 306 release
2. Camera exception fix.

2.0.0.307 changes

1. Fix for problem that occasionally occurs during Azure tables update
2. Fix for problem with bacpac table import
3. Attempt to better handle double clicks in Create From RMS
4. When Create Transaction button was pressed in livescan mode, the wrong TCN was passed to the livescan program, and a usage error dialog was displayed.

2.0.0.306 changes

1. Fix for some Camera exceptions when shutting down
2. Various WDOJ fixes
3. Miscellaneous FSCP fixes
4. FSCP ScanToFile flow for KBI

2.0.0.305 changes

1. Increase timeout for downloading new Fed Submit releases
2. Texas OLS, LIS, IDS, ADS fields should be limited to state codes
3. In Texas mode if a Class C offense has the DMV flag set, then the disposition must be 235.
4. Attempt to eliminate more double click problems when importing demographics

2.0.0.304 changes

1. Add diagnostics to Camera application to resolve issues at certain sites
2. Add handler for errors during display of Create Transaction form

2.0.0.303 changes

1. Remove requirement for DatabaseMaintenance script to install with sysadmin SQL rights.

2.0.0.302 changes

1. Reduce general memory usage in FedSubmit by not loading Matcher and Extractor until (and unless) needed

2.0.0.301 changes

1. Updated barcode library
2. Prevent double-click issues when starting release verification
3. Prevent double-click issues when clicking on “Create from RMS”

2.0.0.299 changes

1. Fix for compatibility with new Integrated Biometrics API

2.0.0.298 changes

1. Fix for compatibility with new Integrated Biometrics API

2.0.0.297 changes

1. Reindex/Reorganize all tables in heartbeat process
2. Reindex/Reorganize codes table after update
3. New version of Integrated Biometrics API

2.0.0.296 changes

1. various printing fixes, including updated TXDPS offense codes, TXDPS ORIs and Print to PDF fixes for ORI and offense codes

2.0.0.295 changes

1. Faster query to load code table information – should reduce occasional SQL timeouts

2.0.0.294 changes

1. 292 release created problems for customers that had previous WSQ -306 errors

2.0.0.292 changes

1. Properly check Agency Case Number length in TXDPS mode
2. Add additional checks for invalid Identification card number in TXDPS mode

2.0.0.290 changes

1. Updated matching engine
2. Updated WSQ library to fix -306 issue with nearly white images
3. Updated mail/ftp/sftp engine

2.0.0.289 changes

1. Fix TXDPS rules check for juvenile age to compare with Date of Offense to determine age at time of offense

2.0.0.288 changes

1. Force DOB to save in YYYYMMDD format for NIGC mode

2.0.0.287 changes

1. DMV fixes in Expunge
2. Fix TXDPS rules check for juvenile age to compare with Date of Offense to determine age at time of offense

2.0.0.285 changes

1. Failure to enter a DOO in JABS mode on a criminal transaction throws exception
2. Fix for problem after cancelling an RMS import
3. Fix exception that can occur for first transaction in a database
4. For EAR flow, change PREEARACK name to PREACK to avoid confusing New World

2.0.0.284 changes

1. Fix for problem with Edit & Resubmit that was introduced in the 283 release
2. DesktopNotifications fix
3. Editing the ORI in the Iris interface errantly change the type 1 ORI field
4. Possible fix for problem checking demographics when an APR transaction is created and then a CAR transaction

2.0.0.283 changes

1. Many palm scanning fixes for FSCP
2. SQL connections are now encrypted
3. Consistent quality scoring from Livescan interface to View interface
4. Segmentation improvements
5. Yaml path fix for NFIQ2.1
6. Failure to find barcode did not properly return error code
7. Wisconsin Offense Modifier fixes
8. Wisconsin STI initialization did not work correctly
9. Fix problem with scanning back images in FSCP
10. Thread safety fixes in low level C code (e.g. ImageDespeckle)

2.0.0.277 changes

1. Fixed rare problem with WSQ decompression (-306 error)
2. Fixed issue with attempt to stop WIA service when service isn’t running and user doesn’t have rights to stop service

2.0.0.276 changes

1. Fixed problems when switching between State and Municipal charges in OSBI mode.
2. Fixed rare problem when transaction with 1000 ppi prints is edited and resubmitted with 500 ppi prints.

2.0.0.275 changes

1. Fixed issues with thumbnails, expungements, and release verification related to TCN recycling.

2.0.0.274 changes

1. Fixed issue with ack file introduced in 272 release

2.0.0.273 changes

1. Fixed issue with ‘Skip’ button when scanning palms
2. Allow Palm capture with TFLU transactions

2.0.0.272 changes

1. Updated Techshare endpoint location to CCSO in house site
2. Change RMS ack file creation time for FS-XML and EAR to the time transaction is saved
3. New Barcode library
4. Updated tptables to include latest Texas Offense codes and WDOJ Offense codes

2.0.0.271 changes

1. Updated Techshare endpoint location

2.0.0.270 changes

1. Fix problem with Desktop Notification

2.0.0.269 changes

1. Fix problem printing court forms to PDF
2. Fix exception that occurs when no /temp folder exists

2.0.0.268 changes

1. Add button to View Form to print court forms to PDF

2.0.0.267 changes

1. Fixed memory leak when capturing back images with the R3
2. Print to PDF and Print Preview did not always display Signature or Mugshot images
3. NIGC mode fix for DOB format

2.0.0.266 changes

1. Wisconsin Account Number support was missing
2. Various fixes for WDOJ LESB/LEAP transactions

2.0.0.265 changes

1. Add indexes to Offense Code tables to address timeout issues on machines with minimal memory.
2. Various fixes for WDOJ LESB/LEAP transactions

2.0.0.264 changes

1. Auto-crop improvements
2. Better handling of rotated barcodes
3. Auto-card finding improvements
4. Remove some incorrect 2” slap height limitations during auto-crop
5. Some Oklahoma date checks could improperly fail during save of transaction
6. Switch to Visual Studio 2022
7. Improved crop of Ipevo images
8. Various improvements for VSP mode in FSCP
9. Improper max size check for AutoCrop of certain palm images
10. Palm images were not displayed on Front/Back image tab
11. Remove palm tab for Create when scanner doesn’t support palms or TOT does not support palms

2.0.0.262 changes

1. APR transactions should not have a 2.412 field
2. SkewTolerence is no longer needed for DATAMATRIX barcodes
3. Support recognition of more than 1 barcode on a form
4. Active Directory support did not work correctly if ConfigShared table fields were NULL
5. Share data read from tptables between View and Create structures to remove need to continually reread tptables
6. During AutoCrop allow heights of slap prints to be up to 3 inches
7. Add diagnostic code to check for WSQ error during compression, and preserve original image, if problem exists

2.0.0.261 changes

1. Fix for printing palm cards with missing palm images
2. Avoid writing too many EventLog messagings when using SFTP to download demographics

2.0.0.260 changes

1. Add Print to PDF capability
2. Fix problem printing more than 1 annotation on fingerprint card
3. Fix rare problem during autocrop

2.0.0.259 changes

1. Add ActiveDirectoryUsers and ActiveDirectoryAdmins fields to Shared Config table to allow juvenile and adult systems to support different sets of users/admins.

2.0.0.258 changes

1. Auto stop WIA service before using card scanner
2. Fix various formatting problems with CR43Js

2.0.0.257 changes

1. Reduce camera exceptions in heartbeats

2.0.0.256 changes

1. Fix errant heartbeat exceptions relating to Camera use when window manager close is clicked
2. Enforce maximum of 12 AKAs in Texas mode
3. Import of SMT photos was broken for FS XML files

2.0.0.255 changes

1. Fix printing problem introduced in version 254.

2.0.0.254 changes

1. AKA format was not properly checked during save, causing occasional MNC responses.
2. Certain operations could cause an exception when running with an empty database.
3. Add warning and error message notifications for certain camera events.

2.0.0.253 changes

1. Fix infinite loop problem that could occur when CrossMatch scanners have sequence check issues due to low quality prints
2. Fix exception that could occur with TechShare integration

2.0.0.252 changes

1. Camera interface did not work for older cameras
2. Print to PDF did not handle strings with carriage returns
3. Change the PrintCR43 button on the View interface to print to both PDF and printer, if both auto-print options are configured.

2.0.0.251 changes

1. Fix issue (introduced in release 250) with DOA for SOR transactions

2.0.0.250 changes

1. Fix another problem with DOA in TXDPS mode introduced in 247 release
2. Fix problem in Release Verification introduced in 244 release

2.0.0.249 changes

1. Fix problem with DOA in TXDPS mode introduced in 247 release
2. Add many new demographic checks in WDOJ mode

2.0.0.248 changes

1. WDOJ DOA fixes
2. Only add unique AKAs when importing a FS XML file
3. Limit AKAs to a maximum of 12 when importing a FS XML file
4. Only add unique DOBs when importing a FS XML file

2.0.0.247 changes

1. Correct typos on Configure form
2. Avoid exception with swipe card reader when height is “”
3. Suppress additional camera exceptions
4. DOA check was not working correctly when saving a transaction
5. Unhandled exception was being thrown while viewing a transaction in WDOJ mode
6. In non-TXDPS mode entry of 01/01/1980 for DOB didn’t work properly
7. DOA initialization only worked correctly in JABS and TXDPS modes

2.0.0.246 changes

1. Fix for checking all zero TRN when not running on a domain.
2. Correct many typos on the Configure form.

2.0.0.245 changes

1. Don’t allow TRNs with all zeros in Texas mode.
2. Reading responses in WDOJ mode could throw an exception and discard the response.
3. Certain jobs would crash with a 1 character SID
4. Avoid overwriting demographic import files from an SFTP source
5. Avoid exception when DOB is less than 8 characters

2.0.0.244 changes

1. NFIQ2.1 startup fix for problem introduced in release 243
2. Fix for conflicting TCN problem in release verification

2.0.0.243 changes

1. Release Verification Transactions did not properly show photos
2. Fixes related to DOB usage in demographic checks
3. PhotoExport and XMLExport did not properly log/retry failed exports
4. TXDPS Version 18 Offense codes

2.0.0.242 changes

1. FD258 printing improvements including printing signatures
2. Fix problem with Edit and Resubmit in FBI mode
3. Restart Fingerprint Scan only displays warning if prints have been scanned
4. Properly clear displayed fingerprint images when Restart Fingerprint Scan is selected.

2.0.0.241 changes

1. Fix for problem cancelling transaction in livescan interface

2.0.0.240 changes

1. Change functionality of Edit and Resubmit to not create a new TCN, if the transaction had not been submitted

2.0.0.239 changes

1. Window manager close of livescan, prevented subsequent save of created transaction.

2.0.0.237 changes

1. While doing a card scan, if user selected save before scan was complete, it was no longer possible to save transaction

2.0.0.236 changes

1. Fix for Iris scanning problem introduced in version 228

2.0.0.235 changes

1. In TXDPS mode, allow users to print CR-43s without all responses if warning is accepted

2.0.0.234 changes

1. In OSBI mode, palm print check at time of save was not correct

2.0.0.233 changes

1. Prevent creation of extra WORKDB in clientdbs.xml when creating new database

2.0.0.232 changes

1. OCA MNC fix for SOR transactions

2.0.0.231 changes

1. Display error message if no TOT is selected from Create popup

2.0.0.230 changes

1. Camera interface did not detect/handle second camera interface running in another application

2.0.0.229 changes

1. Camera interface did not correctly handle window manager close

2.0.0.228 changes

1. XmlPurge did not properly handle permissions problems

2.0.0.227 changes

1. Fix performance issue with NFIQ 2.1

2.0.0.226 changes

1. Fix issue with WDOJ Edit and Resubmit combo boxes

2.0.0.225 changes

1. Fix improper check for AON 13999999 with ADN of 233

2.0.0.224 changes

1. Create from JMS errantly called GetNextTcn twice resulting in the wrong TCN being written to .ack file

2.0.0.223 changes

1. WDOJ applicant response special handling
2. WDOJ Bugfix for Arrest segment
3. AutoPrint setting fix for Create Form
4. Don't allow special characters in WDOJ OTP field
5. Allow slap prints of 3" height in livescan interface

2.0.0.222 changes

1. WDOJ fixes for Offense information selection

2.0.0.221 changes

1. Don’t check quality for slap prints during Save Transaction
2. By default, do not retry failed SFTP transmission as an FTP transmission
3. Fix another EBTS Texas DOB check
4. Remove unused JMS options

2.0.0.220 changes

1. Fix problem launching Signature Pad capture

2.0.0.219 changes

1. Fix NFIQ labeling errors in livescan interface
2. Various fixes in livescan UI interface

2.0.0.218 changes

1. Do not permit submission of TX transactions with ADA > DOA if local time is between 2345 and 0015
2. Try to add compatibility for multiple monitor support for scan interface (especially, to enable testing using second, smaller monitor)
3. Avoid slow heartbeat during exit

2.0.0.217 changes

1. UI improvements in Livescan interface
2. US not valid OLS for Texas
3. Fix EBTS XML fie generation to properly handle multiple CRI values in Record-separated list
4. Bugfix for false warning with existing CRI value in FAA mode and TechShare null SID issue
5. Bugfix for verifying and validating AND
6. Add code to upgrade FedSubmit database indexes at login time (hold ctrl key + yes to confirm).
7. Bugfix to check for missing OCA / TRN
8. Improved handling of unconfigured court forms printer

216 changes

1. Scan interface support for 2 monitors
2. Techshare fix for transaction without SID
3. ReleaseVerification search initiated in background thread. Multiple clicks on 'search' could cause overlapped search operations initiated causing enroll crash.
4. Clean up release verification live scan cancel handling

2.0.0.215 changes

1. Updated NFIQ2.1 release
2. Detect/Log certain matching failures
3. Bugfix to allow processing of 16 year old Juvenile offenders in Texas
4. Larger livescan window (dependent on screen resolution)
5. Only display zoom/recapture buttons on livescan interface when usable

2.0.0.214 changes

1. Incorrect quality code order for left slaps on livescan interface
2. Fix WDOJ TOT error for MAP – LESB and LEAP transactions

2.0.0.213 changes

1. POB bugfix
2. JABS create bugfix
3. TXDPS DOB issue should not allow user to continue
4. Fix for incorrectly import date field in TXDPS mode
5. WDOJ initialization fix
6. Increase matching threshold to reduce false matches that were occurring for facial recognition
7. User and scanner fields were not initialized for WDOJ non-CAR transactions

2.0.0.211 changes

1. NFIQ2.1 support
2. New Canon camera SDK
3. OPM fixes for OCA and RFP
4. Add netTcpBinding option to fsIdms
5. Adjust DOB print area for CR-6 form
6. Fix DataTemplates problem for Remote ID
7. Improved diagnositics for Remote ID

2.0.0.210 changes

1. WSQ support working for Android x86 mode
2. Update IB Support to IB ScanUltimate 3.7.1
3. Bugfix for date picker

2.0.0.209 changes

1. Fix for DOB in WDOJ mode

2.0.0.208 changes

1. PDF response files are now written to ResponseExportDir
2. WDOJ Bugfixes
3. Update to latest SecuGen libraries (4.0.3)
4. Update Matching engine to 12.1
5. Fix for matching enrollment of grayscale mugshot images
6. Card scan slap images now allowed to be up to 3 inches in height
7. Various WDOJ FSCP Bugfixes
8. Remove erroneous debug slap/segmentation image saves to %tmp%
9. Fix issue with tab change (Create/View Transaction)

2.0.0.207 changes

1. Fix for TabControl Exception
2. Update Closed fixes – including closing “DO NOT SUBMIT” transactions
3. IB active finger display fix

2.0.0.206 changes

1. Fix type checking issue with Edit and Resubmit

2.0.0.205 changes

1. Print preview fixes

2.0.0.204 changes

1. FBI and NIGC mode did not allow importing or Edit and Resubmit capabilities

2.0.0.203 changes

1. Update OpenCV to version 4.5
2. Bugfix for Wisconsin Offense selection
3. Do not allow 00/00/0000 entry for DOB in TXDPS mode
4. Updated email/ftp/SMTP library
5. Sequence Check did not properly force recaptures for IB scanners

2.0.0.202 changes

1. New version of Canon SDK
2. Fix problem printing CR43s
3. Only release 64-bit versions of Fed Submit
4. After creating a transaction set current view transaction to that transaction

2.0.0.201 changes

1. PSP fix

2.0.0.200 changes

1. Alias DOB fix

2.0.0.199 changes

1. DOB fix
2. IB 3.6 SDK

2.0.0.198 changes

1. PSP DOC field fix
2. DOB > 2000 fix for TXDPS

2.0.0.197 changes

1. DOA fix for TXDPS
2. PSP OCA width 30 support
3. When printing or previewing, slap prints should not extend into rolled print area
4. PSP changes to handle latest requirements

2.0.0.195 changes

1. Add support for printing CR43s in PDF format

2.0.0.194 changes

1. ComboBox Performance improvements for WDOJ Offense field
2. Improved cropping of flat prints greater than 3.2 inches
3. Better segmentation of inked prints

2.0.0.193 changes

1. WDOJ fix for populating NCIC code automatically
2. DOB printing fix
3. Resolution fix for J2K saves, which fixed batch processing issue for FSCP

2.0.0.192 changes

1. TXDPS DOA fix
2. Improved generalized date printing
3. Improved crop function for live scan flat prints

2.0.0.191 changes

1. Fix for scanning back of card with R3
2. DOB printing fix
3. Improved display of fingerprints for card scan transactions

2.0.0.190 changes

1. Fingerprint segmentation fixes
2. Fix problem restarting livescan palmprint scan

2.0.0.189 changes

1. Add diagnostic information for -306 WSQ error images
2. Livescan fix for capturing all prints
3. Force DOB format for TXDPS sex offender transactions
4. TRN/OCA fix for TXDPS sex offender transactions
5. FSCP Transaction Manager fix
6. RFP enabled for FBI mode in create transaction
7. Wrong fingers shown for right hand after segmentation
8. Fix issue with Re-Scan button in livescan interface
9. Fix for left slap magnify button in livescan interface

2.0.0.188 changes

1. Livescan startup form minimization fix

2.0.0.187 changes

1. Left four slap magnify button wasn’t enabled in livescan interface
2. Inked fingerprint segmentation improvements
3. FBI support for WPF Fed Submit

2.0.0.185 changes

1. New feature showing quality check information for segmented fingers
2. Fingerprint segmentation fix
3. Fixes for new livescan interface

2.0.0.184 changes

1. Fix for problem automatically cropping fingerprint images
2. Magnify fix in new livescan interface

2.0.0.183 changes

1. Recapture for sequence checking fix in new livescan interface

2.0.0.182 changes

1. Recapture single finger fix in new livescan interface
2. Hit count fix for Release Verification
3. Filter out RelVer and RPIS transactions for Release Verification
4. IB device fix for new livescan interface
5. Add support for 4-4-2 captures in new livescan interface
6. Improved error messages for failed startup of services

2.0.0.181 changes

1. Release Verification re-livescan UI fix
2. TXDPS SOR transaction fixes
3. New livescan interface with NFIQ scoring information
4. Fix for impression type setting in type 4 records for card conversion
5. Fix for RPIS task type
6. Fix issue with blank RPIS tab on view transaction
7. Fingerprint names were mis-labeled on RPIS transactions

2.0.0.178 changes

1. Rescanning a single print that was previously skipped did not correctly set the annotation flag
2. For livescan captures with all rolled prints marked as annotated, the slap print was errantly excluded from results

2.0.0.176 changes

1. Fix for fingerprint bounding boxes when creating new transaction
2. Right ring finger was errantly displayed in right little finger window in livescan interface
3. Configure form fix

2.0.0.175 changes

1. Fix for TechShare null SID
2. Create LocalPhotoExport folder if it doesn’t exist
3. Secugen 64-bit fix
4. Add Subject/Operator signature pad options to the FSCP configure form
5. Refresh segmentation data on restart of livescan or cardscan

2.0.0.174 changes

1. Quality check label fixes
2. Segmentation improvements
3. OSBI quality check
4. UI improvements for Fingerprint tab
5. 1000 ppi card scanning fixes for Fed Submit in WPF mode
6. Add quality check display for individual slap fingers and thumbs
7. Add quality check for cardscan transactions
8. Check fingerprint quality when saving a transaction
9. Support TXDPS DOBs for ages up to 125 years

2.0.0.173 changes

1. Add support for NIGC mode in Fed Submit WPF
2. JABS mode fixes
3. Configure form fix for JABS mode

2.0.0.172 changes

1. Rotation fix for some cameras

2.0.0.171 changes

1. Fix error message when connecting a Cross Match 3.0 USB device to a USB 2.0 port
2. When importing a NIST file, preserve T2_IMA field values

2.0.0.170 changes

1. Fingerprint segmentation improvements

2.0.0.169 changes

1. Use RebEx SDK to send single-part Mime messages

2.0.0.168 changes

1. Add support for Tables updates via Azure

2.0.0.167 changes

1. Jenetric scanner support

2.0.0.166 changes

1. 12000XL support fix for non-R3 situation
2. Bacpac connection string fix

2.0.0.165 changes

1. WDOJ support in Fed Submit WPF

2.0.0.162 changes

1. Bacpac link table fix
2. Memory leak fixes

2.0.0.1615 changes

1. Fix for tpl files that reference XML files
2. Add format support to printing for formal dates (e.g. 27th of April, 2020)
3. Support printing field values with underline or italics attribute
4. Print preview window is based on the card definition height
5. Add 4-4-2 template for printing

2.0.0.161 changes

1. Add support for printing characters like §
2. Fix for ORI lookup during printing

2.0.0.160 changes

1. New matching engine version

2.0.0.159 changes

1. New Canon SDK
2. Store image thumbnails in J2K format to reduce size of Thumbnails table
3. Threading issue fix for J2K load/save
4. Memory leak fix

2.0.0.158 changes

1. JABS T2_TAA fix importing existing transactions
2. Distribute Tables file in .bacpac format removing need for Access Database Engine (ADE)

2.0.0.156 changes

1. Blank palm templates could cause an exception for customers that don’t use palms
2. Switch to Microsoft.ACE.OLEDB.16.0 JetDatabaseAccessEngine
3. Camera fixes for unhandled exceptions

2.0.0.152 changes

1. Fix for Must Create DependencySource on same thread as the Dependency Object problem
2. Bringing up the Camera dialog and closing (i.e. not taking a picture) could cause an exception

2.0.0.151 changes

1. OSBI special print card/form support

2.0.0.150 changes

1. Camera interface fixes
2. 64-bit support fixes

2.0.0.149 changes

1. Permanently disable LVN and LVC transactions for OSBI

2.0.0.148 changes

1. Add Subject/Operator Signature checkboxes to configure (replacing SignaturePadEnabled)
2. Fix issue with Fingerprint tabs in View Transaction

2.0.0.147 changes

1. Top Level Form did not correctly display the serial number
2. Auto opening configure form caused problems

2.0.0.146 changes

1. Don't display warning messages at startup for services that are not installed.
2. Remove TPInit failed message
3. Don't do license check during TpInit
4. Fix Sequence check bug introduced in adding 4-4-2 support
5. Set default DPR field properly
6. TXDPS OCA fix
7. Hide angled offsets while capturing mugshots

2.0.0.145 changes

1. Fix for various required TXDPS fields
2. 4-4-2 fingerprint capture support
3. Add configuration switches to require: DPR, DOB, Operator, and OCA

2.0.0.144 changes

1. Memory leak fixes

2.0.0.143 changes

1. Handle exit problems in Camera control program

2.0.0.142 changes

1. 64-bit Fed Submit support

2.0.0.141 changes

1. Card scanner fixes for palm scanning
2. Orientation fixes for card scanning
3. Documentation link fix

2.0.0.140 changes

1. User Guide fix
2. Quality check fix

2.0.0.139 changes

1. Various documentation fixes
2. New xml parser

2.0.0.138 changes

1. Compression ratio fix for Configure form

2.0.0.136 changes

1. Exclude RelVer transactions from Release Verification search results
2. MRJ response handling fix

2.0.0.135 changes

1. correctly import JPEG files with EXIF rotation information
2. Fix for sequence check

2.0.0.134 changes

1. Sequence check fix
2. Remove T2_DPR check for JABS

2.0.0.133 changes

1. Remove ER2 segment from APN transactions

2.0.0.132 changes

1. Delete encrypted files during autoimport

2.0.0.131 changes

1. fsLiveScan control file writing fix

2.0.0.014 changes

1. New Neurotec matching engine
2. Modify USB scanner open code to only use StillImage service if WANT_STILLIMAGE environment variable is set. The NO_STILLIMAGE environment variable is now deprecated.
3. USB Scanner open code now attempts to open specific address, and if that fails tries all addressed until it finds desired device. Note that this code may not work as desired if multiple instances of the same scanner are connected.
4. Updates and various bugfixes for OSBI
5. Fix issue with edit and resubmit not reading fingerprints from original transaction
6. Fix issue with OSBI_AST and add exception handling for Texas offense

2.0.0.010 changes

1. Fix for scanning issue where FingerprintCard structure is freed by garbage collector while still being used by asynchronous thread
2. Improved handling of failure to open Arduino Port
3. UI Bugfix for TexasWaiverForm
4. Visual Studio 2017 (ToolsVersion="15")
5. Bugfix for AKAS popup going off-screen

2.0.0.007 changes

1. Fix exception reading blank zip code with swipe card reader

2.0.0.06 changes

1. Bugfix for non EDSDK cameras issue introduced in v221

2.0.0.005 changes

1. Bugfix for OSBI Offense Literal

2.0.0.004 changes

1. Remove references to older Windows 10 SDK versions 10.0.16299.0, 10.0.17134.0 and replace with 10.0.17763.0

2.0.0.003 changes

1. Fix bug introduced in 2.0.0.0 release updating TPL/XML path in database

2.0.0.002 changes

1. New fsIdmsRemoteID UI
2. Limit maximum remoteid hits to 25
3. Fix bug introduced in 2.0.0.0 release updating TPL/XML path in database
4. R3 back image crop fix for case where back door doesn’t open

3.2-000n.2.0.0.0 changes

1. OSBI fixes for printing No hit responses, applicant cards, and the OSBI criminal card
2. Allow printing .tpl templates in Fed Submit
3. Better R3 error handling
4. Add hierarchy to templates so that TXDPS customers don’t need to see OSBI templates, etc.

224 changes

1. Use Adaptive Threshold to convert CalDOJ front and back images to lineart

223 changes

1. Fix CDOJ CardType codes

222 changes

1. Fix bug when saving multipage tiff file and original file is compressed tiff image

221 changes

1. Eliminate BitmapSourceToFpuImage() for Mugshots and SMTs while saving

220 changes

1. Fix and improve insensitivity of buttons in Batch San Form (FSCP)

219 changes

1. display message when no scan is attempted with no cards

218 changes

1. Reduce warnings for EWS receive (New London)

217 changes

1. Second scan with R3 didn't work

216 changes

1. GOCA list fix

215 changes

1. fixes for WDOJ response handling

214 changes

1. Fix for FSCP CDOJ Submit Transaction

212 changes

1. Case entry not needed for Ohio Card Conversion + Update Ohio EFT file generation

211 changes

1. New FSCP Configure Form WPF

210 changes

1. Fix problem introduced in release 208, restricting print templates to .tpl versions

209 changes

1. CDOJ FSCP Updates (Add JobType and CardType)

208 changes

1. Updates on FSCP (Alternate UI for Skip, Next, Discard etc)

207 changes

1. IIDS Bugfix

206 changes

1. More robust palm type detection

205 changes

1. Fix Tab Indexes for CDOJ UI

204 changes

1. Various CDOJ + OSBI Updates

200 changes

1. TFLUS did not have an ORIA field

199 changes

1. OSBI changes for Filing and Disposition reports

198 changes

1. Back images were not saved in FSCP using R3 (because NoteScanComplete had a threading problem)

197 changes

1. FSCP Bugfixes

196 changes

1. Updated IIDS spec info

195 changes

1. Fixes for various Iris image issues

194 changes

1. Fix for exception when doing an Iris capture from the camera

193 changes

1. OSBI bugfixes + missing ORI bugfix for Type 10/17 records

192 changes

1. FSCP + CDOJ Updates

191 changes

1. Iris Serial Number was not properly written to NIST file

190 changes

1. CDOJ Updates (More data sources) + Various bugfixes

189 changes

1. Attempt to add support for ERRB responses

188 changes

1. Fix various Iris DME issues

187 changes

1. Fix issue with image lock on Mugshot/SMT/Iris tabs.

186 changes

1. Fix problem downloading TXDPS IIDS responses

185 changes

1. Attempt to fix problem downloading TXDPS responses without IIDS folder

184 changes

1. Various Bugfixes (Batch Form, UI, Mugshot SAP...)

183 changes

1. Back out change suggested change to avoid reading all Nist data during view

182 changes

1. Fix problem with initialization of auto print after create of transaction

181 changes

1. Fix exception "SqlException: String or binary data would be truncated." when adding invalid arrest information into the work table

180 changes

1. Another attempt at handling bug introduced by memory leak fix

179 changes

1. Attempt to gracefully handle incorrectly formatted EAR files from CRIMES

178 changes

1. The Ls object should only be used inside of the fsLiveScan process

177 changes

1. Attempt to update help documentation for TXDPS

176 changes

1. Fix issue with DOB (00/00/0000) while doing Edit and Resubmit WPF

175 changes

1. CDOJ Updates (Finish IDN Tab)

174 changes

1. Support importing .png and .jpeg images for Release Verification

173 changes

1. Properly handle CCSO TRNs that begin with 'C' (WPF)

172 changes

1. Add Iris Search (IIDS) TOT in TXDPS

171 changes

1. Add Iris DB variables

170 changes

1. .Net Framework 4.7.2

169 changes

1. Fix for scanning certain heights with the Epson Expression 12000XL

168 changes

1. Fix printing problem in Access version

167 changes

1. Fix FSCP issue with configure form

166 changes

1. CDOJ Updates

165 changes

1. DPS no longer wants "SR" at the end of ORIs for SOR transactions

164 changes

1. Fix to check for Incorrect card/template path in Configure Form + Initialize AppDbDir in WPF (i.e. fix for downloaded demographics problem at Howard)

163 changes

1. Remove MDoEvents calls on WPF Forms

162 changes

1. New icons for Fed Submit, etc.

161 changes

1. Check SQL Server Status before attempting a connection

160 changes

1. Fix for problem in OSBI mode (Access) where entering a literal for a Municipal charge could result in the statute being erroneously populated.

159 changes

1. Fix for OSBI Offense literal

158 changes

1. Fix 'Receive Service' checkbox's binding in Configure Form WPF

157 changes

1. Attempt to fix Access Is Denied error when checking if Camera process has exited.

156 changes

1. Added debug to detect old RemoteID client with new IDMS service

155 changes

1. Fix scale bug for 16-bit data

154 changes

1. Updates on Configure Form WPF (Added NMDPS, WDOJ, CBI, Utah, JABS, NIGC, FAA, MT Tabs)

153 changes

1. Make TRS field editable in WPF interface

152 changes

1. Configure form bugfixes and improvements

151 changes

1. Configure form fix

150 changes

1. Retarget C projects to VS 2017

149 changes

1. OSBI Bugfixes for Palm annotations in Access

148 changes

1. Do not use ‘C:\temp’ folder – which can result in print jobs repeating (Garfield) infinitely

147 changes

1. Test Release for Sachse

146 changes

1. Test Release for Sachse
2. Launch Camera Interface in its own process

145 changes

1. Applied FTP download fix recommended by RebEx for Sachse

144 changes

1. OSBI Offense ComboBox update (WPF)

143 changes

1. New OSBI Offense Code Table

142 changes

1. Test release for Sachse FTP problem

141 changes

1. Update Intel Redistributables, and Visual C++ Redistributables in release

140 changes

1. Miscellaneous OSBI Bug fixes (WPF)

139 changes

1. Fix: Missing Fingerprint AMP/UP/XX Code Issue

138 changes

1. Fix MNC errors in WPF for last names containing a space

137 changes

1. New WPF Submit Form

136 changes

1. Improved autocomplete for WPF comboboxes (e.g. Offense Codes)

135 changes

1. In AD mode, Create From JMS was never enabled.

134 changes

1. Fix for card scan error on create transaction

133 changes

1. Attempt to remove heartbeat messages where there is a timeout downloading from TXDPS SFTP site

132 changes

1. Add capability to rules to restrict special characters in fields and report conflicts in validation

131 changes

1. Attempt to reduce likelihood of two services trying to simultaneously heartbeat

130 changes

1. First cut at adding XML export as an option

129 changes

1. Added L Scan Essentials check for replace pad warning that Guardian 200 scanner can produce, and treat all device warnings as warnings, allowing user to continue

128 changes

1. Camera interface was not compatible with 127 release fpuInit changes

127 changes

1. Do not heartbeat prior to calling FpuInit

126 changes

1. Avoid exception during heartbeat at startup checking NIST XML

125 changes

1. R3 photo back image capture functional in FSCP

124 changes

1. OSBI Auto OTN generation fix (WPF)

123 changes

1. Partial support for R3 camera

122 changes

1. First Visual Studio 2017 build

121 changes

1. TXDPS ETH bugfix in WPF version