Skip to content

OpenConstructionERP v17.8.3

Choose a tag to compare

@github-actions github-actions released this 23 Sep 02:27
· 3518 commits to main since this release

A general contractor can bill a job month by month and get paid for it. A payment application is raised for its own period rather than for everything done to date, and it is checked before it goes out: the screen says what the submission check makes of it, so a line billed past its contract value, or a period that overlaps the one before it, is refused while it can still be corrected. Approved subcontractor pay applications roll up into the contractor's own claim instead of being retyped, with a preview of what would be pulled in and a person confirming it. The breakdown of a claim can be edited while it is a draft, and the screen says why it cannot once the claim has gone out for approval. A payment application issued earlier keeps the figures it was issued with, and is recalculated only when it is regenerated, never behind the reader. Editing a line now re-reads everything that line moved, so the claim's own gross, retainage and net, the printed form and the row in the register all agree with the line on screen instead of lagging a step behind it.

Retention comes back. It accrued on every claim and there was no way to release it: the one action that existed wrote a note on the contract, counted the money as paid the moment it was written, asked for no documents and had no claim to bill it on, so the certificate never showed it and the owner never paid it. A release is a record now. The contract drawer shows what is held, what has gone back and what is free to release, and the release is proposed against what is actually held, sized by the rules of the project's own country, which in the United States returns all of it at substantial completion less one and a half times the open punch items. It is approved only once the documents that event calls for are registered on the contract, and it is billed on a claim, where it lowers the retainage line and is paid with that claim. The moments a release can hang off are named one way throughout, on the screens as well as in the contract and the regional packs, so the template editor no longer stores a name the rest of the product has stopped using. In five languages the money held back was called one thing in one place and something else in another, and it now has a single name in each.

A contract now says which retention rule is actually in force on it, which schedule that ladder came from, and, where no schedule carries tiers, that the contract's own flat percentage is standing in rather than being a ladder somebody chose. The words of the policy, the statute it cites and the notes, can be corrected whenever. The money itself, the tiers, the mode, the rate on stored material, the cap and the date it takes effect, is refused once any claim on the contract has left draft, because that money has already been withheld from the contractor and already been stated on a certificate somebody has read. The refusal names the claim that locked it and says the remedy in words, a change order or the next contract rather than a rewrite backwards, and the contract reports which fields are locked and which claim locked them, so an editor can grey them rather than take the keystrokes and refuse the save. A rejected claim locks nothing. A ladder nobody could apply is refused where it is typed rather than by every payment application afterwards, so a bad first tier no longer turns into a contract that cannot produce a certificate at all with the complaint arriving a long way from the person who caused it. This one is the contract answering for itself rather than a screen: the editor is not built yet, so today it is reached through the API and not from the contract drawer.

Four dead ends on the contract screens are gone. The first line of a schedule of values had no unit, because the empty state drew its own add form instead of the one every later line goes through, so a contract whose first line had no unit could not be signed and nothing on screen said why. A line could be added and then never touched again, so a draft contract's rows now carry an Edit and a Delete, the update sends only the fields that actually changed so a colleague's correction to a description is not undone, and Delete asks first and says what it costs the contract total. On a signed contract the row carries no controls and one line of text says the schedule is what the job is billed on and a variation is the instrument. A contract typed in by hand could not be billed at all, because a claim only ever offered to populate itself from site progress, so it now offers to add a line by hand from the schedule of values lines not already billed, and a contract with no schedule of values at all gets its own sentence saying so, because having nothing to bill is a different problem from having nothing to populate from. The claim page reads the schedule now, which also puts the description of a line in the Line column where the head of an identifier used to be. And two dialogs offered euros whatever the job was in: the claim dialog follows the contract that is selected, and follows it again when the contract is changed without closing the dialog, and the new contract dialog takes the project's currency. All of the new wording is translated into every language the product offers.

The payment application form itself was wrong in five ways and is right now. The continuation sheet rounded every row on its own and drifted a cent or two away from the claim it was printing. A roll-up parent was listed beside its own children, so part of the job was counted twice. The total row took its figures from the claim record instead of from the columns above it, so the sheet could add up to something other than what it showed. A cost-plus claim billed from its costs printed zeros, because the columns were read from a schedule of values that a cost-plus contract does not have, and it now prints a cost of work row instead. A cost-plus contract whose claims do not all have the same shape, some billed from costs and some from typed lines, still does not add up, and that is not fixed here. And retainage was printed as one figure, where the form asks for work and stored material separately, so the sheet now prints both. Retainage in the columns ties to the retainage line to the cent, and the previous certificate line is the previous certificate rather than a figure rebuilt from it.

The payment deadlines that the United States sets by statute are carried, federal and eight more states, each with the statute it comes from. The statutory clock also stopped measuring against the wrong figure: interest and the paid-in-full check now run on the sum that had to be paid rather than the sum applied for, so a payer who answered in time with a lower sum and paid it is no longer told the difference is overdue. Where the statute lets silence concede the claim, the finding says that is what happened, and every finding names the figure it used and the document that stated it.

Every generated document can be given its own look from Settings, and the meeting minutes and the daily diary have their own rather than borrowing the generic report layout. The project report prints on the company letterhead like the rest. A long company name no longer runs off the page: the header and the footer measure the name in the face that will draw it, shrink it where it does not fit and shorten it only as a last resort, and a name in Chinese, Korean, Thai or an Indic script is drawn in a face that can draw it instead of coming out as a row of empty boxes.

One uploaded logo could cost a document minutes and gigabytes. A small file that declares itself a hundred thousand units across was drawn at that size, and a six page estimate took half a minute and most of the memory on the machine to print. The logo is measured and bounded before it is drawn, a six page estimate is back to about a second, and a logo within the ordinary range comes out exactly as it did before. Three of the handlers that lay a document out now draw it beside the request loop rather than inside it, so a large print through those does not make every other page wait on it.

A spreadsheet exported with the company letterhead can be imported back. The letterhead pushed the header row down the sheet and the importers still read the first row, so a budget exported and sent straight back came in as nothing at all. The importers look for the header row now and say which row they found. A cell whose text begins with an equals sign is written as text rather than as a formula, so a note and a phone number survive the trip, and a letterhead that fails partway through puts the workbook back as it was instead of leaving the table moved.

A general contractor gets a focused menu in simple mode, showing the billing cycle rather than everything. On a browser that two people share, one person's workspace no longer greets the next person to sign in, and a new user is no longer judged by the previous one's setup. The Dashboard row lights when the dashboard is open, and a page opened without a tab in the address lights the row for the tab it actually shows.

A snag can carry what the rework costs, so the cost of poor quality adds up from the items rather than being estimated, and a link opens the handover tab directly. The figure now says what it left out: how many of the open items are priced, whether the project has a currency at all, and what was recorded in other currencies, each in its own. An item raised without a currency takes the project's own instead of United States dollars.

Opening a project for the first time no longer answers with a server error when two requests arrive together. The lines of a subcontractor pay application say how many there are rather than quietly returning the first page, so the approval screen shows the whole payment it asks a person to confirm. The delete prompt for a document names the six new places a contract can refer to one. And two lists that a screen joins with a comma now join the way the reader's language joins them, which matters in Arabic, Chinese and Japanese.

Running a database migration inside a longer-lived process used to switch off every logger the process already had, which silenced a third of the application's own logging for the rest of its life. It only ever showed up as tests that expected a log line and got none, across dozens of unrelated modules, but the same mechanism applies to any process that migrates and then keeps running.

Full Changelog: v17.8.2...v17.8.3