Intralink trigger

Hello. I am trying to install a trigger in Intralink, and I am new to
the whole progess. Can I write any DLL to utilize events, or must I
use the "toolkit"?

Right now, I am trying to understand enough to where I can get
started. Currently, I have a generic DLL with a simple function that
just executes some test code. I have no idea where to put the DLL,
although I thought I read somewhere the proi/bin was the directory of
choice.

Is there a global place for this to go so that eventually every user
will have this capability by default, or must it go strictly on the
client side?

When the function is defined, it is a void myfunc(void), and you just
put 'myfunc' in when you add the trigger? If the DLL isn't found, or
fails, do these errors get logged anywhere? Is there any resources on
the web for how to do this? I have been surfing for a few days now,
and managed to come up with a few tidbits, but nothing that explains
more than a few bits and pieces.

Thanks,

-Kevin

 

In actuality, we just need a mechanism to do a check before we check
in a drawing/model, such that we might validate that the parts used
are actually in a database (not intralink database). Is a trigger the
best/only mechanism? Can we use ModelCheck, and if so, can ModelCheck
be run as part as the pre-checkin process automatically?

 

In actuality, we just need a mechanism to do a check before we check
in a drawing/model, such that we might validate that the parts used
are actually in a database (not intralink database). Is a trigger the
best/only mechanism? Can we use ModelCheck, and if so, can ModelCheck
be run as part as the pre-checkin process automatically?

I think you're on the right track with MC. It is wonderfully capable of all kinds of checks on all kinds of criteria, including layers, layer contents and layer status, parameters and their values, parts and their geometry and many other checks. To make it more wonderful, it can be set up to run, in an Ilink environment, as a standalone application, running on a designated "releasing" folder and as part of an electronic releasing process with an automatic email to initiator on pass/fail. It can also be setup to run, as a scheduled job that automatically prepares models/asssemblies/drawings for release by performing such cleanup tasks as assigning default values to parameters, deleting illegal layers and moving their members to legal ones, and then blanking them. It's also possible to set it up to cruise a vault and check/verify every file against some criterion, resetting it to a base standard, if necessary. When well understood, well used and well managed, it is very powerful software that can do all the checking of design and standards you need. It is most definitely worth giving a serious look.

David Janes