How can we get an error when lower lifecycle components are being released on higher lifecycle BOM?
Hi Agile experts,
Apologies if this has been answered somewhere, I couldn’t find it.
Our doc control folks are wondering if there is a way to make Agile check on a change order affected items for the lifecycle of assembly to make sure the children parts are the correct lifecycle?
They manually check now to make sure the components are at the same or higher lifecycle of the BOM. For instance if the assembly is at Pilot lifecycle all the components should be at Pilot or Production lifecycle.
I couldn’t find a smartrule around this.
I couldn’t figure out how to do a criteria for the workflow since you need to check the affected items to see if they are on a BOM, see if the BOM is on the change, see what lifecycle the BOM is and see if the components are same or higher lifecycle than the BOM. And somewhere you have to define what the acceptable parameters are for the BOM to Component lifecycles and you have to do all that through many levels.
I’m guessing this can only be done with a pretty fancy PX/SDK. If someone could confirm, I’d appreciate that.
you`ll need some sort of process extension for this validation, it`s a simple one, when you add an item to the BOM, an event called “update table”, it should trigger the validation process extension (groovy code) that will prevent that an item in the wrong lifecycle phase to added to a BOM.
Smart rule only validates if the BOM item is released or not, so it`s just part of the solution.
To do a good job you need to check not only when an item to a BOM–can configure Agile to check for usage of lifecycles like Obsolete and Inactive, but need to also think about when changing the assembly’s lifecycle or when changing a child’s lifecycle. Then, like you said, have to take into account if items in the BOM are an affected item. It can get complicated depending on how far you want to take it.