nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Link to TeamSite Job Detail Page?

timmerk

Hello,

We are currently creating a web site to be used internally at our company. We also have TeamSite installed on some different web servers. Is there a way to have our website show a link that will link to an job's detail page on TeamSite? Basically, our web page also keeps track of jobs, and when the user clicks on one job, we want it to open a window from TeamSite showing the detail for that job, as the jobs are the same in both sites.

At first, I tried using the link that TeamSite uses to see an job's detail, but when I try it in another browser, I see that it uses sessions and does not work. There must be a link that will work without authentication.

Let me know if you need clarification.

Thanks for your help!

Edited by timmerk on 06/21/04 11:06 AM (server time).

Find more posts tagged with

Comments

Migrateduser

The answer depends upon (1) your version of TeamSite, (2) what you mean by an "item", and (3) what you want the system to do when you click on the link.

In TS 6.1, you can use the URL iw-cc/properties?vpath=vpath to display the properties of a file given its URL. You would probably want the URL to the file in STAGING or in the current edition.

Brinko Kobrin
Interwoven Staff Engineer

timmerk

Opps, I meant job instead of item. I updated my original post. We are running TeamSite v5. (We have 6, but no one will update it) If we NEED version 6, we might upgrade it, but doing it with version 5 is best.

Thanks!

Migrateduser

WebDesk has a URL that will show task details (see KB article 2137), but I don't think there is a public URL for job details.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

In 5.5.2, go to the job details page, CTRL-N so you can see the URL (or right-click and choose properties), then you just have to compose a URL with that path/those parameters. I remember passing session=& and that worked.

Migrateduser

Reverse engineering the system in this manner may give you a solution that works for you and your system. But be forewarned that the solution runs the risk of not working correctly under certain conditions, or breaking if you upgrade to a later version.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Yep. But sometimes you have to hack it to make users happy. Since there is no exposed CCI for job details in 5.5.2, hacking (or a custom CGI/JSP/etc, which is probably way more work) may be the only ways.

Migrateduser

I agree that you want to make the users happy. But you should be aware of the full cost of the solution. In particular, you may no longer be available when the system is updated later, so you may be creating a problem for the future maintainers of the system. Perhaps you don't care because it may no longer be your problem, or perhaps you think of this as creating future employment. In any event, I'd like to see developers make these choices with their eyes wide open.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

I am aware that any unsupported usages may break in future releases. I am not trying to break the system down the road or give myself future business. In this case Interwoven does not provide an alternative in 5.5.2 - what do you suggest? Obviously a custom job history screen, preferably reading from a database, would be a better solution. Maybe they can afford for PSO to come in and do this for them, even though it may break with any upgrade/patch. But the cost of such a solution is high and since there is a "free" solution available with the product, that cost should be considered as part of the upgrade project. If the organization has current budget for a custom workflow reporting application, then by all means run with it, but the original post asked for a simple link. In this case my understanding is that a CCI URL for job details should be provided by IW with 6.1, so as long as that URL is composed in a subroutine and sent in email, they should only have to change that one sub. Emails sent before the upgrade could be broken, but I'm not sure how big of a deal that is. If the URLs are in other applications, then the logic for constructing those links in those applications should be just as "configurable" as a subroutine that generates the link for emails.

Migrateduser

I just wanted to make sure that timmerk -- and any other developers who might read you suggestion -- were aware that this is an unsupported usage, and what that might mean to them.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

> perhaps you think of this as creating future employment

This is a warning to timmerk? It's interesting that an IW engineer wrote this because it feels like IW spends more energy creating future work for PSO and myself than I ever would.