Follow F-Register development from the initial beta to the current release, including new features, improvements and security updates.
Current version1.0.111
Early beta versions are summarised by development series because individual public patch notes were not recorded at the time. From the current development phase onward, every new release receives its own entry.
Stable release
1.0.111
Clear fallback text for payment statuses
An unknown payment status receives a readable label in the user’s language. Known statuses and financial history are retained.
Readable fallback text in Dutch, English, German and French for an unknown or missing order status.
Stable release
1.0.110
Credit orders with clear cancellation reasons
Unpaid credit orders retain a clear status and reason. Pending and uncertain payments are not cancelled solely because of their age. Financial history is retained.
Cancelled with reason Payment declined or failed, or Order abandoned, based on confirmed status.
Expired orders without any payment attempt are closed in bounded batches without starting payments or changing credits.
Administrators and planners can view the latest 50 credit orders in the balance overview.
A later confirmed payment is still credited exactly once.
Both monitor paths share one support-date parser.
Stable release
1.0.109
Clear AI credit messages and reliable update checks
This release clarifies document pricing and credit messages, prevents unnecessary repeat reading and preserves the last confirmed installation status when checks fail. The manual also covers previously added AI support for photos, quotations, calibration and follow-up work.
Quotations and calibration reports share clear document and credit messages.
A one-credit request uses the correct singular insufficient-balance message.
An already-read calibration report points to its existing proposal without another read.
Failed status checks retain the last confirmed version and status payload.
The standard updater confirms the expected version and package identity after installation.
Release checks report a missing credit wallet explicitly instead of displaying an invented zero balance. AI installation summaries are not released.
Stable release
1.0.68
AI serial number recognition and better photo references
Read a serial number from a typeplate photo. The technician checks the suggestion and can edit it. Work orders, document folders and the handbook have also been improved.
AI suggests the serial number for outdoor and indoor units. Existing values are preserved; saving remains an explicit action.
The photo remains available for reference even if recognition returns no result. Each saved unit keeps its own photo; a new indoor unit form does not display the outdoor photo.
Work order summaries give descriptions and signatures more room. Report folders show work order numbers instead of internal IDs.
The final handbook includes clearer download names, text corrections and page breaks. Company-specific versions and existing publications are preserved.
Clear messages explain network errors and usage limits. AI usage is monitored centrally with a monthly budget per company.
Stable release
1.0.35
Collapsible customer portal and clear fault labels
Portal sections start closed, faults show the appropriate asset name and the public QR subtitle is shorter. Mechanics can directly start their own saved draft work order. Includes settings, security and timezone improvements.
Customer portal: installations, technical data, boilers, appointments, work orders, documents and address sections toggle through their headings. Validation failures reopen the affected form.
Fault reporting uses Installation, Appliance or Vehicle according to the selected asset. Disabled specialties are not selectable.
The public QR subtitle is shortened. Customer name, street, city, notes and documents are not displayed. The existing installation identifier may still contain a postcode and house number.
Includes 1.0.34: mechanics can reopen and start their own unplanned draft, while existing authorization and signing controls remain intact.
A valid saved company timezone remains selected even when it is absent from the default options.
Includes previous settings, security and timezone fixes. Historical timestamps are not rewritten; old naive timestamps may display differently. Existing naive expiry values may temporarily remain valid one to two hours longer; scheduled tasks follow company time.
Catalog integration pilot release
1.0.37
Read the technical unit catalog safely
A separate catalog.read permission exposes indoor and outdoor unit types for webshop import. No customers, installations, serial numbers or document paths. Claude reviewed this exact candidate live on test-laravel. Remains TEST: not released as a stable production version.
New paginated read-only catalog API with brand and model filters.
Only explicitly allowed technical fields are exported. Missing indoor specifications and MFA values are not invented.
Includes TEST 1.0.36 quote import improvements. Webshop import uses a separate review preview and retains prices, photos, color variants and compatibility links.
Quote import pilot release
1.0.36
Safe installation creation from a quote webshop
Quote imports leave installations uncommissioned, preserve existing catalog data and retain indoor unit pump choices. Included in Claude's live review of TEST 1.0.37. Not separately released as a stable production version.
New quote installations are not activated before commissioning.
Imports do not overwrite existing catalog specifications, document links or manually selected series. Missing installation specifications are filled from the known outdoor model.
Condensate pump choices are validated and stored per indoor unit. Repeated quote imports return the same result.
Own draft work order pilot release
1.0.34
Start a previously saved own work order
Mechanics can reopen and directly start their own unplanned draft work order. This candidate remains TEST, exclusively on test-laravel, until Claude independently rechecks the exact live release.
Start now remains available on a saved own unplanned work order. Direct start uses company time, default duration and the existing history and planning workflow.
Unplanned orders created by others, planning assigned to another mechanic, completed orders and inactive mechanics remain protected. Normal editing and signing permissions are unchanged.
The shifted-planning notice is translated correctly when creating an ad-hoc work order.
Includes the security and timezone improvements from TEST candidate 1.0.33. Historical timestamps are not rewritten; old naive timestamps may display differently. Existing naive expiry values may temporarily remain valid one to two hours longer; scheduled tasks now follow company time.
Timezone and security pilot release
1.0.33
Company timezone, clear planning notices and security updates
Targeted improvements after Claude's live review of 1.0.32. This new candidate remains TEST, exclusively on test-laravel, until independent live re-review is complete.
New automatic timestamps follow the valid company timezone, including daylight saving time. Historical timestamps are not rewritten.
Company settings accept only valid timezones. The existing settings cache is reused.
Start now displays a clear notice that existing planning was retained when confirmation is missing.
The mobile queue anchor leaves space below the sticky top bar.
Laravel, CommonMark and Flysystem are updated to patched versions.
Pilot release after live review
1.0.32
Safe work order status, indoor unit updates and local QR codes
Fixes for the blocking live review findings and targeted improvements to planning and forms. This candidate remains TEST and is deployed only to test-laravel for independent re-review.
Mechanics cannot use manual status changes to bypass signing. Final manual status corrections require an existing signature and signing timestamp.
Indoor units are updated through their own update route, including after initial save or OCR autosave.
QR codes on nameplates and indoor labels are generated locally without sending installation tokens to an external service.
Start now requires confirmation before replacing existing planning; the server checks this confirmation.
Heading placeholders and notices after starting ad-hoc are resolved correctly.
The queue anchor and accessible sidebar button name are corrected.
Pilot release re-review
1.0.31
Reliable storage measurement and minimized login activity
Improvements from the independent settings and monitor review. This pilot release remains available only on test-laravel.
Storage measurements have their own timeout without limiting regular uploads.
Only staff logins are recorded; customer portal and support logins are excluded from the monitor overview.
Historical status checks are cleaned of personal login activity.
Reordering visible tiles preserves the positions of restricted tiles.
Cooling audits follow the active specialty.
Cron remains silent on success and reports repeated failure only once until recovery.
Settings and tenant overview pilot release
1.0.30
Settings by specialty and configurable tile order
General CRM and cooling settings have separate screens. Active additional specialties have their own overview. The monitor displays installations, work order statuses, recent logins and measured bucket usage. This pilot release is deployed only to test-laravel.
Move settings tiles and save or reset their order per tenant and specialty.
Combustion and vehicle settings are visible only when their specialty is active.
The monitor displays installation and work order totals, grouped by stored work order status.
Successful logins are retained for up to 90 days, without passwords, email addresses or IP addresses.
Bucket usage is measured in the background; status checks do not need to request stored files.
Updates verify the login activity table, indexes, frontend build and file permissions.
Internal labels pilot release
1.0.29
Internal labels for customers, locations, installations and work orders
Manage labels with a name, description and color and use them to filter internal overviews. Labels are excluded from the customer portal, public reports and API responses. This pilot release is deployed only to test-laravel.
Manage labels in Settings and assign them to customers, locations, installations and work orders.
Filter overviews by label while preserving search and pagination.
Clear 2 px colored borders, centered help buttons and compact mobile filters.
Save labels without page reloads, lost notes or unexpected focus changes.
Database relationships support existing INT and BIGINT installations and are verified after updates.
Three modules and separate specialties
1.0.28
Included forms and imports, clear requests and preserved audit evidence
Integrations, maintenance and faults are the three optional modules. Forms and imports are included. Requests display their status and completed requests remain archived; audits follow the selected specialty.
API, Webhooks and external integrations includes Teamleader; Faults includes WhatsApp Business.
Requests display Requested and prevent duplicates; completed requests leave the open monitor queue.
Cooling, combustion appliances and transport have separate audits and exports. Customers can request only the three available modules.
Custom actions and forms, Universal import and Climapulse import are included.
Tool history and original calibration evidence are preserved, including after reopening a completed work order.
Post-update repairs a missing bug-report outbox even if its migration was already recorded.
Module and audit evidence pilot release
1.0.27
Included forms and imports, clear requests and preserved audit evidence
Integrations, maintenance and faults are the three optional modules. Forms and imports are included. Requests display their status and completed requests remain archived; audits follow the selected specialty.
API, Webhooks and external integrations includes Teamleader; Faults includes WhatsApp Business.
Requests display Requested, prevent duplicates and remain recoverable after a monitor outage.
Cooling, combustion appliances and transport have separate audits and exports.
Tool records are locked after completion or signing; new calibration reports do not overwrite historical evidence.
Post-update repairs a missing bug-report outbox even if its migration was already recorded.
Module and specialty pilot release
1.0.26
Three optional modules, visible requests and separate audits
Custom actions and forms and both imports are included in F-Register. Integrations, maintenance and faults are the three optional modules; requests display their status and completed requests remain in the monitor archive.
API, Webhooks and external integrations includes Teamleader; Faults includes WhatsApp Business.
New requests are shown as Requested without duplicate submissions; completed requests leave the open queue.
Cooling, combustion and transport audits are separated and respect the specialties enabled in the monitor.
Safer tool deletion and more reliable bug reporting to the monitor.
Field-aware conditions
1.0.25
Appropriate answer choices and comparisons in the form editor
Select actual checkbox, checklist and choice-field answers for visibility and conditional requirements. Text, date, time and numeric sources use appropriate inputs and comparisons.
Answer choices are taken from the selected field, including indoor-unit and repeat blocks.
Changed or removed choices remain identifiable without silently altering existing conditions.
Decimal comparisons are consistent in the logic preview and on the server; existing work orders and form definitions are unchanged.
Yes/no conditions
1.0.24
Valid yes/no choices for conditional requirements
The form editor now also offers a Yes/No selector for conditional requirements based on checkboxes and boolean installation data, so the selected value is saved correctly.
Consistent Yes/No choices for visibility and conditional requirements, including indoor-unit and repeat blocks.
A selected No is preserved when adjusting the condition.
Existing form definitions and historical work orders are unchanged.
Indoor-unit placeholders
1.0.23
Indoor-unit data in repeated form blocks
Use indoor-unit data in labels, prefilled values, help text and fixed information. Each unit receives its own values in forms and reports.
Placeholders for number, location, brand, model, serial number, condensate pump, port and customer reference.
Available tags inside the indoor-unit block, with resolved sample values in the preview.
Indoor-unit values are saved with the action for reproducible reporting.
Verified TransIP provisioning
1.0.22
Dedicated tenant storage and clearer validation
New installations support dedicated TransIP projects. Creation, export and deletion were tested with fictional data; existing tenant data is not migrated automatically.
Provider-neutral document storage and secured document uploads.
Clear audit upload validation without duplicate errors.
TRA validation updates immediately after successful changes.
TransIP pilot release
1.0.21
Tenant storage and secured document uploads
Pilot release for dedicated TransIP projects and verified document storage. Not yet generally deployed.
Audit document file-type validation and safe download headers.
Improved deletion checks and document mirror retries.
Complete tenant storage on Hetzner
1.0.20
All persistent files go to the tenant bucket
Alongside installation and work-order documents, manuals, audit sources, agreements, company documents and fault attachments are copied directly to the dedicated Hetzner bucket with verification.
New persistent uploads are immediately verified in Hetzner Object Storage by size and SHA-256 content.
An integrity command verifies existing private files and can write a protected migration manifest.
Temporary imports, exports, update files and local backups are kept separate from tenant documents.
Existing local paths remain available during the controlled transition so OCR, PDF generation and existing download links continue to work.
Isolated Hetzner storage
1.0.19
Documents go directly to each tenant bucket
Each tenant can use an isolated Hetzner Object Storage bucket. Document uploads are mirrored immediately and downloads can be served from verified object storage.
New documents are copied immediately to the active tenant bucket with verification.
Existing storage references can be repaired into the fixed customer and installation path with verification.
An unavailable legacy storage provider no longer causes a server error while locating an available document.
Dedicated Storj bucket per tenant
1.0.18
Preparing isolated file storage
The application supports an isolated Storj bucket for each tenant. Existing document routes remain local until file migration and reporting have been verified.
Storj S3 storage is available as a private disk with tenant-specific credentials and bucket.
Exit export and privacy information
1.0.17
More complete data export on cancellation
The exit export now includes linked files and more business data. The Storj entry shows the actual DPA status and globally distributed storage instead of an unverified EU claim.
Administrators can create a free ZIP export of machine-readable data and linked documents.
Privacy settings correct the old default Storj DPA wording without overwriting tenant-specific changes.
Material quantity with decimal comma
1.0.16
Easier decimal material quantities
The material field in custom forms now accepts a decimal comma directly, including on mobile browsers.
The quantity field uses a decimal keyboard without the browser restriction of a numeric input field.
Historical form data protected
1.0.15
Internal corrections and replaced indoor units
Internal material corrections remain private and historical form answers survive indoor-unit replacement.
Reversals of internal or report-hidden materials retain their visibility, even when the same material is also used publicly.
Optional material fields in a conditional section may remain empty; partially completed rows are rejected.
Material quantities using a decimal comma are processed correctly.
Answers for a subsequently removed indoor unit remain unchanged in the work order and report when editing the action.
Form logic refinements
1.0.14
Reliable conditional forms
Conditional sections, source values and internal materials remain correct when saving, editing and reporting.
Conditional sections retain their fields after saving and when reopening an action.
Original installation and indoor-unit values are retained for reproducible condition results.
Internal material lines stay out of reports, the customer portal and external APIs.
Materials in a conditional section are now booked as material lines.
The preview simulates two indoor units and repeat fields retain decimal commas.
Form logic and preview
1.0.13
Test custom actions before publishing
The form builder supports calculated fields, conditional requirements and validation, with an interactive preview and drafts that leave published forms unchanged.
Calculate a value from earlier number fields or constants using addition, subtraction, multiplication, division or percentages; use the result in conditions.
Interactively test visibility, required fields and outcomes before publishing a form.
Save edits as a draft; publishing creates a new version for future work orders.
Hide a calculated field in the form or a field in reports; mark staff-only information as Internal only.
Use a conditional section and compare numbers with a threshold or an earlier number field.
The server recalculates values, enforces requirements and stores the applied form version and condition outcome.
Repeat blocks and materials
1.0.12
Record materials in repeatable forms
Custom actions support manually repeatable rows with searchable materials and quantity. New materials are added to the catalog.
Drag fields into a manual repeat block and add or remove rows while completing the action.
Search existing materials or enter a new name and quantity; the work order also lists the material lines separately.
Conditions apply per repeated row: hidden fields are not required and never book materials.
Edits to signed material actions create a visible reversal with a reason.
A corrected action remains visible as history; further edits use the latest correction.
Conditional forms
1.0.10
Show only relevant fields in custom actions
Custom actions can show fields based on installation data or earlier answers. Each change creates a form version recorded with the work order.
Each eligible field in the form builder has a Conditions tab with searchable, read-only installation sources and earlier form answers.
An indoor-unit block evaluates conditions separately for each unit; previous answers within the block remain tied to that unit.
A hidden field is not required and is neither stored nor used for installation or refrigerant changes.
Form definitions are kept by version; the applied version and condition outcome are recorded with the work-order action.
Corrections to older actions retain their original form version, even after the form is renamed or deactivated. Saved conditional answers remain filled when editing.
The form builder's field palette stays accessible with its own scroll area.
Condition controls and messages are available in Dutch, English, German and French.
Reliable maintenance history
1.0.6
Maintenance planning follows the recorded action
Existing maintenance history is preserved, while new maintenance dates are created exclusively by an explicitly recorded maintenance or inspection action.
Maintenance work orders from before the update remain available as existing maintenance history.
After the update, the Maintenance work-order type no longer moves the maintenance schedule without a recorded maintenance or inspection action.
Text containing the word maintenance in a summary can no longer change the maintenance date unintentionally.
An explicit maintenance action counts immediately when recorded, even while the related work order still has Concept status.
The update records the transition date once; post-update checks automatically repair and verify this setting.
Action-driven installation history
1.0.5
Actions now determine status, maintenance and leak follow-up
The action actually performed is now the auditable source for commissioning, decommissioning, maintenance and mandatory leak follow-up, independently of the work-order type.
Custom forms can commission or decommission an installation, or register maintenance/inspection with the performed date when saved.
Maintenance overviews and the circuit register use this explicitly recorded maintenance action instead of the work-order type.
The form builder includes a dedicated Leak detected field; only Yes combined with an actual refrigerant fill creates a Leak check follow-up due between 24 hours and 30 days later.
The work-order type classifies and schedules the work order but no longer determines the technical installation effects of a custom action.
Administrators can disable functional leak detector reminders or configure an interval from 1 through 24 months; existing check history is preserved.
An administrator can mark a tool alert as Inspection scheduled. The alert then disappears for all relevant staff until the inspection state or date changes.
A circuit that is not leak-tight can be saved as an incomplete action after an explicit warning, but it does not activate the installation and is clearly reported on the work order.
Editing a commissioning action without a linked refrigerant transaction no longer asks for an irrelevant correction reason.
The new fields, messages and form options are available in Dutch, English, German and French.
Reliable photo uploads
1.0.4
Mobile photo uploads are faster and show clear progress
F-Register reduces large photos before transfer, preserves the entered action draft after connection loss and prevents duplicate actions when retrying.
Large JPEG, PNG, WebP and supported HEIC/HEIF photos are reduced to a maximum edge of 1920 pixels before upload; PDF, video, Word and RAW remain unchanged.
Photo optimization covers work-order actions and the other photo upload forms in F-Register, with server-side compression as a fallback.
Per-photo preparation progress is shown and the upload button cannot be clicked again while processing.
Upload status messages are cleared after success or failure and no longer accumulate in the work-order form.
Every new action receives a unique submission identifier, preventing duplicate actions when retrying after a broken connection.
Unsaved text, choices and form values for an action are temporarily preserved in the browser tab and restored after reloading.
Messages for connection loss, expired sessions, oversized requests and excessive file counts are clearer and available in Dutch, English, German and French.
Photos already optimized by the browser are not needlessly re-encoded by the server.
Reliable digital signing
1.0.2
Hiring agreements remain unchanged from offer to signature
The selected company signatory is now recorded before the document hash is calculated, allowing offered hiring agreements to be signed correctly even when the legacy contact-person setting is empty.
The application role controls access only; an active contractor profile and valid BRL 200 certificate determine who requires a hiring agreement.
Administrators, planners and technicians with a valid contractor profile can sign their own linked agreement.
The selected company signatory name is included in the same immutable document hash before the agreement is offered.
Signing also works when the legacy company contact-person setting is empty.
A complete regression test covers offering, signing, PDF storage, document hashing and the immutable audit version through the real routes.
Hiring agreements by employment type
1.0.1
Roles and contractor status are now independent
The application role now controls access only; the active personnel profile, employment type and BRL 200 certificate determine hiring-agreement eligibility.
Administrators, planners and technicians marked as contractor/hired are equally eligible for a hiring agreement.
Selection and storage require an active user, active personnel profile, contractor/hired employment type and a current BRL 200 personal certificate with an expiry date.
The audit view no longer limits contractor/hired dossiers to the Technician role.
The linked contractor can sign regardless of the F-Register role while the profile and certificate remain valid.
Dutch, English, German and French guidance now clarifies the distinction between access role and employment type.
Regression tests guard selection, audit visibility and signing across multiple roles.
First stable release
1.0.0
F-Register 1.0.0 is ready for daily use
The complete beta cycle concludes with a verified stable release for existing and new installations.
Combustion-appliance validation errors now use correct field labels in Dutch, English, German and French.
The combustion-appliance type field now uses an appliance-specific label instead of being described as an indoor-unit type.
The automated language guard now detects validation rules whose required state is determined dynamically.
Public Teamleader and WhatsApp integrations are rate-limited and perform no writes before successful authentication.
Fresh and existing tenants share the same verified database schema; post-update detects and repairs known drift.
A fresh tenant without active refrigerants receives clear guidance when creating an installation.
After upgrading, duplicate indoor-unit numbers may have been renumbered above the previous highest number.
Migration 000025 may mark some previously automatic unit-series links as manual; clear the checkbox to resume automatic matching.
Final 1.0.0 review candidate
0.2.168-laravel-beta
Rate-limited integrations and complete validation labels
This candidate closes the final integration, onboarding and validation findings before the stable 1.0.0 release.
Teamleader validates the shared secret before schema work; invalid requests no longer perform writes.
Default settings and Teamleader field mappings are seeded only during post-update.
Public Teamleader and WhatsApp routes are limited to sixty requests per minute.
A fresh tenant without active refrigerants receives clear guidance and a settings link when creating an installation.
An inactive or unavailable refrigerant produces an actionable validation message.
All 306 detected validation fields have readable labels in Dutch, English, German and French, with a source scan guarding future additions.
After upgrading, duplicate indoor-unit numbers may have been renumbered above the previous highest number.
Migration 000025 may mark some previously automatic unit-series links as manual; clear the checkbox to resume automatic matching.
Final quality pass
0.2.167-laravel-beta
Read routes no longer write hidden data
This candidate closes the four remaining low-severity review findings before the stable 1.0.0 release.
Validation errors use clear field names for maintenance contract, service interval and employment type in every bundled language.
Opening the cooling catalogue no longer backfills warranty data; synchronization remains part of post-update.
The unused and invalid audit_cylinder_explanations settings definition has been removed.
The account page no longer creates a calendar token or schema structure implicitly; users create the calendar link through an explicit button.
After upgrading, duplicate indoor-unit numbers may have been renumbered above the previous highest number.
Migration 000025 may mark some previously automatic unit-series links as manual; clear the checkbox to resume automatic matching.
Complete fresh-install chain
0.2.166-laravel-beta
Installations and downstream write flows verified
This candidate adds the missing installation type to the shared schema contract and now tests the complete core flow on an empty database.
Fresh installations now include installations.type, preventing cooling-install creation from failing on a missing column.
Post-update and verify-only enforce installations.type for existing, new and partially upgraded tenants.
A separate repair migration safely aligns previously deployed candidates with the same write contract.
The fresh-install test covers employee, customer, portal account, location, installation, work order, indoor unit, action, material and planning.
The MariaDB drift gate now deliberately removes installations.type as well and proves detection and complete repair.
All functional release-gate data is rolled back transactionally.
Final fresh-install candidate
0.2.165-laravel-beta
Reliable schema repair without stale-cache blind spots
This candidate closes both fresh-install blockers and ensures verify-only always reads external or recent schema drift from the current database catalogue.
New employees and customer portal accounts are created on fresh installations without a legacy-password error.
Material rows expose the same unit and notes fields on fresh and upgraded tenants.
Post-update makes the unused legacy password column nullable and restores missing write columns.
Verify-only clears all schema metadata first and therefore detects changes made outside the current process.
An isolated drift gate deliberately breaks all three contract points, expects verification to fail and then proves full repair.
The fresh-install smoke test exercises the real employee, customer and material controllers and rolls all test data back transactionally.
Fresh-install release candidate
0.2.164-laravel-beta
Write contract for new and existing tenants
This candidate resolves two blocking differences between fresh and existing installations and functionally verifies the affected user, customer and material flows.
New users and customer portal accounts can be created on a fresh installation because the unused legacy password column is nullable.
The actual authentication field password_hash and legacy-column nullability are now part of post-update and verify-only.
Work-order material rows include both unit and notes fields on fresh and upgraded tenants.
A repair migration aligns existing, fresh and partially upgraded databases to the same schema contract.
A new fresh-install smoke test creates an employee, a customer with portal account and a material row through the real routes.
The release gate now fails whenever any of these schema requirements is missing.
Final release candidate
0.2.163-laravel-beta
Complete 1.0.0 release gate
This candidate includes every medium- and low-severity review fix and closes the final measured hidden writes and N+1 queries on maintenance pages.
Every remaining medium- and low-severity finding from the independent review is addressed and tested.
Maintenance and customer-portal pages no longer run lifecycle mutations or schema scans during GET requests.
Maintenance history is loaded in one bulk query and appointment customers are eager-loaded, removing repeated queries.
Unit-series links, work-order types, permissions, translations, audit labels and transactional unit storage have been tightened.
Default settings and compliance rows are restored exclusively during post-update.
Status preservation when planning is cleared is covered for all six relevant work-order statuses.
Final release candidate
0.2.162-laravel-beta
Complete quality and performance pass for 1.0.0
This candidate addresses every medium- and low-severity review finding and also removes the remaining hidden writes and repeated maintenance queries from read routes.
Every remaining medium- and low-severity finding from the independent review is addressed and covered by focused regression tests.
An explicitly selected unit series is automatically preserved as a manual link instead of being silently replaced.
Work-order types, permissions, validation translations and dynamic audit labels have been tightened.
Indoor-unit and technical-type writes are atomic, preventing orphaned catalogue data after a failed save.
Default settings and compliance rows are restored only during post-update and no longer during regular page views.
Maintenance and customer-portal pages no longer mutate lifecycle state during GET requests.
The latest maintenance date is loaded for all installations in one aggregate query instead of separately for every installation.
Status preservation when planning is cleared remains guaranteed for active and completed work orders.
Final release candidate
0.2.161-laravel-beta
Complete quality pass for 1.0.0
This candidate addresses every remaining medium- and low-severity finding from the independent review and is intended for the final four-role and performance review before 1.0.0.
An explicitly selected unit series is automatically preserved as a manual link instead of being silently replaced.
Work-order types are validated against configured options and year closing is only shown to users with refrigerant management permission.
Validation messages and dynamic audit fields use readable translations instead of technical column names.
Indoor-unit and technical-type writes are atomic, preventing orphaned catalogue data after a failed save.
Default settings and compliance rows are now restored only during post-update, not while viewing an audit report.
Maintenance and customer-portal routes no longer run repeated schema scans, reducing their page load time.
Focused regression tests cover every remaining review finding, including status preservation when planning is cleared.
Release candidate
0.2.160-laravel-beta
Reliable unit series and checks
This candidate restores automatic unit-series relinking without overwriting manual choices and closes the remaining functional findings from the independent 0.2.159 review.
Unit types now record whether their series link was selected manually or automatically; manual links remain preserved.
Automatic links are recalculated when a more specific prefix is added, a prefix changes or a series becomes inactive.
The monthly leak-detector check opens on servers without the PHP intl extension and displays measurements using Dutch number formatting.
Clearing planning no longer resets a completed or active work order to Draft.
Migration, structure repair and verification check the new link-source field on fresh and upgraded installations.
Duplicate existing indoor-unit numbers are moved above the current highest number during the schema update; verify this physical numbering after updating.
Release candidate
0.2.159-laravel-beta
Data retention and safe work-order updates
This candidate closes the five high-severity findings from the independent 0.2.158 review and prevents save or synchronisation actions from silently changing existing customer and audit data.
Audit reports now explicitly exclude public installation tokens and internal notes.
Manually linked unit series are preserved during series saves, post-update repair and full synchronisation.
Missing optional installation fields and a missing locale selection no longer cause server errors.
Saving a work order as a technician can no longer unintentionally erase its planning, status, assignment or linked tools.
A new indoor unit using an existing number is rejected clearly; fresh and upgraded databases enforce the same unique index.
Focused regression tests cover all five findings and the complete test suite verifies their combined behaviour.
Release candidate
0.2.158-laravel-beta
Schema integrity and safe recovery paths
This candidate addresses the blocking findings from the complete independent review and makes fresh and upgraded installations structurally more predictable.
A shared schema contract is now used by migrations, post-update repair and verification for core fields, legal documents and work-order history.
Legacy tenants receive missing nullable timestamp columns without overwriting existing data or compatibility fields.
An automatic leak follow-up work order remains functional when an older work_orders table does not yet contain updated_at.
DOCX safety validation accepts valid Word files again and is tested against every bundled BRL document.
Unit series with linked technical types can be edited, but cannot be deleted while those links remain.
Automatic rollback no longer brings a tenant online when the database backup is missing or database restoration fails.
The table that controls standard action ordering is now also created, seeded and verified on fresh installations while existing customer-defined ordering is preserved.
Beta release
0.2.156-laravel-beta
Shared manuals per unit series
This release safely links one manual to a complete product series, improves customer details and corrects maintenance invitation addressing.
Unit series with multiple type prefixes can now be managed under Brands, units & warranty, for example Stylish with FTXA and CTXA.
Existing and new indoor and outdoor unit types are linked automatically using the longest matching prefix, without prefix searches during regular page views.
A series manual is stored once and shared by all linked types; a manual linked directly to one technical type remains a supported override.
The update verification creates and checks the new series tables and links for both existing and new tenants.
Customers can save address or other details without the incorrect warning that their unchanged email address already exists.
Maintenance invitations are always sent to the customer's email address; a different installation-location address is added as CC.
Beta release
0.2.155-laravel-beta
Faster audits and safer document workflows
This release incorporates the complete independent review of 0.2.154 and improves performance, document safety, structure verification and multilingual legal texts.
The audit export no longer builds unused installation lists and dropped from approximately 160 to 24 database queries in the local reference measurement.
The handbook editor no longer writes during regular page views and preserves the current source file and published PDF when conversion or storage fails.
Signed contractor agreements are locked against silent replacement; Word files are checked first and the default agreement now uses A4 with complete BRL details.
Migrations, post-update verification, backup and rollback now verify all new tables, columns, packages, PHP version and file ownership before a tenant returns online.
Validation messages and default legal documents were expanded in Dutch, English, German and French.
Release candidate
0.2.154-laravel-beta
More complete contractor agreements and handbook workflow
This candidate makes the contractor agreement directly usable with contract terms, existing technician certificates, a linked company contact person and layout-safe Word generation.
The contractor agreement uses a fixed twelve-month non-solicitation period and reuses BRL 200 certificate details from the technician profile.
Estimated deployment, hourly rate and invoicing frequency can be recorded per agreement and inserted into the Word document.
Placeholder replacement better preserves Word formatting, manual line breaks and signature fields.
The default contractor agreement is included with new installations and the update checks verify the new migration and placeholders.
The company contact person is explicitly linked to an active employee; the signature comes from My account and no longer depends on a free-text name.
Current beta
0.2.153-laravel-beta
Faster screens and a more complete audit dossier
This release incorporates the complete independent review, removes hidden database work and improves the reliability of audit, upload and tool workflows.
Work orders, planning, settings, roles and the customer portal now perform fewer duplicate queries and no schema repair during regular read requests.
Calibration and monthly-check alerts use the correct expiry date, role scope and 72-hour snooze, including the transition to overdue.
The audit dossier is generated as a readable landscape PDF with split wide tables, repeated headers and correct singular and plural labels.
Upload limits are repaired consistently and SVG detection also blocks MIME variants containing parameters.
Translations, validation messages, locale-aware number formatting and accessible status feedback were expanded and are covered by automated tests.
Beta release
0.2.152-laravel-beta
Safer indoor-unit photos and review remediation
This release strengthens document linking, authorisation, performance and accessibility following an independent review.
Type-plate photos receive stricter validation and SVG files are never displayed inline.
Indoor-unit documents remain available when a work order or indoor unit is removed.
Duplicate photo links are prevented and verified by the structure check.
Settings permissions, repeated database queries and accessible form feedback were improved.
Beta release
0.2.151-laravel-beta
Photos linked to the correct indoor unit
Photos added during installation management, OCR or a work-order action now use the same indoor-unit link.
A type-plate photo is stored directly as a document of the relevant indoor unit.
OCR can save a new indoor unit through AJAX before linking its photo.
The same gallery is shown in indoor-unit management and the work-order indoor-unit block.
An existing linked photo can satisfy a required photo field when that option is enabled.
Beta series
0.2.144-0.2.150
20 to 23 September 2026
Audit documents, contractor files and planning
This series expanded audit files and document generation while making planning more compact for daily use.
Year closing supports a first partial calendar year and the active refrigerant list.
DOCX preview, placeholders, tables, images and PDF generation were expanded.
Contractor files gained employment type, two-party digital signing and deletion protection.
Queue actions and mobile planning were made more compact.
Beta release
0.2.143-laravel-beta
Extended risk assessment with company controls
The task risk assessment was organised into three clear sections and can be extended with company-specific controls.
Activity and location, hazards and control measures are separate sections.
Company controls can be managed per active refrigerant.
Labels, guidance and groups are stored as an audit-proof snapshot.
Work orders, reports and NL, EN, DE and FR were updated.
Beta release
0.2.142-laravel-beta
BRL 100 V3 and annual refrigerant balance
Audit administration gained annual refrigerant closing, monthly leak-detector checks and the new BRL 100 V3 handbook.
Opening and closing stock, movements, kg difference and CO2 equivalent are calculated per F-gas.
A discrepancy requires analysis and corrective action before the year can be closed.
Leak-detector checks, calibration company and tool status were added.
Company certificates, placeholders and default BRL 100 V3 documents were expanded.
Beta series
0.2.138-0.2.141
19 September 2026
Warranty, catalogues and customer portal
Warranty terms became configurable per brand and customers gained access to more relevant installation details.
Warranty with and without a maintenance contract is managed per outdoor-unit brand.
An installation can override its warranty term without losing an existing commitment.
The customer portal shows warranty, maintenance status and available technical details.
Cooling and combustion catalogues and their settings were separated more clearly.
Beta series
0.2.135-0.2.137
16 to 17 September 2026
Last-minute risk assessment, cylinders and work-order permissions
Safe on-site work was recorded more clearly and daily work-order and cylinder workflows received stricter controls.
Risk-assessment answers and TRA information are stored legibly in work orders and reports.
Validation automatically opens the section containing a missing required field.
Cylinder weights and corrections are recorded more accurately.
Deleting and editing work orders follow clearer role and status rules.
Beta series
0.2.125-0.2.134
8 to 15 September 2026
Independent review and safer updates
A broad code, security and usability review produced a stronger technical foundation and more reliable updates.
CSS and JavaScript were bundled through Vite and made cacheable.
Policies, gates and the separation between staff and customer portal were tightened.
Updates verify migrations and structure and support recovery after a failed deployment.
Forms, navigation, errors and keyboard interaction became more accessible.
Historical beta series
0.2.104-0.2.124
1 to 7 September 2026
Custom actions and mobile work-order workflow
The form builder and work order were adapted for custom processes, repeated indoor-unit blocks and mobile use.
Drag-and-drop actions with checklists, placeholders, defaults and preview.
Repeated fields per indoor unit for serial number, location and condensate pump.
Refrigerant charging and recovery can be included in a custom form.
Work-order signing, reporting, photos and collapsible sections were expanded.
Historical beta series
0.2.52-0.2.103
4 to 29 August 2026
Planning, maintenance and installation management
During this series F-Register grew into a daily workspace for planning, maintenance, documents and installation history.
Day, week and month planning, queue, ad-hoc work orders and iCal feed.
Maintenance rounds with postcode areas, time slots and customer booking.
Import, export, documents, photos, installation manuals and customer portal.
Nameplates, QR labels, unit catalogues, multilingual support and mail templates.
Historical milestone
0.2.0-0.2.51
Early modular beta
Modular disciplines and central monitor
Cooling was separated from the core, allowing combustion appliances, vehicles and custom actions to be managed as modules.
Work orders can target a cooling installation, combustion appliance, vehicle or combination.
BRL 100 and BRL 6000-25/K25000 received dedicated audit documents and reports.
The monitor manages modules, tenant updates, storage limits and temporary support access.
API integrations and dynamic customer portals were introduced.
Initial beta
0.1.0-0.1.x beta
Initial development phase
The foundation of F-Register
The initial beta established the core for customers, locations, installations, refrigerants, work orders and audit reporting.
CRM structure for customers, installation addresses and installations.
Work orders, planning, technicians, materials and tools.
F-gas records, refrigerant cylinders and initial reports.
Company settings, roles, documents and the first customer portal.
Choose cookies by purpose
Necessary functions always work. Optional services load only after your choice. You can change it at any time. Privacy