Change 26.10 Release Notes

This is a preview of the upcoming release. General release is available starting 09-NOV-2026.

*Updated 21-OCT-2026

• *Lock issue fields after PCO association – You can now specify whether issue fields are locked after PCO association. A new toggle, Lock after PCO association, has been added to Configurations > Item type configuration setup > Issue. When the toggle is set to Yes, the Lock after CCO association and Lock after CCO execution toggles are automatically set to Yes. Read more

  Previously, lower-level records become locked after associated higher-level workflows were approved. That is, issue fields were locked when an associated PCO or CCO workflow was approved, and PCOs were locked when an associated CCO workflow was approved. Now, issue fields and PCO fields are locked based on the settings in the Item type configuration setup for the issue or PCO, respectively.

• Item type configuration define supporting documents and document placeholders – You can now configure required supporting documents for specific events, such as PCO or CCO association or workflows, in issues, PCOs, and CCOs. The required documents show as placeholders in their respective Supporting documents pages. Read more

  A new section, Define supporting documents, has been added to the Item type configuration (Settings > Configurations > Item type configuration setup) for issues, PCOs, and CCOs at both the organization and project levels. At the project level, you can make a requirement more restrictive than the organization level, but you cannot make it less restrictive. That is, if a document type is required at the organization level, the requirement cannot be changed to not required at the project level.

  

  For each item, you can click Manage Documents to open the Manage documents dialog box where you can select the document types and subtypes you want to require in your project or organization. The document types and subtypes you select show in the Define supporting documents requirements grid and as placeholders on the Supporting documents pages.

  

  In the Define supporting documents requirements grid, you can specify by document type and subtype whether the document is required.

  • For issues, you can specify whether the document type is required and if approval is required for budget moves, PCO association, and CCO association.

  • For PCOs, you can specify whether the document type is required and if approval is required for workflow and CCO association.

  • For CCOs, you can specify whether the document type is required and if approval is required for workflow and execution. Document type placeholders required for workflow cannot be removed from the Supporting documents page.

  For CCOs, an executed change order document is no longer required for execution, but the default in the organization settings is set to Require for Execution. You can change the value as needed. If you do not want an executed change order as a placeholder, you can deselect it in the Manage document dialog box

  When you create an issue, PCO, or CCO, the Supporting documents page automatically shows blank lines for each of the selected document types and subtypes as placeholders. A yellow warning triangle shows as a visual reminder that the document is a default document type.

  

  You can then add and then edit the document or click the link in the hover text to add document information and the file or link.

• Create new line items in InEight Contract from the Pricing page – When you associate a cost item to a vendor change order from the issue pricing page, you now have the option to create line items in InEight Contract. Read more

  The Create Line Items check box has been added to the Associate to Vendor Change order dialog box that opens when you select Associate to VCO/Back charge > Associate to Vendor Change order.

  

  When the box is selected, the cost item creates a line item in the contract.

  When there are multiple cost items related to the same contract, associating any item associates all items to the vendor change order, and line items are created in Contract for each cost item.

• Collection Table Grouping and Subtotals – You can now use grouping and subtotals, where applicable, in every collection table included in an uploaded Change template in Change writer. Previously, grouping and subtotaling were available for the cost item pricing collection table only. Read more

  The Advanced options section of the Template Details page in the organization and project settings now includes predefined grouping fields for each detected collection table. Predefined value fields included in the table can be selected for subtotaling.

  Also, any field that has value, such as a unit cost, can be subtotaled based on a group or without a group.

  When a template has multiple collection tables, each table shows in the Advanced options section.

  

• Edit value types in cost items in value type grid – You can now edit the ROM, Estimate, Proposal, and Agreed values in the value type grid in the Edit cost item slide-out panel by copying the Adjusted cost field value. You can also now edit values manually in the grid. Read more

  The Copy value icon has been added to the Adjusted cost field on the Details tab of the Edit cost item slide-out panel. After you have entered an adjusted cost, you can click the Copy value icon to select the value type. The adjusted cost value populates the corresponding cell in the values type grid.

  

  The option to add a value type from a drop-down list associated with the Adjusted cost field has been removed.

  If you make subsequent changes to the Adjusted cost field, you must update the grid if you want the values to match. If you manually edit values in the grid, they are not automatically reflected in the Adjusted cost field.

  On the Pricing page, the Value type column shows the highest value type with a nonzero value.

  Any cost item pricing still goes to the pricing summary in the Estimate column in the Pricing summary tab.