How do I activate trigger for example checking in a document or bumping a revision? Please help I've tried everything I know! :D
How do I activate trigger for example checking in a document or bumping a revision? Please help I've tried everything I know! :D
Geoffrey,
Are you an administrator to the vault?
The bulk of your settings are determined in the Vault admin tool.
You need to start there and look that over to first setup your revision schemes
and permissions along with what are called life cycles.
Scott, I have to answer yes to all the above. I am the administrator of the vault and all the settings you've mentioned, and more, has been set-up in the vault admin which has been running for more than a year now. Each Users e-mail addresses have been entered into the vault admin tool yet the notifications still don't work.
Jesse I think that's were the problem lies. The message is being sent to the server but then the server doesn't know what to do with it. Could you help to set it up properly?
From the knowledge base:
The warning message in the log file relates to the trigger functionality in Workgroup API to send notifications. Triggers use MSMQ (Microsoft® Message queuing) to send notifications, so MSMQ needs to be setup in order for this to work. If the vault is not using notifications, ignore the log entries. This message is a warning more than it is an error. To try to resolve it, on the server machine, go to control panel, add / remove programs, add / remove Windows® components, select Message Queuing, click on Details, make sure common and triggers are selected as components, click ok, click next, let Windows reconfigure the MSMQ software. If this does not help, try to uninstall MSMQ and reinstall from add / remove Windows components. Also review the Windows Event application and system logs for errors related to MSMQ. Refer to KB solution S-031602 for more details on configuring MSMQ with workgroup. |
No problem. Brian mentioned below on how to install MSMQ. How MSMQ works is it receives a message, and the message can either invoke an action, or it can sit there and wait to be read by someone or something.
I did a lot of leg work and a guy named Declan (on the forums) helped me when I was still wet behind the ears. He helped be create a message reader service in VB.NET. I would have to dig it out and dust it off. We only used it for a short time until we moved to EPDM.
Another thing to think about in the mean time is your SMTP server. Where is it and what are it's settings? Just a small detail, but we'll need it.
I did a presentation at SolidWorks World 2008 on Triggers and put the presentation along with sample VB.NET 2008 source code on my website that you can download.
Dear, someone could run the triggers downloaded from wlmservices.net page? I have everything set except MSMQ rule condition do not know what to specify in each case in theVaultAdmin considering all options selected.
Any help?
Thanks.
I hope I understand your question. You can either use the VaultAdmin or a rule condition to limit what messages are sent to the mailbox from Workgroup PDM.In the VaultAdmin Triggers tab, Workgroup PDM will only send messages for the actions that are checked.
The other way is to use the MSMQ rule condition. For example to not send a message for a "Bump Revision" action, you could setup a rule where "Message Label Does Not Contain" "Bumprevision". MSMQ rule conditions does give you more flexiblity in filtering messages to be sent.
If you do not setup filters and your code does not handle the different actions, your mailbox will fill up and you will have to manually delete the messages.
Here is a link to more info on MSMQ rule conditions.
http://developergeeks.com/article/77/how-to-use-microsoft-message-queue-triggers-msmq-triggers
Geoffrey,
Are you an administrator to the vault?
The bulk of your settings are determined in the Vault admin tool.
You need to start there and look that over to first setup your revision schemes
and permissions along with what are called life cycles.