Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
How add the Field Relationship for ‘Request Type’ pick list field based on the value of ‘TPhase’ short text field of a Type.
For example,
Initially Request Type has Build, Deploy and Build & Deploy values
1) If TPhase value is "Ready to Build" then the 'Request type' should have Build option only
2) If TPhase Value is not "Ready to Build" then the 'Request type' should have both Deploy and Build & Deploy not Build.
I could not see TPhase in Source Field list of the field relationship column. We use Integrity Server 2009.
Is there any other possible way to restrict Request Type values.
Thanks in advance.
Solved! Go to Solution.
Hello Venkata Sarath Babu,
As Volker Eckardt mentioned, this functionality doesn't exist in the 2009 release series, but comes into play in the Integrity 10 releases, in the node called Constraints on the Type definitions. I've confirmed by setting up an example of this in Integrity Lifecycle Manager release 10.7, although I believe the functionality exists earlier than that release (maybe 10.4?):
I hope that helps.
Regards,
Kael
Hello Venkata,
there are probably not that many installations out using still Integrity 2009. We ship release 11 already, which is almost 10 releases after yours.
I think in 2009 we did not provide this kind of feature. You need to upgrade at least to one of the current Integrity 10 releases.
Regards
Hello Venkata Sarath Babu,
As Volker Eckardt mentioned, this functionality doesn't exist in the 2009 release series, but comes into play in the Integrity 10 releases, in the node called Constraints on the Type definitions. I've confirmed by setting up an example of this in Integrity Lifecycle Manager release 10.7, although I believe the functionality exists earlier than that release (maybe 10.4?):
I hope that helps.
Regards,
Kael
Hello Venkata Sarath Babu,
If you still need assistance with this, can you please let us know the challenge(s) you are still facing?
It looks like Kael's solution is correct, would you please take the next step and mark this answer as "Correct Answer"?
This way other users reading the thread will know there is a solution, and which answer is correct. In addition, it makes the solution easier to find.
Thank you,
Adam