Commit review
Commit review is the last screen before a release. It lists everything the commit will touch, why each row is there, and what it will become.
Open it from the Commit review tab in the Staging Area. The tab carries a count of items pending release.
What the summary tells you
Three figures sit above the table:
| Figure | Meaning |
|---|---|
| Items | How many items this commit releases. |
| New part numbers | How many will be given a fresh CPN, including items released for the first time. |
| Revision only | How many keep their part number. |
If New part numbers is higher than you expected, something in the tree is taking a version and pulling the assemblies above it along with it. The Result column shows which ones.
Edited versus Forced
Every row explains why it is in the plan.
| Label | Why it is here |
|---|---|
| Edited | You changed this item directly. |
| Forced | You did not touch it, but something inside it changed. |
Forced rows are marked with an amber line and cannot be removed from the commit.
This is not a restriction to work around. An assembly whose contents changed has to be issued again, or the record no longer matches what the assembly contains.
Choosing how each row releases
The Release as toggle sets the mode per row:
- Revision keeps the part number and steps
REVAtoREVB. - Version creates a new part number, applies the size of change you choose, and restarts at
REVA.
When you pick Version, a Bump selector appears with three options: major, minor or fix.
The Result column previews the outcome for every row, showing the current identity and then what it becomes. New part numbers are called out. They read as new number rather than a specific value, because the number is only reserved at the moment of release.
When a row switches to Version by itself
Sometimes a row moves to Version without you choosing it, with the tooltip "a descendant took a new part number".
A new part number below suggests a new version above
If something inside an assembly takes a new part number, the assembly's bill of materials now calls for a different part, so Partix suggests a version for it too, and for everything above it up to the product.
You can switch any of those rows back to Revision. Do that when the item is still interchangeable for the people using it. If a whole chain has jumped to Version when you did not expect it, look down the plan for the one row that started it.
Shared items
If a shared assembly is in the plan, a notice names the other products that use it.
Your commit does not change those products. They stay on the revision they were committed against. Their teams will want to know a newer revision exists, though, and this is where you find out who to tell.
Committing
Select Commit. Everything in the plan is released together. There is no partial commit.
If the tree changed while you were reviewing
If someone edited the BOM while this screen was open, the commit is refused and asks you to reload. It will not release a plan that no longer matches the tree.
What happens next is covered in After a commit.