AnsweredAssumed Answered

Is a prefix required on ALL file names in order to go through a workflow ?

Question asked by Russell Simms on May 14, 2014
Latest reply on May 15, 2014 by Russell Simms

Like • Show 0 Likes0
Comment • 4

I come from CREO and Windchill world at my previous job. My new place of business uses CREO, but uses Solidworks PDM for it's data management.

Our administrator is under the belief that all files must have a predefined prefix in order to go through a workflow. So if you could imagine a file that would normally be named "side_panel.prt" would have to be named for example "wpengstd-side_panel.prt" in order to go to a workflow...this applies to ALL files...excel, creo, pdf, anything has to have a workflow prefix.

Everything I see and read seems contrary to that. I am working with her to create a workflow without a condition of Category (which she uses to define the workflow), but with condition of Filepath only so all files in a particular folder go through the same workflow.

Am I missing something or is she correct ? I'm being persistent but hopeful to her in hopes we can set this up correctly for a new engineering folder.

No one else has this question

Outcomes

Tonia Lauer May 14, 2014 3:32 PM

You are correct, there is no need for a prefix. The conditions for a file getting into any given workflow are completely user (well Administrator) defined, as well as each transition within that workflow.

To specify any file in a certain folder would be the condition type: filepath, argument: %\[foldername]\%

These pages spell out the options:

for workflows:

http://help.solidworks.com/2014/English/EnterprisePDM/Admin/IDD_WORKFLOW_PROP.htm?id=88b84b3873b0421fac5ff496edfd17cd#Pg0

for transitions:

http://help.solidworks.com/2014/English/EnterprisePDM/Admin/r_condition_operators_for_workflow_transitions.htm?id=2fc676783797422cbe24e852d8ac1b92#Pg0

Actions

Russell Simms @ Tonia Lauer on May 14, 2014 3:43 PM

Thanks so much. I can't hardly believe any PDM system would have such a restriction on sending anything through a workflow.

It's enough having an incompatibility between CREO and Solidworks PDM, let alone on top of it a restriction on file naming.

I'll keep everyone informed of my final outcome in case something comes out that I can share.

Thanks again !!

Actions

Tim Read @ Russell Simms on May 15, 2014 2:50 AM

Hi Russell,

It is all a matter of choice... Using a prefix in all filenames to assign the Workflow has its benefits as it simplifies the rules. It reduces the complexity of ensuring files enter the correct workflow when basing it on combinations of rules - Caterory, Folder Path (folder, filename and filetype), Variables...

You should not be seeking to change what works without understanding why it has been set up in the way it has.

PS: I see that you have posted this exact same Question in a separate thread... please keep it tidy

Actions

Russell Simms @ Tonia Lauer on May 15, 2014 3:02 PM

So our admin setup a test workflow for the folder I'm testing in. She did not create a category for it and the only condition she has is the filepath.

Yet, when I try and check in a file from the path below it gives the no workflow conditions met error.

This is a snapshot she sent of the workflow properties and my folder location...so I'm wondering why it won't go in....thoughts ?

Actions

4 Replies

Tonia Lauer May 14, 2014 3:32 PM
Mark Correct
Correct Answer
You are correct, there is no need for a prefix. The conditions for a file getting into any given workflow are completely user (well Administrator) defined, as well as each transition within that workflow.

To specify any file in a certain folder would be the condition type: filepath, argument: %\[foldername]\%

These pages spell out the options:

for workflows:

http://help.solidworks.com/2014/English/EnterprisePDM/Admin/IDD_WORKFLOW_PROP.htm?id=88b84b3873b0421fac5ff496edfd17cd#Pg0

for transitions:

http://help.solidworks.com/2014/English/EnterprisePDM/Admin/r_condition_operators_for_workflow_transitions.htm?id=2fc676783797422cbe24e852d8ac1b92#Pg0
Like • Show 0 Likes0
Actions
- Russell Simms @ Tonia Lauer on May 14, 2014 3:43 PM
  Mark Correct
  Correct Answer
  Thanks so much. I can't hardly believe any PDM system would have such a restriction on sending anything through a workflow.
  
  It's enough having an incompatibility between CREO and Solidworks PDM, let alone on top of it a restriction on file naming.
  
  I'll keep everyone informed of my final outcome in case something comes out that I can share.
  
  Thanks again !!
  Like • Show 0 Likes0
  Actions
  - Tim Read @ Russell Simms on May 15, 2014 2:50 AM
    Mark Correct
    Correct Answer
    Hi Russell,
    
    It is all a matter of choice... Using a prefix in all filenames to assign the Workflow has its benefits as it simplifies the rules. It reduces the complexity of ensuring files enter the correct workflow when basing it on combinations of rules - Caterory, Folder Path (folder, filename and filetype), Variables...
    
    You should not be seeking to change what works without understanding why it has been set up in the way it has.
    .
    PS: I see that you have posted this exact same Question in a separate thread... please keep it tidy
    Like • Show 0 Likes0
    Actions
- Russell Simms @ Tonia Lauer on May 15, 2014 3:02 PM
  Mark Correct
  Correct Answer
  So our admin setup a test workflow for the folder I'm testing in. She did not create a category for it and the only condition she has is the filepath.
  
  Yet, when I try and check in a file from the path below it gives the no workflow conditions met error.
  
  This is a snapshot she sent of the workflow properties and my folder location...so I'm wondering why it won't go in....thoughts ?
  Like • Show 0 Likes0
  Actions

Is a prefix required on ALL file names in order to go through a workflow ?

Outcomes

Related Content

Recommended Content