














Save on the products you need with the AEC Collection and discover the toolkit that expands your skill set.
Save on the products you need with the PDM Collection and discover the toolkit that expands your skill set.
PDM Collection includes:
Save on the products you need with the ME Collection and discover the toolkit that expands your skill set.
In this lesson, we’ll look at how to release a revised item, and how to leverage important tools when preparing and reviewing the Change request.
In this video, we explore the process for releasing an item a second time, and explore 3D comparisons, BOM comparisons, release types, and linking Investigation requests to the Change request.
Please note items must have been revised and are currently in Development, ready to be released again.
Transcript
00:05
In this video, we explore the process for releasing an item a second time and explore 3D comparisons, BOM comparisons, release types,
00:13
and Linking Investigation Requests to the Change Request.
00:17
So let's take a look.
00:20
Once you've made all desired changes to your items, you'll need to make sure that you save all of your changes.
00:26
This could be checking in the CAD and drawings if applicable, or simply updating item attribute information in the web application.
00:35
Then, we release it again using a new Change Request. Let's send our drone assembly to a new Change Request.
00:43
We'll do this from the web application, but remember we could have done it from the cart in the CAD plugin as well.
00:50
To send our assembly to a new Change Request, locate the item and load it into the center view, click the action menu,
00:57
hover your mouse over "Send to", then click Change Request.
01:02
A new Change Request is created and the assembly with all of its children is brought into the Change Request.
01:09
But remember only those items in development will be released during this Change Request.
01:20
Because we have made some design changes, let's explore the 3D comparison tool.
01:37
For items that contain mechanical CAD,
01:40
Upchain automatically generates a 3D comparison between the item that is currently being released and its previous released version.
01:52
All areas that have been added are shown in green and all areas that have been removed are shown in red.
01:60
This can help you and the approvers visually see what design changes have been made to confirm that they are correct.
02:18
Another tool that we can take advantage of this time around is the BOM comparison tool found at the bottom of the window.
02:28
This is also automatically generated by Upchain and compares the bill of materials of the item that is currently being released,
02:36
and its previous released version.
02:38
The left side here shows the BOM structure from the previous release,
02:43
and the right side shows the BOM of the item being released on this Change Request.
02:48
Certain attribute changes are highlighted in yellow and you can hover your mouse over the tooltip to see what attributes have changed.
02:58
Items that are added to the bill of materials are highlighted in green and any items that have been removed are highlighted in red.
03:07
Again, this is useful to see how the BOM may have changed from one item version to the next,
03:14
and helps to ensure that items have not been accidentally added or removed from the previous item version.
03:23
This is especially useful with a very large bill of materials.
03:35
Now, since these changes were a result of an Investigation Request,
03:40
we should link the Investigation Request to this Change Request to ensure the full story behind the change can be fully traced.
03:55
Again, you should do this to allow anyone,
03:57
who reviews this Change Request to understand where the original request for this change came from in the first place.
04:07
Lastly, let's ensure the items are ready to be released. All released types have already been set to Major, this is the default.
04:21
If any of these needs to be changed, you would simply put the Change Request into edit mode and you could change them to Minor.
04:29
You could do this based on what the revision note says.
04:33
All revision notes have already been filled out as well from the previous videos,
04:38
because the person who made the changes did so at the time of the change.
04:43
Again, if this information was not filled out or you needed to make a change,
04:48
you could do so here by ensuring, again, the Change Request was in edit mode, and then fixing up or typing in the revision note.
04:58
Again, it is best to ensure this information is filled out at the time of the change, so that it's fresh in that person's mind.
05:10
And that way, you don't have to worry about filling this out here at the time of release.
05:29
Lastly, let's edit the header information. We'll set the priority to match the priority of the Investigation Request.
05:42
This just helps other users understand the priority.
05:46
We'll input a description. Again, this helps users see at a quick glance what this Change Request is for.
05:57
We'll choose a workflow and we said previously our items are ready for production.
06:05
So we'll choose the production item maturity level here.
06:11
Save your changes...
06:17
And now you can start the Change Request workflow.
06:21
In our example, the project manager must approve the Change Request before it completes and releases the items.
06:41
There, the items are currently pending and it is waiting for the project manager to now release the items.
06:52
You can see that the task to release the items has been created and assigned to the project manager.
07:07
So now signed in as the project manager.
07:13
They can review the information we just did ourselves in the 3D comparison tool, the BOM comparison tool,
07:22
review the revision note information, review the Investigation Request where this change came from,
07:29
and then they can go ahead and release the items if they're satisfied with all of that information.
07:48
Now, the items are released.
08:08
You can see the Major and Minor revision levels have been incremented and the version on the item is now set back to 0.
08:18
The item maturity has also been updated to production as we chose on the Change Request.
08:25
One thing you may have learned in the mCAD courses is how to add drawing codes to your drawings.
08:31
These codes are converted when the item is released to their actual values on the DWG and PDF translations.
08:39
So your Upchain administrator needs to have these two translations enabled to use these codes.
08:45
These codes include basic item attributes as well as the revision history of the item.
08:56
In this assembly drawing example, you can see that we have configured a revision table to capture the previous three revisions,
09:03
and we have populated the title block with information, including item name and number, current revision level,
09:10
and people who have checked and approved the drawing.
09:14
Search "drawing codes" in our help center to learn more.
Video transcript
00:05
In this video, we explore the process for releasing an item a second time and explore 3D comparisons, BOM comparisons, release types,
00:13
and Linking Investigation Requests to the Change Request.
00:17
So let's take a look.
00:20
Once you've made all desired changes to your items, you'll need to make sure that you save all of your changes.
00:26
This could be checking in the CAD and drawings if applicable, or simply updating item attribute information in the web application.
00:35
Then, we release it again using a new Change Request. Let's send our drone assembly to a new Change Request.
00:43
We'll do this from the web application, but remember we could have done it from the cart in the CAD plugin as well.
00:50
To send our assembly to a new Change Request, locate the item and load it into the center view, click the action menu,
00:57
hover your mouse over "Send to", then click Change Request.
01:02
A new Change Request is created and the assembly with all of its children is brought into the Change Request.
01:09
But remember only those items in development will be released during this Change Request.
01:20
Because we have made some design changes, let's explore the 3D comparison tool.
01:37
For items that contain mechanical CAD,
01:40
Upchain automatically generates a 3D comparison between the item that is currently being released and its previous released version.
01:52
All areas that have been added are shown in green and all areas that have been removed are shown in red.
01:60
This can help you and the approvers visually see what design changes have been made to confirm that they are correct.
02:18
Another tool that we can take advantage of this time around is the BOM comparison tool found at the bottom of the window.
02:28
This is also automatically generated by Upchain and compares the bill of materials of the item that is currently being released,
02:36
and its previous released version.
02:38
The left side here shows the BOM structure from the previous release,
02:43
and the right side shows the BOM of the item being released on this Change Request.
02:48
Certain attribute changes are highlighted in yellow and you can hover your mouse over the tooltip to see what attributes have changed.
02:58
Items that are added to the bill of materials are highlighted in green and any items that have been removed are highlighted in red.
03:07
Again, this is useful to see how the BOM may have changed from one item version to the next,
03:14
and helps to ensure that items have not been accidentally added or removed from the previous item version.
03:23
This is especially useful with a very large bill of materials.
03:35
Now, since these changes were a result of an Investigation Request,
03:40
we should link the Investigation Request to this Change Request to ensure the full story behind the change can be fully traced.
03:55
Again, you should do this to allow anyone,
03:57
who reviews this Change Request to understand where the original request for this change came from in the first place.
04:07
Lastly, let's ensure the items are ready to be released. All released types have already been set to Major, this is the default.
04:21
If any of these needs to be changed, you would simply put the Change Request into edit mode and you could change them to Minor.
04:29
You could do this based on what the revision note says.
04:33
All revision notes have already been filled out as well from the previous videos,
04:38
because the person who made the changes did so at the time of the change.
04:43
Again, if this information was not filled out or you needed to make a change,
04:48
you could do so here by ensuring, again, the Change Request was in edit mode, and then fixing up or typing in the revision note.
04:58
Again, it is best to ensure this information is filled out at the time of the change, so that it's fresh in that person's mind.
05:10
And that way, you don't have to worry about filling this out here at the time of release.
05:29
Lastly, let's edit the header information. We'll set the priority to match the priority of the Investigation Request.
05:42
This just helps other users understand the priority.
05:46
We'll input a description. Again, this helps users see at a quick glance what this Change Request is for.
05:57
We'll choose a workflow and we said previously our items are ready for production.
06:05
So we'll choose the production item maturity level here.
06:11
Save your changes...
06:17
And now you can start the Change Request workflow.
06:21
In our example, the project manager must approve the Change Request before it completes and releases the items.
06:41
There, the items are currently pending and it is waiting for the project manager to now release the items.
06:52
You can see that the task to release the items has been created and assigned to the project manager.
07:07
So now signed in as the project manager.
07:13
They can review the information we just did ourselves in the 3D comparison tool, the BOM comparison tool,
07:22
review the revision note information, review the Investigation Request where this change came from,
07:29
and then they can go ahead and release the items if they're satisfied with all of that information.
07:48
Now, the items are released.
08:08
You can see the Major and Minor revision levels have been incremented and the version on the item is now set back to 0.
08:18
The item maturity has also been updated to production as we chose on the Change Request.
08:25
One thing you may have learned in the mCAD courses is how to add drawing codes to your drawings.
08:31
These codes are converted when the item is released to their actual values on the DWG and PDF translations.
08:39
So your Upchain administrator needs to have these two translations enabled to use these codes.
08:45
These codes include basic item attributes as well as the revision history of the item.
08:56
In this assembly drawing example, you can see that we have configured a revision table to capture the previous three revisions,
09:03
and we have populated the title block with information, including item name and number, current revision level,
09:10
and people who have checked and approved the drawing.
09:14
Search "drawing codes" in our help center to learn more.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.