Source "Configuration Path" vs "Flat Path" obsolescence in Integrity Lifecycle Manager

[Julia_Mantel]

• Support of Configuration Path Syntax
• Integrity Source Flat Path Syntax should be removed/ deprecated
• Source Configuration Path vs Flat Path obsolescence
• Enhance support to address the areas of the product that still use legacy syntax (flat path) instead of the Configuration Path syntax:
  • Change Package Details view
  • Member & Revision Information view
  • Projects view
•  Receiving the below error while trying to create a normal sandbox using flat path via GUI / CLI:
  • Failed to create sandbox: MKS125443: The subproject <SubProject>/project.pj does not exist (anymore)

See also article CS84840.

[awalsh]

There is a duplicate idea here:

https://community.ptc.com/t5/Integrity-Ideas/Source-quot-Configuration-Path-quot-vs-quot-Flat-Path-q...

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.