Friday, March 26, 2010

Customized Info by UserID or Location

Can Robohelp be the SOURCE knowledge base tool while at the same time customize the view by userID or by where the user is located? For example, certain information is only unique to certain countries (eg regulatory laws). So if a user is from U.S., he can only see the information on U.S Regulatory laws and if this user is from England, he will only see the UK Regulatory Laws Info. Thanks.

Customized Info by UserID or Location

The source would be in the single project and you would apply different build tags to different topics. For example, create three tags called NotUSA and NotUK and NotFrance. Apply NotUSA tags to all topics that you don't want USA readers to see. Likewise with the others.

Then have a layout called say WebHelpUSA with a build expression NotUK AND NotFrance. Build expressions work by excluding content so you want to exclude everything except common content, not tagged, and all other tags.

Duplicate the layout and call it WebHelpUK and tweak the build expression. Repeat for each layout required and bake for 15 minutes.


See www.grainge.org for RoboHelp and Authoring tips

Customized Info by UserID or Location

Can I confirm that this method is applicable on the normal RoboHelp v8 License and not just the RoboHelp Server 8 License? Thanks.

Just so you are clear, the RH Server is purely a physical location onto which your RH output can be placed. It is not a place where the output can be modified. So you'll apply the conditional build tags as Peter has suggested in the RH 8 application and output to the RH Server application. However I should make it clear that you only need to use the RH application if you want the added benefits that that application offers (e.g. usage reports).

There is a lot of information on my blog (see the link below) about the RH Server application which is well worth a look if you are unsure. You'd do well to start here.


Read the RoboColum(n) for a tips and tricks on Technical Communication Suite products.

No comments:

Post a Comment