Pro/INTRALINK 3.4 Trigger

[pedmunds]

I'm looking for a trigger for Pro/INTRALINK 3.4 that blocks users from checking in a file with status "Released" at the same revision as an existing object with the same status. Does anyone have one that they would be willing to share? I have a trigger for version 3.2 as well as 3.3 but not 3.4. Does anyone know if the old triggers will work with the new version? I only have the executables and not the source code so I can't recompile it for 3.4.

Thanks.

[proed]

Does anyone know the answers to Perry's questions (see below)? I was going to ask the same questions, regarding a Release trigger for Intralink 3.4. We've been in touch with Frotime who did earlier versions, but they no longer do this due to lack of resources...

Regards
Edwin Muirhead

In Reply to:

I'm looking for a trigger for Pro/INTRALINK 3.4 that blocks users from checking in a file with status "Released" at the same revision as an existing object with the same status. Does anyone have one that they would be willing to share? I have a trigger for version 3.2 as well as 3.3 but not 3.4. Does anyone know if the old triggers will work with the new version? I only have the executables and not the source code so I can't recompile it for 3.4.

Thanks.

[BarrySchaeffer]

Edwin and Perry,



I just used the 3.3 trigger with 3.4, and it works fine, although it
DOES produce a goofy error message when a user tries to violate the
checkin rule.



The trigger used to return this message with 3.3:







With 3.4, it returns this message:







When my users see that, I just tell them to lower the release level,
bump the rev, and check it in.



Barry Schaeffer

Fluke

[JasonRuprecht]

Intralink triggers can only be written in straight C. This prevents the
programmer from using tools like MFC dialogs. However, what I have done
is created a second MFC DLL program, and loaded it using the straight C
Intralink trigger to display meaningful error messages. As well, you can
gather all of the errors and display them in the dialog, so the user can
fix all of the problems before attempting to check in again, rather than
fixing one at a time, and cycling through the check in process each
time.







I could create a trigger like this for you, however I am busy at work
and cannot do it there. As well, I do not own my own license of
Intralink or toolkit. Could you provide a license for me to work on?



Jason Ruprecht
General Atomics - EMS Division
System Administrator
jason.ruprecht@gat.com <">mailto:jason.ruprecht@gat.com>

[proed]

Thanks folks for your quick replies on this topic. As Barry mentions (see below), the 3.3 trigger actually works with 3.4 - just gives a different error message. As long as users know what it means you should be OK.

This question was prompted by my US colleague, since one of our Texan servers couldn't get the trigger working at all. Today I hada look - turned out the "Function" was mis-typed: one letter had the wrong case!

Other replies included below.

Regards
Edwin