Workflows for navons and navtrees

Rhythmyx Technical Discussion
1

What are the minimum number of states that are required in a workflow for navons and navtrees?

We have already set up a separate workflow, purely so we can hide these items from ordinary users who do not manage navigations. But we just duplicated the FastForward standard workflow. Because of complications such as http://forum.percussion.com/showthread.php?p=3439 I am wondering if we couldn’t simplify it and save ourselves some bother.

Presumably, navons and navtrees have to have a public state for the managed navigation set up to be reflected in published pages. But they aren’t published themselves, hence do not need an archive or unpublish state? Could be reduce it down to:

Public (Publishable=Publish)
Quick Edit (Publishable=Ignore)

And can the Public state be set as the initial state of workflow?

Thanks,

Andrew.

2

Andrew,

I cannot see any reason why this wouldn’t work, but I caution you that I’ve never tried it, nor do I know of anyone who has.

Dave