Change 26.5 Release Notes

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

• Configure PCO and CCO fields with item type configuration setup – You can now define the required fields for PCOs and CCOs in the new Potential change order and Client change order Item type configurations. The settings let you specify whether fields are enabled and if they are required for workflows and for events such as CCO association or CCO execution. You can also specify whether to lock the field after workflow or other events. Read more

  The configurations for PCOs and CCOs have been added to both the organization settings (organization Settings > Configurations> Item Type Configurations > Potential change order or Client change order) and project settings (project Settings > Configuration settings >Item Type Configurations > Potential change order or Client change order).

  

  For PCOs, you can enable each field. When enabled, you can then require them for workflow, lock them after workflow, and require them for CCO association.

  For CCOs, you can enable each field. When enabled, you can then require them for workflow, lock them after workflow, and require them for CCO execution.

  The check box Allow projects to edit configuration settings is included at the organization level. When it is selected, you can add or edit the configuration settings at the project level. When it is not selected, all fields in the project settings are disabled.

  When editing at the project level is enabled, you can edit values to make fields more restrictive than they are at the organization level. For example, if a field is not required for workflow at the organization level, you can configure it to be required for a workflow at the project level. When a field is required at the organization level, the field is required at the project level.

  Require for workflow

  When the Require for workflow toggle is set to Yes, the fields show with an asterisk on Details pages and must be completed before the PCO or CCO can go through the workflow.

  Lock after Workflow

  When the Lock after Workflow field is set to Yes, you can no longer update the item at that level after workflow. The locked field and its value show on the PCO or CCO Details page, but the field is disabled.

  Require for CCO association

  When the Require for CCO association toggle in the Potential change order settings is set to Yes, the fields shown with an asterisk on the Details page must be completed before you can associate the PCO to a CCO.

  Require for CCO execution

  When the Require for CCO association toggle on the Client change order settings is set to Yes, the fields shown with an asterisk on the Details page must be completed before you can execute the CCO.

• DocuSign eSignature at the issue level – DocuSign eSignature functions are now available at the issue level. When a project is integrated with DocuSign, the eSign section where you assign the recipients and project contacts now shows on the issue Details page. Read more

  

  You can use the eSign section to view or add recipients to be used as default eSign signees like the eSign sections in PCOs and CCOs.

  The Send for signature icon has been added to the issue Supporting document page. You can select a document, and then click the icon to select recipients and send a document to DocuSign.

  

• Issue log edit issue status – You can now use a bulk edit function to edit the issue status on the issue log. Change issue status no longer has its own button. Read more

  To edit the issue status now, select one or more issues, click the Bulk Edit icon, and then select the Issue status column. You can then select the value

  .