Skip to main content
June 13, 2011
Question

One Project, 2 Sign-ons, 2 Versions?

  • June 13, 2011
  • 2 replies
  • 1043 views

In addition to our existing product, we are creating a new software that  needs to share the same help system . In RoboHelp 9, I know that you can apply conditional tags to the project to create two versions from the same project.

However, some of the users of our new product will not necessarily be users of our existing product and must not have access to its help topics. Can RoboHelp 9 be set up to have one sign-on to the existing product and one sign-on to the new product? Users of the existing software could see both versions if they buy the new product, too.

What option in RoboHelp allows users to see one version or the other?

Thanks.

Bill

This topic has been closed for replies.

2 replies

Peter Grainge
Community Expert
Community Expert
June 13, 2011

I wonder if merged help can be considered?

The parent would have no content or just an introductory page.

Your existing Version 1 help would be child one.

A copy of that would then be used to create the Version 2 help that would be child two.

Depending on version your installers would then install the parent and appropriate child.

There is more about merged help on my site.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
June 14, 2011

Peter,

The following may work:

The parent would have an introductory page with two login options:

Option 1:

For users of product A (version 1, child 1) and/or product B (version 2, child 2). Both versions are visible at all times to both user types.

Option 2:

For users of product B (version 1, child 1).

Thoughts?

Bill Janke

Peter Grainge
Community Expert
Community Expert
June 14, 2011

But everyone could access anything and in your first post that was not an option.

If everyone can access any part, then Dynamic User-Centric Content DUCC is what you want. I'm not sure that can be done from RoboHelp for Word. Indeed, I missed that point before when suggesting merged help. Merged help can be done from RoboHelp for Word but it is not straightforward. There's a page on my site about it within the Merged Help pages.

All the real solutions you need are available in RoboHelp HTML.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Captiv8r
Legend
June 13, 2011

Hi Bill

The only way you can manage that is to create two different versions of the help. I'll call them version A and version B.

Allow one group of users access to version A and the other group access to version B. And nary the twian shall meet.

Or, you could restrict one group of users to one version and allow the other group access to both. Your call as you will need to decide who can see what.

Cheers... Rick

Helpful and Handy Links

RoboHelp Wish Form/Bug Reporting Form

Begin learning RoboHelp HTML 7, 8 or 9 within the day!

Adobe Certified RoboHelp HTML Training

SorcerStone Blog

RoboHelp eBooks