Can a trigger open the Resources tab

Yes, I agree that not changing the file name is the ONLY way in which triggers to the Resources tab would work without causing more maintenance. However, what happens when you have version control protocols in place in which the file name needs to reflect updates made (e.g. file_v3.b or file_2014.doc). Then you are required to change both links in which case resource tab triggers are not efficient. And I've also had strange instances when keeping the file name the same for the purpose of reducing maintenance of links but was still led to the old file even when clearing my browser's cache. Other users have reported similar issues with documents not updating properly here. This isn't consistent but I've had this happen on more than one occasion and the only workaround for me was to rename the file. So for these reasons, I am motivated to change triggers on both ends. However, it basically comes down to what process you are using based on your project's requirements and whether your documents are updating properly each time.