Document Change Orders shipped today. Until now, every change order in Duro bumped the revision — even when you were just updating a datasheet, swapping a supplier, or fixing a typo in the description. That meant a new revision for changes that had nothing to do with the design. DCOs fix that.
When you create a change order now, you pick the type: Engineering or Document. Engineering COs work exactly as before — they bump the revision when approved. Document COs skip the bump entirely. Both lock the component during edit so you can't accidentally release something mid-change.
This unlocks workflows teams have been routing around for months. Update compliance docs without triggering a revision cascade. Swap an approved manufacturer without re-releasing downstream assemblies. Track the change history without the revision noise.
Document Change Orders. New change order type that updates components without bumping revision. Choose Engineering or Document when you create a CO — the system handles the rest. DCOs still lock component status during edit and route through the same approval flow.
Change order type selector. Segmented control on the CO creation screen. Existing change orders show a read-only type badge so you know what you picked.
Assembly import now handles creates and updates in one pass. Previously you had to import once to create components, then import again to update them. Now the importer resolves parent-child ordering and handles both in a single run.
