Thanks for the link urmas. I ran a little spike today on Paul's javascript redirect and Sundar's link action update approaches. While both work - they're both work. What If we keep it simple? Get ready for this - I can't believe it works...
Problem statement: I need to link to the team on the different investment types in a Portfolio's contents in an NSQL portlet. As shown in the screen shots above, the action is projmgr.investmentRoster and you need to feed it an ID, creating a URL like https://<your url>/niku/nu#action:projmgr.investmentRoster&id=<invesment id>. It is best if this is built & maintained through Studio only and requires no more than standard Studio knowledge, skills, tools & access (this requirement eliminates Paul and Sundar's approaches).
Solution:
1) Create a page and use projmgr.investmentRoster as the Page ID. Make it linkable.
2) Give it a Link Parameter to capture ID.
3) Put nothing on it.
4) Setup the link on your query as you normally would. Pass in INV_INVESTMENTS.ID to the ID parameter.
5) Looks like it's feeding the proper URL - does it work?
6) Ideas test out successfully linking to the Idea Team.
7) Projects test out successfully linking to the Project Team.
I have only tested this on Ideas & Projects but it is functioning as expected. I suspect it will work on the other objects too.
Part of me wants to call this a bug that you can create a page with an ID of an internal action... but the seasoned product guy in me says this is no accident. Welcome to an undocumented feature? Very useful.
It is possible this approach will work on the other linking problems in the other threads. This is also 'OnDemand' safe in that it only uses OOTB Studio capability.
HTH.