Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
I am using Windchill 11.1 CPS 25
We noted that there is no default setting/option to collect related SUMA parts from an OEM part on any of the OOTB collector (available on Promotion Request/Change Objects).
The idea was that the OEM part & SUMA part would go through said Promotion & ECN together.
There is an ability to add those SUMA parts Ad-Hoc (+ button or through the search field below the tables); this assumes the person creating the Promotion/Change is aware of the associated SUMA objects.
How are you/your organization circumventing this problem ?
(Also, if I have overlooked any configuration do let me know)
Since most all users in my system are prevented from interacting with SUMA parts (Search, BOMS, etc), this is not our requirement. The SUMA administrator managed these parts manually. If you did want to add these to change objects for release, you have to make sure users are trained on what these are and how to handle them. This might also clutter change object tables since this adds more objects. It might be easier to add these object via a workflow task since rules seem pretty simple to add them if the exist, following the OEM part.