by mamarachel on Fri Sep 26, 2008 9:06 am
We have managed to do both context and role sensitive help with a single web help project. As the help author, I have created two topics, say, Welcome Administrators and Welcome Agents, each with its own identifier and value in the alias file. Then I tell the developer that value 1 is to be used with application page xyz when the user is logged in as administrator and value 10 is to be used with the same application page xyz when the user is logged in as agent.
Below is a snippet from the developer's email in which he is describing to me how he makes this work on his end.
The way I do it(without getting too "techy") is not overly complicated, but the application has to have set user designations in-place.
For example, with our application when a user logs into the site, we track what kind of user they are through session variables. We can access these variables on any page within the site. So we know what kind of user someone is(admin, agent, etc.). Your help system is built pretty nicely, in that I can just switch the number value I pass in to call on the fly. So I do a quick check at the top of the page to see if the user is an admin or not (by referencing those session variables). If they are an admin, I set the value passed to the URL to one thing. If they are not, I set it to something else.
Hope that makes sense. I guess it really depends more on the system around it. But I assume anyone looking to set up the help system on a per user basis would have the designations in place and accessible.