Community Tip - You can change your system assigned username to something more personal in your community settings. X
Hi all,
as a System Architect I am looking for a way to define the attribute fields that trigger a suspect OSLC link between Polarion and PTC Modeler. When referencing requirements from Polarion, there are some fields in Polarion that are not relevant in regards to impact analysis. When they change in Polarion, this should not lead to a suspect element in PTC Modeler. I would be happy to only use the relevant fields for suspecting.
Is there a way to configure those fields?
Thanks,
David