End User Preview ?

How do people handle outside end user reviewers ? I have users that are from differing groups who are a wide range of one time customers.

Since, if I email joe a URL from TeamSite, it requires a login to see the virtualize page, this implies one of 3 options. First buy licenses for 1 time use, second have people log in as reviewer (probably a license violation), or create another URL outside of TS to view this.

Any other choices ?

Andy

Find more posts tagged with

Comments

ReggieRWalker

Andy,

We have solved this issue in two different ways.

(1) We set up another web server and deployed the changed content (generally from our WORKAREA) to a web site on that server.

(2)Created web sites (on the TeamSite server) that point to the workarea and the STAGING area that are accessible by users outside of TeamSite.

Those are just two suggestions.

Reggie

Adam Stoller

If you're dealing with static HTML pages - you could use Mail: Smiley Frustrated

endmail which, I believe, supports the use of attachments (Mail::Mailer, which is used by iwsend_mail and other such scripts, does not, I believe, support attachments).

If these are truly one-off events, that - or creating a "review" server that you can deploy everything to and sending links to that review server - are probably your best choices.

If these reviewers are going to be involved more frequently - it might be worth getting [author / reviewer] licences for them and also looking at Visual Annotate...

--fish
(Interwoven Senior Technical Consultant)

13adam13

Another option that might be worth pursuing:
We created a guest account on the server. This account had very limited permissions, with no ability to modify any files, just to look at the web pages.
Then, we added a link on the homepage that said "Click here to log in as guest". This made it easy for the very large number of people that simply needed to review content without actually interfacing with TeamSite at all.

Bowker

We had the same desire and found that if you go to:

http://<server>:81/iw-mount/default/main/<backingstore>/STAGING/www/
or
http://<server>:81/iw-mount/default/main/<backingstore>/WORKAREA/<workarea>/www/

You will probably get what you want. There are some issues with relative/absolute addressing that we took care of with changes to the proxy settings. If you need assistance send me an e-mail at ddb@ntrs.com.

Dan
P.S. I also wrote a front end for users to allow them to choose from a list of dropdowns between staging, workareas or even old editions for each branch.

nipper

works great, thanks