Change 26.7 Release Notes

This is a preview of the upcoming release. General release is available starting 07-SEP-2026.

  • New issue approval workflow – New issue approval setup has been added to the Change organization settings, so organizations can establish workflow steps that are inherited by projects. Change also supports approval groups for steps in the Change project settings. ClosedRead more

    At the organization level (Settings > Change > Workflow assignments > New issue approval setup) you can add steps and assign them to a role.

    You can also indicate whether projects must select specific users based on assigned roles. If the Project must select specific users based on assigned roles setting is selected, you must select a user in the role at the project level. If the setting is not selected, any user in the role with access to the project in which the issue is created is eligible to approve the issue.

    At the project level (Settings > Change > Workflow assignments > New issue approval setup), you can add new steps and assign them to users, roles, or groups. If you created steps at the organization level and selected the Projects must select specific users based on assigned roles check box, the step shows with a warning, and you must select a user before you can save the workflow.

    When the workflow is configured, the Submit for approval button now shows on the New issue log, and the Submit for approval button replaces the Add button on the Add new issue dialog box.

    Click Submit for approval to start the workflow. Issues are still created and logged even if approval cannot start because of errors in the workflow steps. The issue is added to the New issue log with the ID Pending and an Issue approval status as Not started. To start the workflow, you can select the issue, and then click Submit for approval to see a list of steps that require attention.

    If there are no steps that require attention, the Submit for approval button is disabled, and the issue is added with the issue ID Pending and the Issue approval status as In approval.

  • Associate InEight Contract back charges to a pricing item – You can now associate pricing cost items to back charges in Contract from the issue Pricing page. ClosedRead more

    The Associate to Back Charge option has been added to the Pricing page Associate to Vendor change order icon.

    If the pricing item is not already associated with a back charge, you can associate it with an existing back charge from Contract or create a new one. After the back charge is associated with the pricing item, the issue shows in the Association section of the Back charge Details page in Contract, and the back charge shows on the pricing item’s Edit slide-out panel in Change. You can click the link in the Edit slide-out panel to go directly to the Back charge Details page.

  • Decimal precision for unit cost – You can now configure decimal precision for unit costs on the Configurations > Decimal precision page. The decimal precision applies to pricing (Detail/Plug items), Pending Import History details, and generated Microsoft Word documents.

  • Pricing page new columns – The Committed total cost, Pending VCO commitment, Other adjusted cost (-), Other adjusted cost (+), Other Adjusted Costs, and Projected Uncommitted budget columns have been added to the Issue, PCO, and CCO Pricing pages. These columns give better visibility into the cost item across the project. ClosedRead more

    The committed total cost is the sum of contract line items associated to the WBS cost item across the project.

    The Pending VCO commitment column shows the total of unexecuted VCO line items associated to the WBS across the project

    The Other Adjusted Cost columns show negative, positive, and net adjusted costs for everywhere the WBS cost item is used in the project except the current issue, PCO, or CCO.

    The Projected Uncommitted Budget column is calculated as follows:

    (Current budget + Other adjusted costs + Adjusted cost) - (Committed total cost+ Pending VCO Commitment)

    The new columns are available in the Column selection builder.

  • Lock issue after CCO execution – The Lock after CCO execution option has been added to the issue, PCO, and CCO Item type configuration (Settings > Change > Configurations > Item type configuration). This setting prevents a field from being edited at the issue level after the associated CCO has been executed. The default for the fields is Locked.