Simplifying PDM Categories

Using Categories effectively is a principal and critical step in PDM vault definition.

PDM Categories serve as the primary means of routing files added to a PDM vault to the appropriate workflow. These Categories often depend on intricate Filepath parameters, making it challenging to configure their behavior as required. To address this issue, we can employ Variable values to define Categories.

Utilizing a variable as a component of the parameters that define a Category offers significant advantages in vault management. Furthermore, it can substantially minimize the potential for confusion and errors when implementing new categories. Let's explore an example.

Installation Drawing category definition.

This category, known as "Installation Drawing," is defined by only two parameters. The first parameter is the variable named "File Classification," which is set to "INSTL" for Installation Drawings. The second parameter is a Filepath definition, which, in this case, encompasses any SolidWorks© file type. These two parameters work together in an AND logic function, meaning that both conditions must be met for a file to be categorized as an Installation Drawing.

Utilizing the Variable and Filepath parameters in this manner ensures that regardless of where the file is created in the vault, it will be classified as an Installation Drawing. This approach, which combines a variable with a Filepath parameter, is more intuitive and sustainable compared to using multiple Filepath parameters like "%.sld% AND Design\Mechanical\Installation Drawings AND NOT Design\General Drawings," especially over time. One advantage is that directory names or locations within the vault may change or move without adversely affecting the Category definition.

If you predominantly define your Categories using a Variable and Filepath, along with the Category name aligning with an ASME Y14.24 document type, managing them becomes effortless.

To route a file to a specific workflow, you can simply make the Category a condition for that workflow, as illustrated below. It's worth noting that all the conditions mentioned here are encapsulated within an OR container, ensuring that any of these file types will be directed to the Engineering workflow.

Workflow conditions using Variable based Categories.