2026 News Archive - Revision history

BurnsD: /* July 29, 2026 */

2026-09-23T20:44:37Z

July 29, 2026

BurnsD: /* June 22, 2026 */

2026-08-28T14:33:51Z

June 22, 2026

BurnsD: /* May 21, 2026 */

2026-07-29T17:28:12Z

May 21, 2026

BurnsD: /* March 10, 2026 */

2026-06-22T14:27:38Z

March 10, 2026

BurnsD: /* February 20, 2026 */

2026-03-19T14:00:52Z

February 20, 2026

BurnsD: Created page with "=February 20, 2026= Orange Barrel season is just around the corner, and we’re busy laying the groundwork for a smoother spring! In this edition, you’ll find system update..."

2026-02-20T20:21:18Z

Created page with "=February 20, 2026= Orange Barrel season is just around the corner, and we’re busy laying the groundwork for a smoother spring! In this edition, you’ll find system update..."

New page

=February 20, 2026=

Orange Barrel season is just around the corner, and we’re busy laying the groundwork for a smoother spring! In this edition, you’ll find system updates targeted at report updates, payment-estimate performance, and calculation accuracy - all designed to make your APCM days a little easier. Grab a coffee, take five, and let’s dive in.

'''Announcements'''

Please be advised that AASHTOWare Project will be offline starting at 3:00 PM on Friday, February 27th, and will remain unavailable through Sunday until early Monday morning. This downtime is necessary to complete the upgrade to version 5.04.

'''Reports'''

*'''''Item History To Date Report''''' – Various fields and labels were updated on the report as requested from field offices.

'''System Configurations'''

*'''''Payment Estimate Performance''''' – A hotfix was applied to address some computations used in the creation of estimates. With this fix in place, estimates should generate more quickly.

*'''''Rounding Fix''''' – The estimate calculation process was updated to handle values beyond two decimal places that in some cases caused rounding issues.

'''Did you know?...'''

Proposal, Contract, and Project Line Numbers - Ever wonder why AASHTOWare shows two different types of line numbers? Here’s the breakdown:

*'''''Contract Line Number (a.k.a. Proposal Line Number)'''''
Contract Line Number and Proposal Line Number refer to the same thing. These are generated at the contract level and include all items across all projects and categories in that contract. They appear on screens like the Contract Items – General tab, where items are rolled up without duplicates at the contract level. These numbers are sequential (e.g., 5, 10, 15…) and represent the entire contract’s item list.

*'''''Project Line Number'''''
Generated at the project level, ensuring no duplicates within that project.
Found on tabs like Contract Project Items, where items are grouped by project and category.
'''Important:''' Project line numbers may match contract line numbers when there’s only one project, but they are not the same thing. On large contracts with multiple projects, the contract line number will often '''NOT match''' the project line number.

'''''Key Difference:'''''
Both are created the same way and function similarly, but they organize items at different levels—contract vs. project. This helps keep things clear when contracts include multiple projects (e.g., road work vs. bridge work) or categories. If you see “Line Number” on the General tab, assume it’s the contract line number. If you’re working within a project view, it’s likely the project line number. Always confirm which level you’re on before referencing line numbers!

To view previous news articles, visit the [[Construction Technology News Archive]].

@@ Line 1: / Line 1: @@
 ====July 29, 2026====
@@ Line 23: / Line 52: @@
 To view previous news articles, visit the [[Construction Technology News Archive]].
 ====June 22, 2026====

@@ Line 1: / Line 1: @@
 ====June 22, 2026====
@@ Line 15: / Line 42: @@
 For audit compliance, any Daily Work Reports (DWRs) that cannot be completed by their original author must be placed in a rejected status within the contract. If a DWR is still in draft, another user will first need to submit it so it moves to pending approval. Once in this status, a user with an Office Tech role can select Reject. The system recognizes “Rejected” as a valid final status, and these DWRs will not appear as exceptions on pay estimates.
 ====May 21, 2026====

@@ Line 1: / Line 1: @@
 ====May 21, 2026====
@@ Line 28: / Line 48: @@
 To view previous news articles, visit the [[Construction Technology News Archive]].
 =March 10, 2026=

@@ Line 1: / Line 1: @@
 =March 10, 2026=
@@ Line 36: / Line 67: @@
 A quick double‑check during your DWR entry can prevent delays and keep your estimate processing smoothly.
 =February 20, 2026=

← Older revision		Revision as of 14:00, 19 March 2026
Line 1:		Line 1:
		+	=March 10, 2026=
		+
		+	Spring is (almost) here, and so are a few quirks and fixes following our recent AASHTOWare Project upgrade. As everyone settles into version 5.04, we want to keep you informed about what’s changed, what’s been resolved, and a few troubleshooting tips that may save you some time. Grab a coffee and take a quick look at the latest updates.
		+
		+	'''Announcements'''
		+
		+	We’re continuing to monitor system behavior post‑upgrade, and several issues have already been identified and addressed. Below is a summary of what we know so far.
		+
		+
		+	'''System Configurations'''
		+
		+	*'''''Email Notifications''''' – Following the upgrade, system‑generated email notifications were temporarily offline. The triggers have been restored, and all email notifications should now be functioning properly.
		+
		+	*'''''Pay Estimate Type Selection Required''''' – When creating a pay estimate, you may notice that the Type field appears preselected. However, users must still select or reselect the Pay Estimate Type before they can proceed. This ensures the system properly registers the selection.
		+
		+	*'''''Unable to Assign Default Tests''''' – If you encounter issues assigning a default test to a sample record, it may be due to cached files interfering with updated system behavior. To clear your cache: Press Ctrl + Shift + Del, then select Clear Now. After clearing, reload the application and try again.
		+
		+	*'''''Subcontract Item Worksheet''''' – When building a subcontract and selecting a lump sum item in the item worksheet, the unit field may not automatically populate. The cell will display as blank and highlighted. To resolve: Click into the unit cell and manually select LSUM from the table.
		+
		+
		+	'''Did you know?...'''
		+
		+	When posting materials on a Daily Work Report, it’s essential to correctly record how materials were used so the system can validate them for payment.
		+
		+	Here’s what to keep in mind:
		+	*'''''If a material is used (installed quantity is greater than zero) -''''' You must enter and record a material source.
		+	No source = the system will withhold payment for that material and may cause issues in your payment estimate.
		+
		+	*'''''If a material is not used -''''' Make sure to zero out the installed quantity.
		+	A non‑zero quantity tells the system the material was used—even if it wasn’t—which triggers a missing‑source error and blocks payment. If a user enters 0.00 in the material quantity field, the system will ignore that material as part of the payment estimate generation process.
		+
		+	In short:
		+	*Non‑zero installed quantity requires a source.
		+	*Zero installed quantity tells the system the material wasn’t used.
		+
		+
		+	A quick double‑check during your DWR entry can prevent delays and keep your estimate processing smoothly.
		+
		+
		+
		+
		+
	=February 20, 2026=		=February 20, 2026=