Example of a Dispatch for EPDM

Hello

I had posted this question 10 years ago, but I think that asking it again today is relevant because there will surely be more EPDM users and therefore more interesting feedback.

What do you do with the ' Dispatch ' tool integrated into PDM?

Automatic uses in your workflows?
Manual uses?

And possibly thank you for sharing the Dispatches that seem most relevant to you.

Hello

I use several of them myself. Here's an overview:

  • renommage_fichier → during a state transition, the file is renamed to a variable value if the condition on its name is met
    image

  • export_excel → during a state transition, the Excel file is copied out of the vault
    image

  • avertissement_code_manquant: During a transition corresponding to an automatic rollback because a variable is missing, a popup is displayed on the user's workstation
    image

  • valid_admin: Displays an OK/Cancel popup if an administrator (whose login starts with " adm..."  tries to validate a plan. This avoids a bad handling when I juggle between my two accounts.
    image

  • verif_pdf_ouvert: the most twisted :slight_smile: ! → During a transition, PDM automatically generates the pdf of the plan in the background, outside the vault. If a PDF file with the same name already exists and is already open by a user, this generation will fail. So I tried to set up a dispatch that tries, even before the build (so at the beginning of the transition) to delete the already existing PDF in the target directory, and display a popup if it doesn't work, then cancel the transition.
    image

  • remplissage_matiere → each time a 3D file is archived (i.e. not plan and not excel), the script fills in the Material variable according to the content of the Material Type variable that the user has previously filled in on the data card. This works better than doing the same thing in a TaskAction.
    image

Available to discuss it more!

Hello

For my part, use during transition for a script that takes care of applying the new reference in the file properties (we changed ERP at a time so recodive each time we take a hint) and offers the entry of the old codification which will be displayed in a field mapped in the plan.
I have another script that allows you to rename files when passing a transition following a user's input and allows an exit door that cancels the transition if necessary.
Finally, I use a last script that checks the version of a Word frame and prevents archiving if the correct one is used.

1 Like

Hello Cyril, I'm curious to see how you check the compliance of the word frame, it might interest me for excel files.

I added a variable called version which is in the properties of the file.
Since most of our users don't know how to access them in Word (well hidden in Office 365), I just have to query this variable.
If different from the one expected, it cancels the PDM command and reopens the file (displays a message on the way to change the frame)
image

1 Like

Thanks for sharing.

Well seen the script for blocking the transition if the pdf is blocked in writing (we also have this kind of problem from time to time). Does it work well?

I don't understand why you created the " remplissage_matiere " script though. For us, the SW material property of the config is linked to the data card and it seems to work without any problem for us (EPDM is not linked to an ERP or anything else for us so it's not necessarily ultra critical for us)

The script for the pdf works :slight_smile: . In fact, the popup does not necessarily appear in the foreground and the user does not understand why his file is rolled back. But it doesn't hurt anyway.

For the subject script, this is a particularity of our operation:

  • if the user chooses the value "Solidworks Material" in " Material Type", then the " Material " variable takes the value defined in SW (via a 3rd variable mapped by customproperty) 
  • if he chooses another value (see BOM, see Note) it is this value that will appear in the " Material " variable.
    In short, a gas plant that only works with this Dispatch :stuck_out_tongue:

And you didn't want to " just " map this file property to a PDM variable via a customerproperty?