Legacy Workflows To New Workflows Transition Guide

Subject lines include the object type and identifiers (for example, PO # or Contract #).

• Subject lines are less granular and not configurable.

• Subject lines do not include detailed identifiers.

Emails include full workflow history and previous responses.

• Emails include limited context.

• Full workflow history is available only inside Procore.

Supported one-click 'Respond on behalf of' action.

• This action is not supported.

• A workaround requires adding yourself as an assignee or changing the assignee.

Comments and attachments are clearly visible in tabular sections.

• History appears in a side panel.

• Users must expand and scroll to view comments and attachments.

• Filters (comments-only or attachments) are not available.

Tables display the current assignee and days awaiting action.

• These columns are not currently available in tables.

• Information must be viewed via hover or side panels.

Not available.

• In-flight legacy workflows cannot continue after upgrade.

• Items automatically restart in New Workflows.

• Legacy history is preserved, but execution resets.

Best practices

• Complete active workflows before upgrading.

• Create and assign workflows to projects, then configure and mark as default at the project level to ensure new workflows can be used.

Note: If this step is not performed, any in-flight legacy workflows will be permanently stuck post-upgrade.

Not available.

Granular permissions are limited by tool-level admin rights.

• Tool Admins automatically have workflow admin permissions.

• Tool Admins cannot be restricted from changing assignees or due dates.