When it comes to 3DEXPERIENCE, there is possibly no better benefit than an integrated, ‘out-of-the-box’ data management system with very little to no setup.
With that said, the system can be modified quite heavily, and depending on your application, this may make sharing and collaborating on ‘your terms’ even better.
It would be atypical to release an assembly, without releasing the parts and subassemblies underneath that top level product as well. There are 2 ways to handle this.
Make no changes to the Platform settings and rely on internal procedures
In this option, users choose Maturity inside SOLIDWORKS and ‘Include Structural Objects’ to transition all related objects. A multiselect would work here, too. The problem here is that the users must be on the same page and make sure to release the underneath parts. Otherwise, you end up with a released top-level and “In Work” parts. You probably don’t want that!
In the graphic below, the user can select “Include Structural Objects” to bring the child components with the release of the assembly.
Your Platform Administrator can work in the Collaborative Spaces Configuration Center widget > Maturity > Engineering Definition. Next, the user will select the transition from “In Work” to “Released”. Select the Plus icon and Object Type here is Physical Product for SOLIDWORKS objects. You will choose the “Reject if any of the Governed Children is not on Target State”.
Now, any of the child files would first need released in order to release the assembly.
In many cases, the second option will reduce any chance of releasing the parent object without the child and it would be a best practice to enable the transition rule.
Learn more about the 3DEXPERIENCE platform in our upcoming webinar "What's new in 2022x FD02 for 3DEXPERIENCE SOLIDWORKS".