What is the proper method to record an A-replaces-B relationship in Agile?
I can see how I can implement the replacement of part A with part B in all instances where A is currently used. Is there a standard method, though, to indicate to a user who is looking at obsolete part A for whatever reason that it has been replaced by part B?
I don’t know that there is a specific “Standard” for this, but one option is adding the replacement details to the part record (perhaps the Page Two “Notes” field) as the lifecycle phase is being changed to Obsolete.
You may also want to create a Relationship between the two parts to provide quick access to the replacement part from the Obsolete Part record.
If you are planning to maintain relationship in peer to peer manner and also want to bring it as part of process.
create field in affected items so that you can assign item whose relationship to be established and write px.
PX will establish relationship with the part through relationship tab.
And workflow process will take with the rule that you programmatically define in assigning parts
In this case, one care you need to take is relationship is always one way like example A to B.
Hi All. Thanks for you ideas and comments. We ended up creating a Page Two multi-list field titled “Replaced By” tied to Item Number and implemented a rule requiring it be populated in order to Obsolete the part. Created an “N/A” item for those cases where there is no replacing item. Not bulletproof, but it seems to meet our needs.