Hi Pablo, you have a couple of options here (hoping I have understood the problem correctly)
1. You can set up notifications in the Convert Task for success or failure. The engineers don't need to know about the failure of the Convert Task, but you could potentially setup notifications for the success of the task to your engineers. Personally I wouldn't really use this as you don't have many options of configuring the notifications
2. If the PDF files created by the Convert Task are saved inside the PDM vault and going into a Workflow you could set up notifications for:
- Files being checked into a state
- Or setup a automatic transition from the initial state of the PDF workflow to another state, and notify your Engineers)
Hope this helps,
Ideally, it sounds like you need a tool that will automatically collect all SOLIDWORKS files after PDF conversion and transition them to the next state. Take a look at this PDM addin that is a transition task that will transition files based on a schedule, and the transitions are completely configurable. It's a paid addin, but that may be a good option to save your team from having to manually move those files.
Thanks for your comments.
I dont know if I made myself clear with the original comment, but suppose the following scenario:
.SDLDRW files have three possible states.
[Editing] ---(send to approval)----> Creating PDF -----> PDF created
When the user changes state to "send to approval" the first transition schedules the convert task and goes to "Creating PDF".
Then, when the PDF has been created, I want an automatic transition to take the document to "PDF created"
How can I achieve that?
My apologies, I did understand your need.
There isn't an "easy" way to make a "trigger" without a task or an Add-in. Dispatch "can" help but is very limited.
You need a way to trigger the transition of the slddrw to go to the next state "after" the PDF is created or updated.
Hope this helps,
Believe in The Q!
I might be misunderstanding your needs, but if you're just looking for a way to automatically transition the generated PDF file to the "PDF created" state, you can use this solution that Tim Webb provided me a few years ago: https://forum.solidworks.com/thread/64978
If I didn't understand your request correctly and you're actually wanting the SLDDRW file to transition to "PDF created" after the PDF file is automatically generated, I apologize. Can I ask why the SLDDRW file can't just go straight to the "PDF created" state? It seems that the engineer would be able to review the PDF once it shows up in their vault view without any need for notifications.
With Matt's reminder about my own post it helped me see you may not need that intermediate state called "Creating PDF". Let the SLDDRW transition through to PDF Created, add the destination state variable to both the PDF and SLDDRW cards, and follow the instructions I provided in the post he mentioned I helped him with. Thanks Matt Camacho-Cook
I also agree with Matt's question:
...Can I ask why the SLDDRW file can't just go straight to the "PDF created" state?
I do believe this is a much easier way to handle that process than all the extra detail.
Otherwise, Greg Thomson's idea is a good way to handle it. And Greg, it's not ugly, just pretty deep. I've used that script to do amazing things with PDM files once they are in the vault by adding the necessary IEdmVaultX, IEdmFileX, and IEdmEnumeratorVariableX calls.
Definitely agree with the amazing things you can do with the interfaces and customization. I just chose to abandoned the Convert scripting environment for the custom add-in (Visual Studio) environment. I feel I'm far more productive and can develop more 'industrial strength' customizations. It would really be a great thing if PDM truly integrated VBA like SW and other Office type products.
You could modify the Convert VBA script via Output File Details ==> Advanced Scripting Options and add the few lines of code required to change the state of your files once your PDFs are generated.
Ugly, but possible.