Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
Version: Windchill 12.0
Use Case: While editing the Change Request adding new affected objects under select affected object, suppose there is 2 affected objects already present for the change request we are adding 1 new object.
Description:
The problem faced is while fetching these affected object through code using ChangeHelper2.service.getChangeables(changeRequest) inside editFormProcessor only able to get the 2 affected object, I need to check all the affected objects(existing + newly added) as well as just newly added object.
Solved! Go to Solution.
You can't expect ChangeHelper2.service.getChangeables(changeRequest) to get the newly added objects because at this point in the process they are not added yet. They are not linked to the CR at this point and therefore there is no link in the dB that getChangables() method can query.
BTW, can you tell us exactly what you are intending to check when checking the newly added objects?
You can't expect ChangeHelper2.service.getChangeables(changeRequest) to get the newly added objects because at this point in the process they are not added yet. They are not linked to the CR at this point and therefore there is no link in the dB that getChangables() method can query.
BTW, can you tell us exactly what you are intending to check when checking the newly added objects?
What does that mean?
WTDocuments don't have affected data.
While editing change Request we can select WTDocument as affected object, need to get this newly added WTDocument.
Yes, that was clear, but what you have not answered is why you need to get the WTDocument?
Once you get it then what? All of this info should be in the "Use Case" portion of your original post.
need to compare one attribute value of newly added WTDocument and that of change request
And once compared do you do anything with the comparison. Or regardless of the comparison you continue.
@NG_10595539 , can't you just spell out EXACTLY what you are doing without the need to keep asking questions.
For example, if WTDoc attribute Compare 1 is X and CR attribute Compare 2 is Y do what?
or
if WTDoc attribute Compare_1 is X and CR attribute Compare_2 is NOT Y do what?
This is what the Use Case if for. To clearly state, well, the use case.
1. WTDoc attribute X = CR attribute Y -> set fromResult as failure
2. WTDoc attribute X != CR attribute Y ->set fromResult as success